Message Module, Message Definition File

The message definition file utm-path/msgdescription and the two standard message modules kcsmsgs (K and P messages) and kcxmsgs (U messages) are supplied with openUTM.

kcsmsgs and kcxmsgs are located in the following directories/libraries:

Unix and Linux systems:

• kcsmsgs.o is contained in the library libwork under the path utmpath/sys.

• kcxmsgs.o is loaded from the library libxmsgs under utmpath/sys by default.

Windows systems:

• kcsmsgs.obj is contained in the library libwork.dll under the path utmpath\ex.

• kcxmsgs.obj is loaded from the library libxmsgs.dll under utmpath\ex by default.

The standard message modules contain the English message texts and the default settings for the message destinations (e.g. terminal or SYSLOG file). The message definition file is used as an input file if the user wishes to change the UTM messages. It contains message texts in both English and German and the framework definition of the messages (structure of the messages).

In the following description, the common term “standard message module” will be used for both standard message modules.

The message definition file can be expanded with message texts in other languages. Users can translate the message texts and enter them in the message definition file with the tool KDCMTXT (see "Messages in other languages - the KDCMTXT tool"). From the message definition file users can use the tool KDCMMOD (see "Generating a user-specific message module with KDCMMOD") to create your own message module.

CAUTION!

You may only use the UTM tools KDCMTXT and KDCMMOD to process the message definition file msgdescription! Any other write access, such as with an editor will destroy this file!

When a message is output, openUTM accesses the UTM message module. Among other things this contains the following for each message:

• the message number Knnn, Pnnn or Unnn

• the message text

• the message destinations

• the inserts

A particular type of message output is specified in the standard message module. Users who wish to change these must generate their own message module. 
If there are no NLS message catalogs for openUTM and no user-specific message module, openUTM generates the messages from the standard message module.

The standard message module must be linked into each UTM application program, i.e. even if you are using NLS message catalogs or your own message module.