On Tue, 7 May 2019 21:00:45 +0000, Seymour J Metz wrote: >The post quoted a message citing the block size. The obvious fix is >BLKSIZE=32760, not BLKSIZE=0.
I agree. I'm pretty sure that coding BLKSIZE=0 for an existing data set will have no effect because it is indistinguishable at OPEN time from not coding BLKSIZE on the DD statement. The only time BLKSIZE=0 will help is when the data sets are created. -- Tom Marchant > >-- >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 thre d 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
