Thanks. The program (the subroutine in question, anyway) is in assembler. The DCB is coded without BLKSIZE= (i.e., defaults to BLKSIZE=0). The program picks up LRECL and RECFM values from a combination of DD/DSCB attributes, passed parameters used in an open exit, and values pulled from another DCB, but never touches BLKSIZE (although it could be coming from a DD or DSCB). The JCL does not specify any DCB attributes in this particular case.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ulrich Krueger Sent: Friday, June 16, 2006 1:34 PM To: [email protected] Subject: Re: Track capacity? Charles, my response has nothing to do with track capacity, but since you mentioned an unexpected SB37-04 and previously talked about a blocksize mismatch between JCL and actual allocation ... Is the user's program, by any chance, a COBOL program? Does the JCL hardcode a blocksize value (or BLKSIZE=0), yet you still end up with an unblocked dataset? ---------------------------------------------------------------------- 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
