IDC21364I ERROR DETECTED BY DIAGNOSE: {VVDS|ICFCAT} ENTRY: `entry` RECORD: `rec` OFFSET: `offset` REASON: `reason-code`

For BCS Entries:

Explanation
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.
In
the message text: entry
The entry name. The entry name is followed by a character which
indicates the entry type. See z/OS DFSMS Managing Catalogs for
an explanation of the entry types.
rec
The record in which the error occurred. If the record name is
followed by a number greater than X'00', the record is an
extension record.
offset
The offset into the record at which the error was found.
reason-code
The reason code, as follows: Code
Explanation
1
CELL LENGTH IS ZERO 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.

2
CELL TYPE NOT RECOGNIZED 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.

3
RECORD TYPE NOT RECOGNIZED Each record in a BCS or VVDS has
an record type. The record named has an invalid type for integrated
catalog facility catalogs.

4
UNEXPECTED RECORD ID ENCOUNTERED 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.

5
COMPONENT LENGTH IS ZERO 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.

6
CELL LENGTH TOO LARGE A cell length was found that is inconsistent
with component or record length. This may describe the cell being
processed or the preceding cell.

7
CELL LENGTHS SUM AND COMPONENT LENGTH DISAGREE 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.

8
REPEATING CELL NOT VALID 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.

9
RECORD LENGTH INCORRECT The record length at the front of the
record is not the same as the length stored by VSAM record management.

10
INCOMPLETE EXTEND DETECTED The EXTEND function did not execute
to completion. The named entry was interrupted in the middle of an
EXTEND/EOV operation.

11
INCOMPLETE DELETE DETECTED The DELETE function did not execute
to completion. This may indicate existence of partial record structures
in the BCS.

12
CATLG AND VVDS NAMES UNEQUAL There are four name fields in
a VVDS record. The BCS entry and the VVDS entry do not have precisely
the same names (length fields must also be the same) for one of the
following four fields: Record name
Subrecord name
Component name
Catalog name

13
VVDS AND VTOC EXTENT SEQ. NO. UNEQUAL 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.

14
CATLG AND VVDS VOLFLG UNEQUAL 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.

15
CATLG AND VVDS KEYS UNEQUAL BCS and VVDS records both have
high and low key fields. The fields and their lengths must be equal;
they were not.

16
VVDS AND VTOC STARTING CCHH UNEQUAL The extents in the VTOC
DSCB and VVDS record were compared. They were not equal, although
they should be.

17
VTOC ENTRY NOT FOUND The data set control block (DSCB) for
the named entry could not be found in the VTOC.

18
VVDS ENTRY NOT FOUND There should be a VVDS entry for this
BCS entry, but one could not be found.

19
CATLG ENTRY NOT FOUND The BCS should have an entry for the
VVDS record, but one could not be found.

20
ASSOCIATION NOT 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.

21
ASSOCIATION LOOP FAILURE 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.

22
TRUENAME NOT FOUND 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.

23
TRUENAME LOOP FAILURE The truename entry for a cluster did
not point back to the cluster record.

24
REQUIRED CELL MISSING, CELL TYPE type Depending
on the component or entry type, certain cells are required. The cell
type indicated is required, but missing. 

25
ALLOCATE OF COMPARE DATA SET FAILED The BCS named in the VVDS
record could not be allocated.

26
CELL TYPE INVALID IN CONTEXT The indicated cell is a valid
cell type, but it is not valid for the type of entry being scanned.

27
ENTRY MISSING FROM GAT CELL 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.

28
GAT CELL ENTRY NOT FOUND 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.

29
ENTRY MISSING FROM REL CELL 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.

30
REL CELL ENTRY NOT FOUND An entry in a REL ("relation")
cell in a cluster record does not represent an alternate index entry. 

31
OPEN OF COMPARE DATA SET FAILED The BCS named in the VVDS record
could not be opened.

32
WRONG RECORD TYPE A BCS record which matches a VVDS record
was found, but the BCS record is not a cluster, truename, or non-VSAM
record.

33
INCOMPLETE UPDATE DETECTED The current entry was undergoing
a subrecord update/move operation that did not complete. This record
or subrecord may be damaged.

34
VVDS AND VTOC ENDING CCHH UNEQUAL The extent information kept
in the VTOC and VVDS should agree, but do not.

35
VVDS AND VTOC EXTENT COUNTS UNEQUAL The extent information
kept in the VTOC and VVDS should agree, but do not.

36
LENGTH OF NAME INVALID The length of a name cell should be
from 1 to 45 characters long, but is not. 

37
ASSOCIATION NAME CELL NOT FOUND A BCS entry that matches a
VVDS record was found, but the BCS entry was missing its required
association cell.

38
CLUSTER AND EXTENSION RECS SMS MISMATCH 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. 

39
BASE OR COMPONENT CELL NOT FOUND Although a truename record
was found for a component, the associated cluster record or component
cell was not found.

40
COMPONENT CELL NOT FOUND The component cell for a VSAM cluster
could not be found within the cluster's sphere record in the BCS.

41
DUPLICATE VVR/NVRS IN VVDS Two VVRs for a VSAM component, or
two NVRs for a non-VSAM data set, were found in the VVDS. Both records
are displayed.

