Rational Developer for System z, Version 7.6

The batch error message file

The batch error message file contains records whose description is detailed below.

This file has the following physical characteristics:
Its records are constituted of the:
  1. Library code
  2. Entity type
  3. Instance code
  4. Error number
  5. Error type
  6. Line number
  7. Error gravity
  8. Error message
Example:
AP6AMB00 0035000EERRONEOUS VALUE FOR DATA ELEMENT DELAY
GCCHJIE0100054000ENON-NUMERIC CLASS DATA ELEMENT ACTION 
LU1IDO000116 002 009
Decoding this example::
  • Library code: AP6
  • Entity type: A
  • Instance code: MB00
  • Error number: 003 (rank - location on the Segment -CE Lines)
  • Error type: 5 (erroneous value)
  • Line number: 000
  • Error gravity: E
  • Error message: ERRONEOUS VALUE...
These are the possible values of each constituting element of the records:
Num. Position Meaning
1 3 Library code
2 1 Entity type:
  • A: For Data Structures or Segments (Batch error messages).
  • H: For Screens (online error messages).
  • I: Record reserved for internal use by the online function. It is used by the Help function to indicate the position of a field on a Screen, using a line / column formula.
3 6 Instance code
4 3 Error number:
  • For automatically generated error messages: it is the Data Element position (or sequence number) in the Segment or Screen.
  • For user-defined error messages: it is indicated with specific code.
5 1 Error type:
The following values are used by the system to flag erroneous conditions as specified in the control fields on the Segment or Screen Call of Elements (-CE Lines) for Data Elements:
  • 2: Invalid absence
  • 3: Invalid presence
  • 4: Erroneous class
  • 5: Erroneous value.

You can define other error types for non- standard controls. They must be inserted via specific code in control and update programs.

Documentary messages assigned to Data Elements are identified by the following values:
  • 0: Documentation located before Data Element Description information.
  • 1: Documentation located after Data Element Description information.
6 3 Line number:
This number is automatically managed:
  • 000: Error messages
  • 001-999: Documentary messages
Note: For a record with an I entity type, this number is automatically managed and contains the column number of the erroneous field on the Screen.
7 1 Error gravity:
You can control the value of this field in order to restrict transaction rejects.
Exemple:
  • W = Warning. Transaction accepted.
  • C = Caution, error.The Data Element is corrected, or its update is refused (the rest of the transaction is accepted).
  • E = Error. This error is not corrected. The transaction is rejected.

The value of this field is not standardly checked. All erroneous transactions are rejected.

8 30 Error message - First part:
For automatic error messages, this part of the message remains constant and is used to indicate the type of error:
  • 2: Invalid absence for the field
  • 3: Invalid presence for the field
  • 4: Non-numerical class field
  • 5: Invalid value for the field
For explicit error messages, this is the first part of the message indicated with specific code.
Note: For a record with an I entity type, this number is automatically managed and contains the column of the erroneous field.
9 36 Error message - Second part:

For an automatic error message, this is the name of the Data Element as defined in the Data Element Definition, or on the Segment Call of Elements (-CE Lines).

For an explicit error message, this is the seond part of the message indicated with specific code.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)