I can't for the life of me explain why this is not HIPER, but if you use
PDSEs in your shop I highly recommend APAR OA30338.
Without this fix, we had broken PDSEs that could not be read, accessed,
or even deleted and that led to abends in HSM, CATALOG errors, DADSM
errors, corrupted VTOCs with overlapping extents--the works. The VTOC on
one volume (an EAV) was so screwed up, we had to completely reINIT it.
To get rid of these bad PDSEs, we had to one-at-a-time ZAP the FMT-1
DSCB in the VTOC to turn off the PDSE flag, delete the PDSE, immediately
allocate a "dummy" sequential data set to reuse the just-freed DSCB for
non-PDSE data set, and then either restore the PDSE from a backup or
recreate from scratch. It was ugly!
Unfortunately, an IPL is required to make the fix effective. But, it's
worth it!
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
