You can indicate error messages that correspond to errors
that are described with specific code.
About this task
You indicate explicit error messages for all the errors that
are triggered by nonstandard controls. You must perform the following
tasks:
- Describe these explicit error messages in the -GE lines of a Program
or a Macro. Since only two Programs containing error messages can
be associated with the transaction Data Structure, it is convenient
to define separate Programs (or Macros) just to contain these messages.
Using only one Macro to store the explicit error messages of an application
is advised.
- Associate the explicit error messages with the errors by using
the UT-UPR(n) user error table, which is generated
with the ERUT error variable. Error messages are
positioned according to the error number (example: 001 then 002).
To specify the adequate error message, you must use the instruction Move '1'
into UT-UPR(n), where n is the
error message number.
- Associate the error message Programs with the transaction file.
To do so, enter the Comment field of the Definition section
of the transaction Data Structure Overview tab
in the following way:
Table 1. Positions
in the Comment fieldPosition |
Content |
1 |
Blank |
2 |
E (required value) |
3- 8 |
First program with error messages |
9 - 14 |
Second program with error messages |
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 Data Structure. The Error Message instance groups the generation
options of the error messages for this Data Structure. You must then
generate the Error Message instance.