On Tue, 4 Dec 2018 23:48:12 +0000, Jesse 1 Robinson wrote: > >I'm not aware that IEBGENER itself ever changed. You either kept the classic >version or played the alias game. The app we shot in the foot counted on >IEBGENER default behavior by hardcoding I/P block size later on for the same >file. I personally think it's inexcusable to make that kind of choice. If >you're going to hardcode on input, you should also be hardcoding at creation. >IIRC the I/P block size was some kind of complicated logic that calculated a >specific number of records per block on tape. > Surely IEBGENER has changed. Nowadays it supports a PARM=SDB=... But IEBGENER antedates SDB and would not have a PARM=SDB in days of yore. And ISTR that the number of control statements in SYSIN once needed to be declared in PARM. (Imagine! such REGION parsimony!) The Ref. now states that SDB is the only supported PARM option. I bet they still tolerate that older one for compatibility.
And in: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.icea100/iceins.htm Use ICEGENER instead of IEBGENER ... ICEGENER, like IEBGENER, will use an SDB=value parameter you supply using PARM='SDB=value', ... You must have fallen into a hole while ICEGENER had not caught up with IEBGENER. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
