The message definition file defines the way in which openUTM issues standard messages, i.e. which text is used, which destination it is sent to, etc., together with constraints as to the extent to which they can be modified. If you wish to change these default characteristics, you must generate your own message module and link it to the UTM application.
The following changes may be made:
Adding or omitting message destinations (with KDCMMOD) as well as, for example, logging additional messages to STDERR or entry of the destination MSGTAC as a prerequisite for the use of an MSGTAC service.
Translating message texts into a different language and transferring them in the message definition file with the KDCMTXT tool ("Messages in other languages - the KDCMTXT tool").
Changing message texts with the KDCMMOD tool ("Generating a user-specific message module with KDCMMOD"), such as adding or removing (permitted) inserts to/from a message text, converting texts into lowercase/uppercase letters, etc.
Defining text constants. These can be used in many message texts. Control characters are also included here.
Individual modification of message output applies only to the corresponding UTM application. It has no effect on other UTM applications on the same computer and requires no changes to be made in the operating system.
You may only make modifications with the aid of the KDCMTXT and KDCMMOD tools.
The KDCMTXT tool should be used when translating all message texts into another language. If only a few texts are modified for a language contained in the message definition file, then the KDCMMOD tool can also be used.
Generation of a user-specific message module
A user-own message module must be generated with the KDCMMOD tool, see "Generating a user-specific message module with KDCMMOD". From the message definition file and a user-generated modification definition, KDCMMOD creates a C source program and an NLS source file. Compilation of this C program results in the application-specific message module which is linked to the program units of an application instead of the standard message module.
When compiling the user-own message module, specify the openUTM include directory utmpath/include.