Most of the time this is something is 'broke'. A general scenario is IEHLIST of the pack to look for overlaps. If restoring a file to another pack it is helpful to now the UCAT where it was. ADRDSSU print with DUMP of VVDS should show DSN and UCAT. Then to further narrow it down IDCAMs DIAGNOSE for UCAT or VVDS can point out discrepancies.
If the DIRF bit is flicked on you should see a message in the LOG INDEXED VTOC disabled. In the olden days we would run batch jobs to allocate temp dsns on packs in question to rebuild VTOC, but haven't done this in many moons-since RAID 5. If it's not a 'size' problem can just run CNVTIX to rebuild the Indexed VTOC. PDS86 and ISMF indicate VTOC construct with I. In a message dated 08/21/13 11:46:34 Central Daylight Time, [email protected] writes: What do you want to know besides whether the index is enabled or not? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
