Creating a message module on Windows systems

Changing message texts

As openUTM primarily prepares messages using message DLLs, you must use the UTM utility program KDCWMSG to create an application-specific message DLL for each application.

Proceed as follows:

• Call up KDCWMSG and specify the NLS source file created by KDCMMOD as the input file. KDCWMSG generates a Windows message text file.

• Compile this text file with the mc.exe program supplied with Microsoft Visual Studio and generate a message DLL.

  The name of the message DLL must be utmsys.dll for K and P messages and utmxprog.dll for U messages.

• Provide these message DLLs 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 modules ownmsgs.obj and kcxmsgs.obj.

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

• U messages: Use the kcxmsgs.obj object to generate a message DLL with the fixed name libxmsgs.dll. Provide this library under the directory filebase.

Examples can be found in the example application (QuickStartKit) supplied with openUTM (Windows 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.