Rational Developer for System z

Overriding the automatic error messages

You can override the automatically generated error messages be entering new messages in the -GE Lines subtab of the -G Lines tab.

About this task

Two line types must be described:

A Type = C is also possible for comments, attached to the error message which directly precedes it.

For Data Elements:
  • Type = F (Data Element call). You can click the icon in the Link field to select the Data Element code, which will then be automatically displayed in the Description field.
    Table 1. Positions in the Description field
    Positions Contents
    1 - 6 Data Element code
  • Type = U (error message)
    Table 2. Positions in the Description field
    Positions Contents
    1 - 3 Blank
    4 Number of the error type to be replaced for the Data Element:
    • 2 for an invalid absence,
    • 3 for an invalid presence,
    • 4 for an erroneous class,
    • 5 for an erroneous value.
    5 Blank
    6 Error message
  • Type = C (comments on the error message)
    Table 3. Positions in the Description field
    Positions Contents
    1 - 5 Blank
    6 Comment
    Example:
      F NUCLI                                           
      U    2 CLIENT NUMBER IS REQUIRED                  
      U    5 CLIENT NUMBER MUST BE > 10001              
For Segments:
  • Type = S (Segment call). You can click the icon in the Link field to select the Segment code, which will then be automatically displayed in the Description field, in a read/write mode.
    Table 4. Positions in the Description field
    Positions Contents
    1 - 4 Segment code
    5 Blank
    6 Category code (required if the same Segment code is used in several categories):
    • Screen-top: blank,
    • Repetitive: R,
    • Screen-bottom: Z
    7 Segment rank in the category (required if the same Segment code is used several times in a category).
  • Type = U (error message)
    Table 5. Positions in the Description field
    Positions Contents
    1 Use category of the Segment
    • F for reception
    • G for display
    2 - 3 Blank
    4 Error type code
    • 8: record found, (invalid creation)
    • 9: record not found, (invalid modification, end of file...).
    5 Blank
    6 Error message
  • Type = C (comments on the error message)
    Table 6. Positions in the Description field
    Positions Contents
    1 - 5 Blank
    6 Comment
    Example:
         S CD10                                            
         U F  8 PRODUCT REFERENCE NUMBER ALREADY ASSIGNED 
         U G  9 END OF SEARCH FOR THIS STATE                          
    Notes: You can replace an automatic error message on a single line, on the -GE Lines section. On a U-type line, the rank of a Data Element on the Screen Call of Elements (-CE Lines tab) must be entered in positions 1 - 3. The rank of a Segment on the Screen Call of Segments (-CS Lines tab) must be entered in positions 2 - 3.

    The rest of the Description field is entered as indicated above. This method implies specifying the error codes again when a Data Element is added to or deleted from the Call of Elements, or when a Segment is added to or deleted from the Call of Segments.

What to do next

You must generate the error message file.

Terms of use | Feedback

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