I would divide the problem into two: 1. how to make the file be transactional. to do this, you can use MQ as the mechanism to write into a "file". 2. where to fire the transaction. You can "write" the message into a queue managed by CICS and LINK to the application program (not START TRAN that will cause a lot of overhead on CICS). CICS will give you fine recovery and error handling and minimize the changes you need to make in the current program (is you run in under OTE). other alternatives are MQ to DB2 and define a trriger on the table to fire a Cobol (or other language) stored procedure.
ITschak On Mon, Feb 20, 2012 at 9:03 AM, Magen Margalit <[email protected]> wrote: > Hi. > > The records arrives from a few sources to a few seq files > The collection process collect the records from the files and then the > batch process begins. > In the new situation, the batch process or STC will handle each record and > the collection process will be eliminated. > > Regarding the maintenance gap, I'm not concern from a complicated code, > but from using functions that IBM will someday > will no longer support, i.e. LE functions. When you upgrade a zOS version > you contact all the software vendors and > check for compatibility to the new zOS version, on a "self developed" STC > you cann't do that... > > Magen > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
