On Thu, 2 Sep 2010 14:40:06 -0500, Kirk Wolf wrote: >We are working on some support in our Co:Z Toolkit that allows users to >submit and manage jobs, and I was wondering how often (at all) anyone really >needs to submit jobs with records that are not fixed length, LRECL=80? > The only thing that I could think of was some sort of NJE transfer of data >(without TSO SEND/RECEIVE). Its not that it is hard to allow this, but it >would simplify the interface if it were only F/LRECL=80. > >Any thoughts would be appreciated. > I was generating a job with a script and submitting it with FTP.
It had commands in an instream data set. I was anguishing over inventing a continuation convention for long commands. Then, I thought, "That's _so_ 20th Century; why restrict commands to 80 characters?" I made it JESRECFM=V,JESLRECL=254 (254 is also an outdated restriction). I'm not sure I ever had a record >80, but I don't have to worry about it. What's simpler about F/80? Are you in a place where you can't allocate SYSOUT=(,INTRDR),FILEDATA=TEXT? Beware. Regardless what you specify on INTRDR DD, JES2 causes instream data set to appear as RECFM=(as on INTRDR), LRECL=(longest instream record); JES3 RECFM=FB, LRECL=(longest instream record). (All empirical; ran IEBGENER and inspected attributes of SYSUT2.) -- 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
