As a general rule, the programs will not intentionally ABEND unless
a suspect program logic error is encountered that could make further
processing risky. The ABEND codes used are shown below with their
meanings.
- U0001 - An SMF record is being processed that is not a type 61/65/66
at a place in the logic where other record types should already have
been excluded.
Issued by module CRURRSV, CSECT CRURRSV.
- U0002 - Field SMFxxSUB in a type 61/65/66 SMF record is neither
'IN', 'DE', or 'UP'. This field should have been either supplied by
catalog management in the SMF record, or 'fabricated' by CRURRAP if
missing. There is no way to determine the correct disposition of the
record without this information. It is not sufficient to merely check
whether the record in question is a DELETE, ALTER, OR DEFINE record.
The pertinent question is which VSAM record management function is
represented by this SMF record: an insert of a new record, an update
of an existing record, or a delete. The record type (DEFINE, DELETE,
ALTER) is merely an indication of the type of request to catalog management.
For example, an IDCAMS DELETE could cause catalog record updates as
well as deletions.
Issued by module CRURRAP, CSECT CRURRAP.
- U0003 - A calculated sequence value used to index a table of sequence
values and sequence error values is greater than 16, the maximum acceptable
value.
Issued by module CRURRAP, CSECT CRURRAP.
- U0004 - One of the following errors occurred during logging:
- Calculated message table offset greater than 32, the maximum acceptable
value.
- SMF record to be logged is not type 61/65/66.
- Calculated action message table offset greater than 17, the maximum
acceptable value.
- Index value not found in action message table.
Issued by module CRURRAP, CSECT CRURRAP.
- U0005 - The program was unable to locate the data name cell in
a cluster record during 'fabrication' of the subtype field (SMFxxSUB).
This prevented determination of the correct disposition for the record.
See the discussion of ABEND U0002 above for more on the importance
of this field. This problem could be caused by either a logic error
in the program or a change in the format of catalog records.
Issued
by module CRURRAP, CSECT CRURRAP.