STEP1 may have other DDs in it which the user is used to overriding with //STEP1.ddname DD and so that would require a JCL change for all users of the PROC. Curiously, as I recall, OS/VS1's JES work-alike allowed the DSN referback to SYSIN and SYSOUT of a previous step. For SYSIN, it reread the input. For SYSOUT, it did the equivalent of a DISP=MOD.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Lizette Koehler > Sent: Tuesday, January 11, 2011 2:20 PM > To: [email protected] > Subject: Re: passing instream sysin to next step > > > 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. > > > > So is there any reason you cannot have an IEBGener step at the very > beginning of this job stream that would pass a temp DSN > through the rest of > the JCL. Then if your users want to override SYSUT1 with > instream it is > still a temp dsn for the remainder of the job? > > Lizette > > ---------------------------------------------------------------------- > 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
