Easily solved by making the new first step name STEP0 or COPYDATA or any other unique name. The instream input data would then have to go into STEP0.SYSUT1 or COPYDATA.SYSUT1 of course, not SYSIN.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Ken Moore > Sent: Wednesday, January 12, 2011 12:34 PM > To: [email protected] > Subject: Re: passing instream sysin to next step > > If it were any other DD besides SYSIN, I would definitely consider it. > However, SYSIN for IEBGENER is reserved for command parms and input to > IEBGENER. Additionally, as John M pointed out, there are potentially 3 > or 4 other overrides for the current STEP1. If STEP1 suddenly becomes > an IEBGENER, the overrides are lost for the subsequent step. -- 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, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
