-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of McKown, John Sent: Thursday, June 24, 2010 1:21 PM To: [email protected] Subject: Re: instream data
<SNIPPAGE> That has been a restriction since the dawn of OS/360. In that case, I think it was due to the primitive nature of the reader code. IIRC, the original reader code (pre HASP), read cards from the card reader. When it detected in-stream data, it actually created an "temporary" OS dataset and wrote the cards into that dataset. The processing of PROCs (expansion) was done in another part of the code, not in the actual reader. So, to have "in stream" data would require a more complicated and advanced expansion. And that was not really possible at the time. <SNIP JES2 specific comment> Of course, that is not really a good reason to continue to have this restriction, IMO. <SNIPPAGE> Let us not forget JES3 (ASP). Interestingly JES2 supports a larger in-stream LRECL than JES3 does (or did, they may have fixed that in the last few releases). Regards, Steve Thompson ---------------------------------------------------------------------- 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
