|
I have not been following this thread very closely, but one could certainly
do what ever data gathering is necessary in the exit program (it runs in
the job performing the SBMJOB), if necessary (due to size) store the data
under some arbitrary key passed in the first parameter (or just make the
data into a parameter), and then have the initial program of the submitted
job perform whatever is necessary to recreate the environment. Assuming
that the submitted job would run OK in the initial job if directly CALLed
(which is what I'm not sure of when skimming this thread), then the
submitted applications would/should require no change.
This would require no change to the defaults of the IBM SBMJOB command
itself, require no duplication of the SBMJOB command and subsequent playing
with the library list, and as an added benefit enable one to do a whole lot
of "other things" while in the exit program.
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.