The entry has an error indicated by the reason code. The error occurred in the record specified, where the record is either the key of the record in a BCS, or an RBA for a VVDS. In most cases, this message is followed by an IDC21365I message that displays the record in error. An IDC21363I message summarizes all entries with errors at the conclusion of the DIAGNOSE run.
Each record is composed of cells, each of which has a cell type and a cell length. The indicated entry has a cell length of zero, which is an error. This error may be caused by incorrect positioning (caused by some other error) or the length may actually be zero.
Various catalog records can only contain certain cell types. The record being analyzed contained a cell type that either did not belong in the record or was not a legal cell type. This error may be caused by an incorrect length in the preceding cell that resulted in incorrect positioning.
Each record in a BCS or VVDS has an record type. The record named has an invalid type for integrated catalog facility catalogs.
While processing an entry, a cell type was encountered that signalled the beginning of a new record. This may be caused by an invalid length value or a damaged entry.
VSAM clusters and alternate indexes, and generation data groups, have components. While checking one of these types of entries, DIAGNOSE found a component length of zero. However, component length should always be greater than zero.
A cell length was found that is inconsistent with component or record length. This may describe the cell being processed or the preceding cell.
The sum of all cell lengths in a component is not equal to the component length, which it should be. Either the component length is wrong or one of the cell lengths is wrong.
Although certain cells such as volume cells can occur more than once in an entry, most cells may not. The indicated cell occurred more than once, but is a type of cell that should not.
The record length at the front of the record is not the same as the length stored by VSAM record management.
The EXTEND function did not execute to completion. The named entry was interrupted in the middle of an EXTEND/EOV operation.
The DELETE function did not execute to completion. This may indicate existence of partial record structures in the BCS.
VTOC sequence numbers start at 0; VVDS record sequence numbers start at 1. The VVDS record number should always be one greater than the VTOC number. An exception to this rule is the VVR sequence number for key range data sets.
VOLFLG is a field in the VVDS record for the named entry. This field has prime and overflow indicators. For the named entry, the indicators in the BCS and VVDS are not equal.
BCS and VVDS records both have high and low key fields. The fields and their lengths must be equal; they were not.
The extents in the VTOC DSCB and VVDS record were compared. They were not equal, although they should be.
The data set control block (DSCB) for the named entry could not be found in the VTOC.
There should be a VVDS entry for this BCS entry, but one could not be found.
The BCS should have an entry for the VVDS record, but one could not be found.
Certain types of BCS entries may be paired with other BCS entries. For example, catalogs, non-VSAM data sets, and generation data sets are paired with their aliases, and VSAM data sets are paired with their paths. This pairing of one record with another is called an "association." Associations between entries are connected by name and are indicated by an association cell in an entry. The indicated association name cannot be found elsewhere in the BCS.
For an explanation of "association", see reason code 20. If an association can be found, but the association does not point back to the original entry, an association loop failure exists. For example, if a non-VSAM data set has an alias, the alias record should point back to the non-VSAM data set record.
VSAM clusters with components have more than one catalog entry. The associated components have truename entries. A truename entry was not found, although there should be one.
The truename entry for a cluster did not point back to the cluster record.
Depending on the component or entry type, certain cells are required. The cell type indicated is required, but missing.
The BCS named in the VVDS record could not be allocated.
The indicated cell is a valid cell type, but it is not valid for the type of entry being scanned.
Each generation data set entry should be reflected in the generation aging table (GAT) cell of the generation data group entry. An entry is missing.
Each entry in a GAT cell represents a generation data set entry within the current generation data group record. No generation data set could be found for a GAT cell entry.
Each alternate index entry is reflected in the REL ("relation") cell of the associated cluster record. An alternate index entry was found that was not reflected in a REL cell.
An entry in a REL ("relation") cell in a cluster record does not represent an alternate index entry.
The BCS named in the VVDS record could not be opened.
A BCS record which matches a VVDS record was found, but the BCS record is not a cluster, truename, or non-VSAM record.
The current entry was undergoing a subrecord update/move operation that did not complete. This record or subrecord may be damaged.
The extent information kept in the VTOC and VVDS should agree, but do not.
The extent information kept in the VTOC and VVDS should agree, but do not.
The length of a name cell should be from 1 to 45 characters long, but is not.
A BCS entry that matches a VVDS record was found, but the BCS entry was missing its required association cell.
A VSAM extension record indicates that the cluster is SMS-managed, but the associated cluster record indicates that the cluster is not SMS-managed, or vice versa.
Although a truename record was found for a component, the associated cluster record or component cell was not found.
The component cell for a VSAM cluster could not be found within the cluster's sphere record in the BCS.
Two VVRs for a VSAM component, or two NVRs for a non-VSAM data set, were found in the VVDS. Both records are displayed.
The catalog named in the VVDS record for an SMS-managed data set is not the system default catalog. (The default catalog is the catalog that is chosen for a data set when the catalog search is not being directed by the user.)
The storage class or management class names are not the same in the catalog and VVDS records. The catalog and VVDS records are displayed.
A volume cell that matches the volume serial number of the VVDS was not found. This may indicate an orphaned VVDS record or multiple VVDS records pointing to the same BCS.
An attempt to allocate the BCS named in the VVR failed.
An attempt to open the BCS named in the VVR failed.
An attempt to get a VVR/NVR record that matches the BCS record failed.
An attempt to get the specific VVR/NVR within the CI that matches the BCS record failed.
An attempt to get the entire VVDS record that matches the BCS record failed.
An attempt to get the specific VVR/NVR within the VVDS that matches the BCS record failed.
A Migration Cell was found in the BCS, but the VOLSER in the Volume Cell is not equal to 'MIGRATE'.
The alias entry shown contains reserved flags that are incorrectly set.
The VSAM data set is incorrectly defined.
Processing continues with another record.
Except for the reason codes listed below, use the following procedures to recover from these conditions:
If the names that disagree are not catalog names, and if the VVDS record is correct, remove the entries from the BCS by using the DELETE command with the NOSCRATCH option. Then use the DEFINE RECATALOG command to recatalog the data set.
If the VVR is incorrect, remove the data set by using the EXPORT command. At this point, you can import the data set using the IMPORT command with the desired NEWNAMES parameter.
DFSMSdfp
IDCDA02