not when I ran production... but I suspect you're talking about a short control card sysin, something easily CC'd in SPF edit, not raw data input. haven't seen raw data in a production JCL stream since we parted with punch cards circa 1980. if other folk's mainframe shops still run that way, I'll reiterate putting the data safely into a flat file before running batch against.
--- On Wed, 1/12/11, Sam Siegel <[email protected]> wrote: > From: Sam Siegel <[email protected]> > Subject: Re: passing instream sysin to next step > To: [email protected] > Date: Wednesday, January 12, 2011, 6:36 PM > On Wed, Jan 12, 2011 at 3:01 PM, Cris > Hernandez #9 > <[email protected]>wrote: > > > ok, let's back up to the beginning. why would > anyone want to put their > > data into a SYSIN DD * ? > > doesn't sound like anything that would happen in a > production environment, > > or QA testing, so that leaves unit testing in > development, ad hoc reporting > > and classroom exercises. > > > > happens frequently in production on restarts with a dd > override. > > > > > If it isn't production or Quality Assurance, do > whatever suits you, but the > > answer to your questions... > > > > how to corrupt your in-stream data: > > 1) edit with ISPF > > - caps on-off > > - change all's > > - accidental keystrokes > > - datatype, lrecl restrictions > > - unprintable characters > > - TSO inexperience > > - inadvertant tabs, spacing > > > > Copying the data to a flat file keeps the raw data > separate and somewhere > > it won't be lost or edited unless editing is required, > plus its reusable by > > other JCL members. > > > > > > --- On Wed, 1/12/11, Paul Gilmartin <[email protected]> > wrote: > > > > > From: Paul Gilmartin <[email protected]> > > > Subject: Re: passing instream sysin to next step > > > To: [email protected] > > > Date: Wednesday, January 12, 2011, 12:56 PM > > > On Tue, 11 Jan 2011 15:44:20 -0800, > > > Cris Hernandez #9 wrote: > > > > > > >I agree with this post. Why read the same > file twice > > > other than to make a copy of it, especially when > it's > > > something as easily corruptible as raw, instream > data coded > > > within JCL. > > > > > > > What makes instream data so "easily > corruptible"? > > > > > > Well, OK, as recently as yesterday I typed "SAVE" > with my > > > cursor in the > > > data rather than on the command line. (I > recovered in > > > time.) > > > > > > But how does adding an IEBGENER step make the > process more > > > resistant > > > to this or any such error compared to simply > reading the > > > SYSIN twice > > > (if that were possible)? > > > > > > Related question: Long ago an Expert told me it > was > > > forbidden to > > > open SYSIN, read it, close it, reopen it and read > it again > > > in the > > > same step. (I had asked him why he preceded > a > > > Waterloo SCRIPT step > > > with IEBGENER to a temp DSN.) By recent > experience, I > > > can reread > > > SYSIN (within a single step). Has something > changed, > > > or was my > > > mentor mistaken long ago? (I think it was > MVS 3.8.) > > > > > > -- 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 > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > 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 > ---------------------------------------------------------------------- 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
