After you modified the automatic error messages or added
explicit messages, you must generate them so that they get recognized
by the applications.
Before you begin
You must know whether a specific file must be used. The error
messages that it contains will replace the standard messages that
are displayed for any input errors that are automatically detected
from the controls 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 error 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
To specify a new specific file, create a file with a
.properties extension.
Copy and paste the lines of the standard error messages in this file. Then,
overwrite the error messages (second part of each line, after the
= sign)
as needed.
About this task
You must generate the batch error message file in the
following cases:
- You modified the automatic error messages by replacing them with
your own messages or by supplementing them with documentation,
- You added explicit error messages that correspond to errors described
with specific code.
You can generate this batch error message file in two different
ways:
- Enter an rpp --generateErrorMsgs command line from
a command prompt.
- Right-click a Data Structure in the Design Explorer view
and select . Enter the parameters
in the generation wizard that opens and click Finish.
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.