42
NONSYSTEM DEFAULT CATALOG NAME IN VVDS 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.)

43
CATALOG AND VVDS SMS CONSTRUCTS UNEQUAL The storage class or
management class names are not the same in the catalog and VVDS records.
The catalog and VVDS records are displayed. 

45
VOLUME CELL NOT FOUND 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.

46
VVDS ENTRY NOT FOUND.  ALLOCATION ERROR. An attempt to allocate
the BCS named in the VVR failed.

47
VVDS ENTRY NOT FOUND.  DATA SET OPEN ERROR. An attempt to open
the BCS named in the VVR failed.

48
VVDS ENTRY NOT FOUND.  GET RECORD FAILED. An attempt to get
a VVR/NVR record that matches the BCS record failed.

49
VVDS ENTRY NOT FOUND.  SCAN RECORD FAILED. An attempt to get
the specific VVR/NVR within the CI that matches the BCS record failed.

50
VVDS ENTRY NOT FOUND.  GET VVDS FAILED. An attempt to get the
entire VVDS record that matches the BCS record failed.

51
VVDS ENTRY NOT FOUND.  SCAN VVDS FAILED. An attempt to get
the specific VVR/NVR within the VVDS that matches the BCS record failed.

52
INVALID VOLSER FOR MIGRATION CELL. A Migration Cell was found
in the BCS, but the VOLSER in the Volume Cell is not equal to 'MIGRATE'.

53
RESERVED BITS SET IN CATALOG ALIAS ENTRY. The alias entry shown
contains reserved flags that are incorrectly set.

54
EXTENT AMOUNT IS NOT A CA MULTIPLE.The VSAM data set is incorrectly
defined.

System action
Processing continues with another record.

Programmer response
Except for the reason codes listed below,
use the following procedures to recover from these conditions:
For
BCS Entries: Use DELETE NOSCRATCH to remove the sphere or base record, if it
exists.
Use DELETE TRUENAME to remove any remaining association records.
Reintroduce the removed entries into the catalog, by recataloging
or redefining them. Introduce generation data sets into the generation
data group in the proper order.

For VVDS records: Use DELETE NOSCRATCH to remove the entries from the BCS, if they
exist.
Use DELETE VVR or NVR to remove the damaged VVDS records.
Restore the data set from a backup copy.

For the following reason codes, recover as indicated: Code
Action
10
You should recover the data set. Records existing in a data set
prior to the aborted extend operation should still be accessible if
the data set is opened for input only. You can retrieve these records
by using the REPRO command. After you retrieve the records, you can
delete or redefine the data set. Then reinsert the records by using
the REPRO command.
11
You can finish the deletion process by rerunning the DELETE job.
12
If the catalog names disagree, remove the entries in the BCS by
using the DELETE command with the NOSCRATCH option. At this point,
if the VVDS record contains the desired catalog name, you can catalog
the data set into the desired BCS by using the DEFINE RECATALOG command;
otherwise, catalog the data set into the catalog indicated in the
VVDS record. (It will be necessary to define this catalog if it does
not exist.) Then move the catalog record to the desired catalog by
using the REPRO MERGECAT command. 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.

25
Check for OPEN or allocation error messages to determine the source
of the problem.
31
Check for OPEN or allocation error messages to determine the source
of the problem.
38
Delete the cluster entry with DELETE NOSCRATCH, and recatalog
it with DEFINE RECATALOG. Then rebuild the alternate index with DEFINE
ALTERNATEINDEX and BLDINDEX.
41
Delete the data set. Then use DELETE VVR or NVR to delete the
duplicate VVDS record. Recover the data set from a backup copy.
42
Use REPRO MERGECAT to move the data set's catalog entry to the
correct catalog.
43
Use DELETE NOSCRATCH to delete the BCS record, and DEFINE RECATALOG
to recreate the BCS record. The storage class and management class
may be changed with ALTER if they are incorrect.
45
Delete the orphaned or extra VVDS records.
46
Determine if the BCS named in the VVR is valid.  If necessary,
see z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
47
Determine if the BCS named in the VVR is valid.  If necessary,
see z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
48
Determine whether the BCS entry or the VVR/NVR entry is in error.
See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
49
Determine whether the BCS entry or the VVR/NVR entry is in error.
See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
50
Determine whether the BCS entry or the VVR/NVR entry is in error.
See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
51
Determine whether the BCS entry or the VVR/NVR entry is in error.
See z/OS DFSMS Managing Catalogs for
the appropriate recovery procedures.
53
Delete and redefine the alias entry to correct the problem.
54
DELETE and redefine the VSAM data set. If the problem persists,
contact IBM® Service.

Source
DFSMSdfp

Module
IDCDA02

IDC21364I ERROR DETECTED BY DIAGNOSE: {VVDS|ICFCAT} ENTRY: entry RECORD: rec OFFSET: offset REASON: reason-code

Explanation

System action

Programmer response

Source

Module

IDC21364I ERROR DETECTED BY DIAGNOSE: {VVDS|ICFCAT} ENTRY: `entry` RECORD: `rec` OFFSET: `offset` REASON: `reason-code`