At 15:31 -0600 on 01/14/2008, Chase, John wrote about Re: IEBGENER is BROKEN:
> -----Original Message-----
From: IBM Mainframe Discussion List On Behalf Of Anthony Fletcher
If you use IEBGENER in straight copy mode, it does check and
enforce that the LRECLs match.
All well and good -- for FIXED-length records. Irrelevant for
VARIABLE-length records.
It can be relevant if the new LRECL is less than the old one as
opposed to being larger. While increasing the LRECL will allow all
the records in the input file to copy to the output one, decreasing
the LRECL can run into problems if any of the input records are
larger than the smaller output LRECL (unless you switch from VB to
VBS). This "sanity check" when decreasing the LRECL is only a safety
check if the new LRECL is still equal to or larger than the actual
largest record in the input file (IOW: If the largest record is 100
bytes long, you can safely reduce the LRECL to 100 and BLKSIZE to no
less than 104).
----------------------------------------------------------------------
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
