IRR62063I

Explanation
A segment count of zero was detected in an index
entry beginning at offset offset.  This is an incorrect
state in that all index entries should have one or more segments.

System action
Utility processing continues. A return code of
8 is issued.  BAM allocation errors (BAM=ALLOC ACTUAL=UNALLOC) are
flagged during MAP processing for valid entries in the block containing
the failing entry.
For index processing, statistics are not
compiled for the failing index block.  Validation continues with the
next index entry.
Map processing stops for the failing block.
 It continues with the next block.

Programmer response
A dump is provided for the index block in
error if INDEX was requested.  The offset of the index entry containing
the incorrect segment count is included in this message text. (If
only MAP processing was requested, running IRRUT200 another time requesting
INDEX FORMAT can help identify the block in which the error occurred.)
Determine whether it is easier to delete or correct this entry.  In
either case, see z/OS Security Server RACF Diagnosis Guide for
index entry formats.
If
it is decided that the entry should be deleted, do so by using the
BLKUPD command.  After deletion, MAP processing shows BAM allocation
errors (BAM=ALLOC ACTUAL=UNALLOC) for the BAM associated with the
deleted profile. These errors can be resolved by using the RACF® database utility (IRRUT400).
If
it is decided that the entry should be corrected, do so by using BLKUPD.
Upon
completion of index entry correction or deletion, IRRUT200 must be
run against the updated database to ensure complete validation.  IRRUT200
bypasses validation for index entries containing a zero segment count.
 Data block verification is bypassed during map processing for all
entries in the data block following the entry in error.