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
