The following components of UTM event reporting are included in the delivery package:
Standard message module of openUTM
The standard message module contains the message texts in English and standard settings for the message destinations (e.g. terminals, SYSLOG file).
openUTM only generates the messages from the standard message module if no NLS message catalogs and no user message modules exist for a language.CAUTION!
The standard message module must be linked in each UTM application program.Unix and Linux systems
The standard message modules
kcsmsgs.o
(K and P messages) andkcxmsgs.o
(U messages) are supplied with openUTM on Unix and Linux systems:kcsmsgs.o
is contained in the librarylibwork
under the path utmpath/sys
.kcxmsgs.o
is reloaded from the librarylibxmsgs
under utmpath/sys
by default.
The expression “standard message module“ is used for both modules together.
Windows systems
The standard message modules
kcsmsgs.obj
andkcxmsgs.obj
(U messages) are supplied with openUTM on Windows systems:kcsmsgs.obj
is contained in the librarylibwork.dll
under the path utmpath/ex
.kcxmsgs.obj
is reloaded from the librarylibxmsgs.dll
under utmpath/ex
by default.
The expression “standard message module“ is used for both modules together.
Message definition file msgdescription (in the utmpath)
It contains the standard message texts in German and English, as well as the framework definitions for the UTM messages (structures of messages).
NLS standard message catalogs (Unix and Linux systems) / message DLLs (Windows systems)
NLS standard message catalogs are supplied with openUTM in German and in English.
On Windows systems the message catalogs are implemented as message DLLs.
The message catalogs only contain the message texts. When structuring the messages from an NLS catalog, openUTM uses the structure information and message destinations of the default message module, or if available, the user message module.
Unix and Linux systems
On Unix and Linux systems, the NLS standard message catalogs are stored in the directories utmpath
/nls/msg/
xxx. In this case, xxx is the language ID for the corresponding language.On Unix and Linux systems you can modify existing NLS message catalogs and create your own NLS message catalogs for other languages.
You can set the language to be used for the messages to your preferred language in the LANG shell variable.
Windows systems
On Windows systems, the message DLLs are stored in the directories
utmpath\nls\msg\
xxx.On Windows systems you can change the existing message DLLs and create your own message DLLs for other languages.
You can set the language to be used for the messages to your preferred language in the LANG shell variable.
In the simplest case, you operate your application with the standard UTM messages, i.e. you do not modify the UTM messages nor the UTM message destinations. In this case, no additional specifications are required in the KDCDEF generation. You must merely link the standard message module utm-directory/sys/kcsmsgs.o to the application program.
If you use an own message module, you have to define it via the KDCDEF statement MESSAGE when generating an application. This message module is then created using a C source file created by KDCMMOD.
MESSAGE statement in section "MESSAGE - define a UTM message module" |
MODULE=
Name of the module that is to be created using the tool KDCMMOD.
To modify the messages, use the message tools KDCMTXT and KDCMMOD (see openUTM manual “Messages, Debugging and Diagnostics on Unix, Linux and Windows Systems”).