I kind of missed some of the posts for this, but if you really want them to run one by one, you could give them their own job class and only define one initiator for that class.
Jon L. Veilleux [email protected] (860) 636-2683 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Walt Farrell Sent: Wednesday, February 11, 2009 2:21 PM To: [email protected] Subject: Re: JCL job execution order On Wed, 11 Feb 2009 11:13:07 -0700, David Logan <[email protected]> wrote: > You can prevent >temporary dataset name conflicts by ensuring that the last step that >uses a temporary uses DISP=(OLD,DELETE) > You're right that the user can certainly prevent the conflicts by making sure his JCL always has a DISP=(OLD,DELETE). However, since it does not matter in an individual job, it's likely he has not done that or will make a mistake at some time, causing unpredictable failures in the job if you were to simply concatenate multiple jobs together.. And I think it would be difficult for the automated job submission tool to find and correct this kind of error. -- 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 This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ---------------------------------------------------------------------- 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
