Creating a message module on Unix and Linux systems

Changing message texts

Since openUTM primarily prepares messages using the NLS catalogs, you must use the Unix/Linux system program gencat to generate an application-specific NLS catalog for each application:

• Call up gencat as follows:

  • Specify the NLS source file created by KDCMMOD as the input file.

  • Enter utmsys.cat as the NLS catalog name for K and P messages and utmxprog.cat for U messages.

• Provide these NLS catalogs under the directory filebase/nls/msg/lang.

Changing message destinations

If you have changed message destinations, you must carry out the following additional steps:

• Compile the relevant C source program (in the example ownmsgs.c and kcxmsgs.c) to create the user-specific message module ownmsgs.o and kcxmsgs.o.

• K and P messages: Link the ownmsgs.o object to the application program utmwork.

• U messages: Use the kcxmsgs.o object to generate the dynamic library with the fixed name libxmsgs.so. Provide this library under the directory filebase.

Examples can be found in the example application (utmsample) supplied with openUTM (Unix and Linux systems).

Note

To avoid unnecessary catalog accesses, an application-specific NLS catalog should contain all the messages. You should therefore copy the standard NLS catalog of the language you require to filebase/nls/msg/lang, use the KDCMMOD tool to create an NLS source file with the modified message texts, and merge this file into the application-specific NLS catalog.