Scott Rowe wrote:
Most likely because the BLKSIZE is in the JFCB, and so acts as an override. If the small BLKSIZE is only in the DSCB it is treated differently. I actually thought about testing this yesterday, but didn't have time. I suspected that it would work this way.
This appears to be true. If I code a blksize on the DDCARD of the passed temp dataset in the ASM step, it also fails. I guess this means the system (or assembler) will use the largest blksize at open time if there is no blksize in any JFCB's. Obviously the system can't override a blksize coded on a DCB macro. -- Richard ---------------------------------------------------------------------- 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
