From: Bruce Black <[EMAIL PROTECTED]>
> So, the question seems to be "is the VTOCIX active?", and nothing to do
> with the VTOCIX name.
For the sake of clearness and to close the thread on this topic, I have to
admit that Bruce
was right about VTOCIX name having nothing to do with the problem I had.
I reviewed the output of the IEHLIST LISTVTOC which confirmed an active VTOCIX
on the volume.
However, SYS1.VTOCIX.xxxxxx was the only dataset whose SER NO field was xxxxxx,
while all other datasets had SER NO yyyyyy, being the volume yyyyyy, too.
I don't know where this mismatch come from, but it didn't cause any problem to
us so far,
until I had to restore the data for DR and found the problem with the wrong
volser.
Instead of simply renaming the VTOCIX, I converted the VTOCIX to OSVTOC with
PURGE; then
I built a VTOCIX with a consistent name on the affected volume and reran my DR
restore.
The correct volser shows up now, everything is consistent. Another thing
learned.
Walter Marguccio
z/OS Systems Programmer
Munich - Germany
----------------------------------------------------------------------
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
