Hi, All,
One of our DBAs noted that a DB2 batch utility whose JCL typically
includes:
//SYSPRINT DD SYSOUT=*
Is occasionally changed to:
//SYSPRINT DD
DSN=data.set.name,DISP=(,CATLG),RECFM=FBA,LRECL=132,. . .
This variation with LRECL=132 apparently had been working "for decades",
including most recently with DB2 v8.1 in compatibility mode.
Now DB2 has been switched to "new function" mode (still v8.1). The DBA
notes that the same DB2 batch utility now fails when //SYSPRINT is
directed to a dataset with LRECL=132, but works fine if the LRECL is
changed to 133. He told me that along with the switch to "new function"
mode, this utility program had to be re-linked, and that the re-link
used only IBM-supplied object decks. He is unaware of any other changes
that might have affected the LRECL of //SYSPRINT.
Anybody have any ideas as to why "it used to work" with LRECL-132, but
now -requires- LRECL=133?
TIA,
-jc-
----------------------------------------------------------------------
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
