On Fri, 15 May 2009 11:31:19 -0500, McKown, John <[email protected]> wrote:
>Perhaps this explains the observed action? > >http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/IGY3LR31/5.2.4 > ><quote> >BLOCK CONTAINS > 0 can be specified for QSAM files. If BLOCK CONTAINS 0 is specified for a QSAM file, then: > > * The block size is determined at run time from the DD parameters or the data set label. If the RECORD CONTAINS 0 CHARACTERS clause is specified and the BLOCK CONTAINS 0 CHARACTERS clause is specified (or omitted), the block size is determined at run time from the DD parameters or the data set label of the file. For output data sets, with either of the above conditions, the DCB used by Language Environment will have a zero block size value. If you do not specify a block size value, the operating system might select a system-determined block size (SDB). See the operating system specifications for further information about SDB. ></quote> That quote specifically refers to use of BLOCK CONTAINS 0. It does not seem to explain why the same results are seen if there is no BLOCK CONTAINS clause at all. ... Wait, it does say "or omitted". So I guess this does explain it. This gives me one more reason to not have BLOCK CONTAINS 0. That as well as "BLOCK CONTAINS can be omitted for SYSIN files and for SYSOUT files. The blocking is determined by the operating system. " Though of course specifying BLOCK CONTAINS 0 there would not hurt. But again I don't like to have it there if it's just going to be ignored. Oy! Frank ---------------------------------------------------------------------- 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
