The post quoted a message citing the block size. The obvious fix is BLKSIZE=32760, not BLKSIZE=0.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jesse 1 Robinson <[email protected]> Sent: Tuesday, May 7, 2019 4:38 PM To: [email protected] Subject: Re: BLKSIZE=0 (was: Crazy ...) With the thread having been rechristened, I'm not sure who gets the OP title. I was the OOP. Turns out there was actually no BLKSIZE error. The problem was Fault Analyzer's rush to judgment after an SQL data choke. OTOH I'm pretty sure that BLKSIZE=0 would help only to set the max value of 32760. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Seymour J Metz Sent: Tuesday, May 7, 2019 10:25 AM To: [email protected] Subject: (External):Re: BLKSIZE=0 (was: Crazy ...) There were documented cases where you still needed an explicit block size for the for the concatenation. Based on the OP, it would appear that there still are. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Tuesday, May 7, 2019 11:53 AM To: [email protected] Subject: Re: BLKSIZE=0 (was: Crazy ...) On Tue, 7 May 2019 15:33:39 +0000, Seymour J Metz wrote: >Well, removed except when it wasn't; there were caveats. > ??? >________________________________________ >From: Tom Marchant >Sent: Tuesday, May 7, 2019 11:02 AM > >>What about BUFL=? As I recall, I used to use this to keep from having >>problems with concatenations... > >Yes, until about 25 years ago, when the requirement that the first data >set of a partitioned data set concatenation have the largest BLKSIZE >was removed. > Silly (naive?) me. I just coded an overriding BLKSIZE on the first catenand. Or supplied a leading empty temp DSN with suitable attributes. Would that satisfy the "caveats"? Same for LRECL. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
