You can override the automatically generated error messages
by 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. It is attached to the error message that
directly precedes it.
For Data Elements, the following line
types are possible:
- Type = F (Data Element
call). You can enter the Data Element directly in the Description field
or select it in the Link field
Table 1. Positions in the Description fieldPositions |
Contents |
1 - 6 |
Data Element |
- Type = U (error
message)
Table 2. Positions in the Description fieldPositions |
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 fieldPositions |
Contents |
1 - 5 |
Blank |
6 |
Comment |
Figure 1. Sample of an error message on a Data Element F NUCLI
U 2 CLIENT NUMBER IS REQUIRED
U 5 CLIENT NUMBER MUST BE > 10001
For Segments, the following line types are possible:
- Type = S (Segment
call). You can enter the Segment directly in the Description field
or select it in the Link field The Segment
that is displayed in the Description field
is in a read/write mode.
Table 4. Positions
in the Description fieldPositions |
Contents |
1 - 4 |
Segment |
5 |
Blank |
6 |
Category code (required if the same Segment
is used in several categories): - Screen-top: blank,
- Repetitive: R,
- Screen-bottom: Z.
|
7 |
Segment rank in the category (required if the
same Segment is used several times in a category). |
- Type = U (error
message)
Table 5. Positions in the Description fieldPositions |
Contents |
1 |
Use category of the Segment:
|
2 - 3 |
Blank |
4 |
Error type code - 8: Record found (invalid creation)
- 9: Record not found (invalid modification
or end of file. for example).
|
5 |
Blank |
6 |
Error message |
- Type = C (comments
on the error message)
Table 6. Positions
in the Description fieldPositions |
Contents |
1 - 5 |
Blank |
6 |
Comment |
Figure 2. Sample of an error message on a Segment 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 it is indicated here. 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 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.