|
Although not quite what you had in mind... its in the neighborhood. You can force a program to run before and after each job in a particular subsystem via: o A subsystem routing entry forces a call to PGM1 instead of QCMD o PGM1 does whatever BEFORE-JOB processing you wish, sends a request message to *EXT with message data 'CALL PGM2', and then does TFRCTL PGM(QCMD) o -- the particular job executes -- o PGM2 does whatever AFTER-JOB processing you wish I believe program PGM2 will be executed at end of job whether or not the job ends normally. PGM2 has a chance to examine or force creation of a joblog - no matter how the LOG(x xx *xxxxxxx) parameter is set. I've used this before to generate straight forward job execution statistics under certain situations. Jerry Jewel +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.