My perl scripts ensure that temporary datasets only exist across the important steps, and are deleted in the last used step.
My point is that if it's being controlled by an automated job creation process, it won't screw up the OLD,DELETE. David Logan Manager of Product Development, Pitney Bowes Business Insight http://centrus.com W: (720) 564-3056 C: (303) 818-8222 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Walt Farrell Sent: Wednesday, February 11, 2009 12:21 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 ---------------------------------------------------------------------- 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
