See my post from yesterday.
Based on your response below, this 300706 seems to have been a backup volume.
There is apparently 1 dataset on a "prevvol" that thinks it is continued onto
300706.
1) HSEND LIST TTOC SELECT(FULL) will show all volumes eligible for recycle
(both ML2 and BACKUP).
Scan this listing for 300706 in the SUCC VOL column. (This information is
from the volume record for "prevvol").
2) HSEND LIST TTOC("prevvol") which will be the volser shown in the first
column.
HBDEL "last dsn on prevvol" ALL (this will delete the connection
to 300706)
If the above does not work, examine the recycle logs immediately prior to the
request for 300706.
If it shows that the volume immediately prior to 300706 was successfully
deleted, I would open a case with IBM. L2 can produce some pretty amazing
FIXCDS commands.
If the immediately prior volume was not successfully deleted, you have your
culprit. Perform step 2 above.
You might also try HSEND LIST DATASETNAME BCDS SELECT(VOLUME(300706)) to get
the datasets that way, independent of the TTOC's.
HBDEL these datasets.
Warning, this will run a while, depending on the size of your BCDS.
Might also be a "leftover" piece of storage. Try a bounce of the relevant DFHSM
address space (unlikely to be successful, but worth a try if all else fails).
HTH,
<snip>
ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X RECORD FOR
300706
Volser 300706 is neither in any hsm ttoc listing (ergo the data set x record
for 300706) nor in rmm, so no prev-vol recycling can come into play here
unfortunately.
Regarding "try a fixcds create which should then enable you to do a standard
delvol."
I issued a TSO HSEND FIXCDS X 300706 CREATE and hsm reported the record created:
ARC0197I TYPE X, KEY 300706, FIXCDS CREATE SUCCESSFUL (I chose type X since X
was what was reflected in the ARC0184I error message for volser 300706)
Then followed with a DELVOL 300706 BACKUP(PURGE) but that apparently simply
deleted the record just created with the fixcds create command.
ARC0260I BACKUP VOLUME 300706 ENTRY DELETED leaving still, some vestige of
300706 residing somewhere in HSM A subsequent LIST TTOC SELECT(FAILEDRECYCLE)
still is showing the same "ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X
RECORD FOR 300706"
Short of reconstructive surgery on the cds...is there any other commands I can
try to tell HSM to just fuhget-about this non-existing volser 300706??
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
