Given the overlapping extents, at least two of your datasets (assuming you
don't have a dataset that overlays itself) are suspect as is the free space map.
Step 1: Prevent any new allocations. This includes both new datasets
and additional extents for existing datasets. "V SMS,VOL(xx),DISABLE,NEW"
restricts new datasets if the pack is SMS managed.
Step 2: Obtain a list of extents/associated datasets and identify the
datasets that overlap.
Step 3: Move all the non-overlapping datasets off this volume and
restore the overlapping datasets from the most recent "good" backup. (Possibly
the owners of the overlapping datasets could tell you if either is still good.)
Step 4: Find out how this occurred and take corrective action.
Depending on the cause, you may want to examine other packs for possible
overlap.
-----Original Message-----
From: esmie moo
Sent: Monday, September 22, 2008 5:59 AM
To: [email protected]
Subject: VTOC INDEX STATUS : DISABLED
Good Morning Gentle Readers,
I noticed (via ISMF) that one of our dasd is in DISABLED status under INDEX
STATUS.
When in TSO option 3.4 I do a "V" I receive a "Free space error". I attempted
to perform the following
BUILDIX DDNAME(D01) OSVTOC - I receive :
ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 ICK31515I 61E5 BUILDIX COMMAND
FAILED.
I tried BUILDIX DDNAME(VOLDD) IX but I was not successful. I received :
ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 ICK31515I 61E5 BUILDIX COMMAND
FAILED.
Is there something else I can try short of reinitializing the pack, which is
presently 75% full.
----------------------------------------------------------------------
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
