You create explicit (or user-defined) error messages in
the -GE Lines subtab of the Dialog or Screen -G
Lines tab.
About this task
You must create explicit error messages if you have described
non-standard errors 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).
- Errors on Data Elements
You must enter two types of lines: an
F-type
line, followed by one or more
U-type lines.
You can also specify comments on
C-type lines.
- Type = F (Data Element
call). You can enter the Data Element code directly in the Description field
or select it in the Link field
Table 1. Positions in the Description fieldPositions |
Contents |
1 - 6 |
Data Element code |
- Type = U (error
message)
Table 2. Positions in the Description fieldPositions |
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 corresponding to these messages must be indicted
in the specific code with the ERR micropattern.
- Dialog-related errors:
- Type = U (error
message)
Table 3. Positions in the Description fieldPositions |
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 which correspond to these messages must be indicated
in the specific code with the ERU micropattern.
What to do next
You must generate the error message file.