ISTM, this restriction is still in place. I ran isrddn the other day and it flagged a dataset in the concatenation that had a smaller blocksize than those following it. We reblocked that data set and isrddn did not complain.
Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville [email protected] 502-495-5000 x7011 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Kington Sent: Friday, August 07, 2009 7:49 AM To: [email protected] Subject: Re: Concatenations and blocksizes >It is a misdesign that the OS allows this ever to happen. The >principal use of this facility is to correct errors that were >introduced by its earlier inadvertent use. Simply, any OPEN for WRITE >with overriding attributes where the label contains different nonzero >attributes should ABEND for inconsistent attributes. >If the programmer feels compelled to change attributes the recourse >should be: >o ZAP the VTOC, or I use the same mis-design to reset it back to the original blocksize. If the change was recent (last couple of days), I make an attempt to find the culprit and have them fix their jcl. Zapping the vtoc is the last (*very* reluctant) resort and only to be done by a very select few. >o COPY, reblock, and rename. This is the proper way to make a planned, permanent change to the dataset attributes. Regards, John ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
