Scott Ford wrote:
>We have a Cobol STC running with a Assembler Operator Interface, single >thread. I understand I could redo in Assembler and multi-task, redo in C or >C++ and thread, but this isnt what I am looking for. Inside the STC we >maintain a secondary index of data items. If the Operator issues a 'P ......' >or 'C ........' we will loose the secondary index. My idea is to write a Cobol >condition handler with TRAP(ON) in LE to capture the S222 and at that time >read the secondary index and write to disk. I am just not sure of the steps in >the Cobol. I could write the condition handler in Assembler or C I dont care. >My object is not to loose this data.. Until you get a solution, why not at intervals write out that index to DSN1 and again, but to DSN2. Repeat with DSN1 and so on? Just to keep your index updated regularly on disk. If you can, try putting your indexes in a database, say DB2 or something? AFAIK, COBOL just can't handle a sudden death properly, you'll have to add something else using a trap condition handler. Alternatively, put in RACF this OPERCMDS class profile MVS.CANCEL.STC.<name> and MVS.STOP.STC.<name> to prevent rogue ops to play king. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
