Text
Define message text
The Message Text File (MTF) function is most frequently used by technical personnel to set up system messages. Check with your system administrator before adding or changing your message text so you can make sure that your changes meet with your company's message standards.
To define message text, complete the following steps.
-
At a menu selection line, enter MTF and press Enter or select OK.Expected ResultResult: The Message Text form displays.
-
For Action, enter one of the following action codes you want to use.
-
To add a new record, enter A.
-
To change an existing record, enter C.
-
To delete an existing record, enter D.
-
To find a record, enter F.
-
To inquire on a specific record, enter I.
Expected ResultThe cursor goes to the next field. Press TAB to move from field to field or select any field you want to change.You can also press F1 to see a list of existing records. -
-
For Opt, enter 1 and press Enter or select OK.
-
For Action, if necessary, change the code.
-
For Message ID, enter a unique message ID.Step InformationNote:
-
If you are changing, deleting, or viewing the record, skip this field.
-
Message IDs consist of seven characters. The first three characters are alpha, followed by four numeric characters. Message IDs start with DCL. The final message found must not end with 00 because the MONMSG host command uses message IDs ending with 00 as a global monitor request.
-
-
For Severity Code, enter one of the following values.
-
Enter 00-19 for notification records that do not require a response.
-
Enter20-79 for error messages requiring immediate action and attention.
-
Enter 80-99 for urgent or catastrophic messages that may indicate potential production problems.
-
-
For Message Type, enter the one of the following codes that identifies the use case for the message and the type of action to take.
-
Enter *ABEND to indicate the program ended abnormally.
-
Enter *COMP to indicate the program ended normally.
-
Enter *EDTERR to indicate basic edit errors.
-
Enter *ERROR to indicate a general error.
-
Enter *FLDERR to indicate a field validation error using substitution date fields to identify a specific field name.
-
Enter *INFO to provide general information.
-
Enter *WARNING to provide the operator with warning information.
-
-
Optional. For System Code, enter one of the following codes to identify the software system to which the message applies.
-
Enter JDE to identify Enterprise as the software system to which the message applies.
-
Enter SEC to identify Security as the software system to which the message applies.
-
Enter SYS to identify System as the software system to which the message applies.
-
Enter TCR to identify Transaction Control and Routing as the software system to which the message applies.
Step InformationNote:In the System Code field, press F1 to view a list of valid codes. -
-
Optional. For Field name, enter the name to which the message applies.Step InformationNote:The Field name is a reference used with *FLDERR messages, and organizes messages for review.
-
For First level text, enter the text for the first level message.Step InformationNote:The First level text is the text that appears when the message displays. This text can be up to 78 characters in length.
-
For Second level text, enter any additional text you want users to see when they press the help key while the cursor is on a line containing first level text.Step InformationNote:This text can be up to 512 characters in length.
-
If the message uses substitution data, for Sub data length, enter the number and the length of the substitution data field and press Enter.Step InformationNote:A host message can use substitution data in message text, therefore, the system must know the number and lengths of each substitution data field. For example, a message requiring three substitution data fields consisting of a ten character name, a three character code, and a five digit number with zero decimal places would be 10 3 5.0.Expected Result
Result: The command in the Action field executes.
Loading...
There was a problem loading this topic