After indicating errors or help messages in the -GE
Lines of Dialogs/Server Dialogs, or Screens/Servers (on
the Data Element -D Lines tab for the online
help on Data Elements), you must generate them. You can request the
generation from Dialogs or Server Dialogs only.
Before you begin
You must know whether a specific file must be used. The error
messages it contains will replace the standard messages displayed
for any input errors automatically detected from the controls specified
on the Segment
-CE Lines tab.
A specific
file is to be used only if the standard messages are not adapted to
the applications of the current repository.
There are five standard
messages for errors on Data Elements and three standard messages for
errors on Segments:
Figure 1. List of the standard messagesINVALID_ABSENCE_FOR_THE_FIELD = INVALID ABSENCE FOR THE FIELD
INVALID_PRESENCE_FOR_THE_FIELD = INVALID PRESENCE FOR THE FIELD
INVALID_VALUE_FOR_THE_FIELD = INVALID VALUE FOR THE FIELD
NON_NUMERICAL_CLASS_FIELD = NON-NUMERICAL CLASS FIELD
NON_ALPHABETICAL_CLASS_FIELD = NON-ALPHABETICAL CLASS FIELD
INVALID_CREATION_RECORD = INVALID CREATION RECORD
INVALID_DELETE_MODIFY_RECORD = INVALID DELETE/MODIFY RECORD
END_OF_LIST = END OF LIST
ABSENCE_OF_RECORD = ABSENCE OF RECORD
To specify a new specific file, you must create a file with
a
.properties extension and copy-paste the lines
above in it. Then overwrite the error messages (second part of each
line, after the '
=' sign) as needed.
About this task
To take the error messages indicated in the
-GE
Lines section of Dialogs or Screens or the online help
into account, you can generate them in two different ways:
Results
The generation generates the error messages in the file (with
a
.txt extension) you have indicated in the wizard.
You must then integrate this file into the error messages file used
by the applications. To do so, load into an indexed file or a DB2
database, or update this file. In both cases, you are responsible
for this integration process.