On Thu, 22 Mar 2007 13:50:17 +0000, Bill Wilkie <[EMAIL PROTECTED]> wrote:
>If it is not what Steve said, you may want to see if it went into extents >due to updates. The extents are known at startup and if it gains an >additional extent during normal operation, the PDS directory block will >correctly point to the right data block, but that block is now outside of >the extents known at startup. If that's the case, you can prove it with a >compress to hopefully bring the block back into the original extents. No need to compress. JES2 is dealing with it on its own by re-opening the library after the I/O error. If you compress at that point, you will run into a problem again (which JES2 will again deal with). > If it's a pdse, i'm not sure. Not an issue for PDSE. There... to jump into another thread with all the PDSE bashing... this is one thing that is good. We changed our JES2 PROCLIBs to PDSE years ago because of this (long before dynamic proclib support). Also good in LNKLST... PDSE only counts as 1 extent. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
