|
>We have a long running CL program that runs in batch. This program calls another long running CL program and runs it under the same submitted job before >coming back to the original CL to finish up processing there. We can not submit the second CL job as it needs to process completely before the first one can finish. >Is there any way to identify the second CL job is running via the WRKACTJOB screen? It would be great if I could somehow change the originally submitted job's >name when the second CL starts, but do not see a way. Dave one way to tell is by looking at the program stack (option 10 from WRKACTJOB). An idea could be to send a message to say QSYSOPR indicating the points where the program/job has got to.. HTH Mike ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ This communication and the information it contains: - (a) Is intended for the person(s) or organisation(s) named above and for no other person(s) or organisation(s). Access to this mail by anyone else is unauthorised. (b) Is confidential, and may be legally privileged or otherwise protected in law. Unauthorised use, circulation, copying or disclosure of any part of this communication may be unlawful. (c) May be susceptible to interference, and should not be assumed that it has come in its original form and/or from the stated sender or PinkRoccade UK accepts no responsibility for information, errors or omissions in this e-mail or use or misuse thereof or any act done or omitted to be done in connection with this communication. If you are not the intended recipient, please inform postmaster@xxxxxxxxxxxxxxxxx immediately and delete it and all copies from your system.
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.