Creating Dialog explicit error messages

In the -GE Lines of a Dialog or Screen, you can create your own error messages for the errors that are described with specific code.

About this task

You must create explicit error messages if nonstandard errors are described with specific code. There are two types of explicit error messages: errors on Data Elements (related to a Screen), and user errors (related to a Dialog).

  • For the errors on Data Elements, you must create F lines followed by one or more U lines in the -GE Lines of the Screen. You can also specify comments on C lines.
    • F (Data Element call). You must select the Data Element in the Link column.

      You can click the Link column and click the button that is displayed in this column. It opens a selection wizard with all the available instances. Select the appropriate instance and click OK. The instance is then displayed in the Link column.

      You can also enter the name in the Link column. Place the cursor in the column and enter the name directly. To make the input easier, you can open a content assist wizard by clicking Ctrl and the space bar simultaneously. If you start entering a name, the content assist displays the instances that start with this input. If you enter the name of an instance that does not exist and if you validate, the input is discarded.

    • U (error message). You must conform to the following input format in the Description column.
      Table 1. Positions in the Description column
      Positions Contents
      1 - 3 Blank
      4 Error code (alphanumeric character except 0 and 1)
      5 Blank
      6 Error message
      Figure 1. Sample of an error message on a Data Element
         F NUCLI                                           
         U    3 THIS CLIENT NUMBER IS NOT AUTHORIZED       
         U    A THE TYPE DOES NOT CORRESPOND TO THIS CLIENT
      Note: The errors that correspond to such error messages must be indicated in the specific code with the ERR micropattern.
    • C (comments on the error message). You must conform to the following input format in the Description column.
      Table 2. Positions in the Description column
      Positions Contents
      1 - 5 Blank
      6 Comment
  • For user errors, you must create U line (error message) in the -GE Lines of the Dialog. You must conform to the following input format in the Description column.
    Table 3. Positions in the Description column
    Positions Contents
    1 - 4 Error code (specific code)
    5 Blank
    6 Error message
    Figure 2. Sample of an error message on a Dialog
         U AV01 DATE AND NATURE OF NOTICE MUST CORRESPOND 
    Note: The errors that correspond to these messages must be indicated in the specific code with the ERU micropattern.

What to do next

You must then generate the error messages. To do so, you must create an Error Message instance and associate it with the Dialog. The Error Message instance groups the generation options of the error messages for this Dialog. You must then generate the Error Message instance.


Feedback