On Sat, 10 Jan 2009 11:47:27 -0600, Scott Barry wrote: >Now that JES2 (and maybe JES3?) now support instream data-image (like SYSIN)
JES3 longer than JES2, perhaps forever, and perhaps better than JES2. What does JES3 supply as the attributes of such an instream data set? I had thought it used RECFM and LRECL of the submitting INTRDR, but perhaps I was merely guessing. Recent experiment shows that JES2 supplies RECFM=FB, LRECL=(longest input record with a floor of 80). I prefer the (possibly conjectural) JES3 convention; it gives the programmer better control. Best would be to allow the programmer to specify RECFM, LRECL, and BLKSIZE on the sysin DD statement. >LRECLs greater than 80-bytes, I am curious if/when VM/RSCS instream >data-image interface will ever support the same? > What happens if you CP SPOOL/TAG a virtual printer to the z/OS guest and write your JCL to that? >Of course, that observation/question would include any application/utility >program which also takes instream data images, considering that the LRECL >may exceed the legacy-standard of 80 bytes. > I gladly regard that as a pejorative use of "legacy". -- 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
