John, The largest blksize first restriction did go away with for Fetch in XA, and it was before the restriction was lifted for SAM-E datasets (refer to Ed Jaffe's comments).
In one shop I was in a JCL check product was insisting that this was required for production JCL that had worked faultlessly for years. Are you able to recreate the error and post it to the list? Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of > John Kington > Sent: Thursday, August 06, 2009 11:34 AM > To: [email protected] > Subject: Re: [IBM-MAIN] Concatenations and blocksizes > > Herman > > >Really, I took it out and the job failed. Put it back in and it worked > >without incident. And yes I still have it in that job to date. > > I would look at the blocksize on each dataset in your concatenation and verify > that you do not have any members blocked greater than the blocksize. A problem > that I have had in the past was someone updating a PDS with a blocksize on the > DD which causes the blocksize in the vtoc to be changed. > > I believe Ed and Ted are right about the largest blocksize first restriction > on concatenations being lifted with MVS/ESA. > > 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
