On Tue, 8 Jul 2008 13:05:03 -0700, Skip Robinson wrote: >The problem seems to be that any reference to a data set in JCL with an >'exclusive' disposition (new, old, mod) will render the data set >inaccessible outside that job until it finishes. I haven't experimented,
My understanding is, no, not until the job finishes, but only through the last step that has any JCL reference to the data set (new, old, mod, shr). >but I would think that creating the data set dynamically would work. For >example, run a TSO TMP step > >//CREATEDS EXEC PGM=IKJEFT1B >//SYSTSPRT DD SYSOUT=whatever >//SYSTSIN DD whatever > >either with individual TSO commands (delete, allocate, etc.) or with a Rexx >containing those commands. I'm pretty sure that the data set will be >accessible because the job's initial TIOT will not have an entry for it. > But beware, if in a subsequent step your JCL references that data set, even with DISP=SHR, the job's inial TIOT will have an entry for it, and creating the data set dynamically will upgrade the ENQ to EXC, and the data set will remain inaccessible outside that job until that later step finishes. (Or so I've been told.) -- gil ---------------------------------------------------------------------- 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
