On Wed, 11 Feb 2009 09:39:48 -0500, Dave Salt <[email protected]> wrote: >The only messy part might be ensuring the step names are unique throughout the job, but other than that I think this might be the best solution?
And that temporary dsnames don't conflict (e.g., DSN=&TEMP with DISP=(NEW,PASS)), and that you don't have more than 255 steps (I think that's still the limit, but I haven't checked recently), and that condition code checking doesn't cause skipping of later steps that would not have happened if they were separate jobs. If an automated process is doing the submission, why couldn't it build a nested job stream. It would read the first job, and add a step to submit the second. While building the SYSIN file containing the 2nd job, it could add a step to submit the 3rd. While building that SYSIN, it could add a step to submit the 4th, etc. You don't change the real JCL, which allows the user to submit manually whatever/whenever he wants. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
