> > Hi list. > > We have a daily betch job that is processing as input records which has been collected > all day. > volume of records is about 5 millions for 24 hours. > > In order to make systems more "online" we are looking for a way to run the process > for each record all day long instead of a daily run, and doing so with minimum as > possible application changes. > > One idea that came up is to convert the process to a "self developed" STC which will be > triggered by a record on an MQ queue and will run as STC all the batch process > programs > > To me it seems like a bad idea because having a "self developed" STC in production > create a maintenance gap (and where there is one STC a second one will soon to > follow...)... > > Are there other advantages / dis-advantages regarding a "self developed" STC ? > > Are there any "self developed" STC's at your shop? > > Any other ideas on how to approach this issue? > > Thanks in advanced. > > Magen >
Perhaps you could review the BATCH PIPES process in z/OS or if you have MQ, perhaps that could support what you need. Other options could be IMS solution MQ solution CICS solution DB2 Solution We currently have a need to send out orders when a DB2 table is updated. To do this we use our CA-ESP Scheduling software to monitor the DB2 table, when there is a row change, it triggers the process to action the order. If there were some more details on your problem, we might be able to come up with more specific answers? Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
