Hi. There are probably a dozen ways to skin this cat, and only 2 or 3 of them palatable.
I have a proc that has one step to which I will add another step. The SYSIN for the second step needs to be the exact same input as the SYSIN for the first step, so I have a refer-back for the STEP2 sysin //SYSIN DD DISP=SHR,DSN=*.STEP1.SYSIN. This works like a charm, until someone uses instream data for the SYSIN for STEP1. So I'm trying to figure out what is the best way around this. If I leave as is, STEP2 gets a JCL error (naturally) because the JES dataset has been deallocated at the end of STEP1. So, what little bit of JCL magic or IBM utility magic can I use to make sure that STEP2 uses the same SYSIN as STEP1, regardless of input medium? I would even go for a conditional 'skip this step' if I can deduce that the SYSIN input was instream in STEP1. Ken Moore ---------------------------------------------------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
