If you choose not to use the supplied standard message module containing English message texts, openUTM allows you to create your own customized message module. The information in the standard message module can thus be modified within certain limits simply by describing the changes with respect to the standard module.
The K messages K001 - K149, the P messages, and the U messages U101 - U250 as well as U301 - U340 can be modified.
Using your own message module for K and P messages you can
change the destinations of individual messages,
output messages at the console,
use a MSGTAC routine,
output user-written message texts, and
change the message texts, e.g. by translating them into another language.
For the U messages you can
output user-written message texts,
change the message texts, e.g. by translating them into another language,
change the destination of individual messages.
The destination SYSLOG is only possible for the following the messages:U182 to U200, U221 to U250, and U301 to U340.
With the KDCMMOD tool you can create your own message texts, and modify inserts and message destinations. Each insert allowed may only appear once in the message, however.
There is considerable scope for modifying the message texts but the length restrictions must be observed; see "Control statements for KDCMMOD". The available inserts are listed on section "Message inserts". It is possible to remove inserts from the message text that were specified in the standard text or include inserts in a message that were not specified in the standard text. In addition, it is possible to alter the sequence of the inserts within the text. Each insert may only appear a maximum of once in the message. The message numbers can also be moved to another place in the message text or even removed altogether. However, this should only be done in certain exceptional cases since it can make diagnoses on the basis of the messages more difficult.The message destinations can be modified within certain limits (see section “Destinations of UTM messages”). You should also note that different destinations may be required or prohibited for each message.
From the message definition file and your entries, KDCMMOD creates a C source file and an NLS source file each with the modified texts for the appropriate NLS catalog.
The KDCMMOD tool stores the corresponding generated C source program in the current directory, e.g. in the files ownmsgs.c (K and P messages) and kcxmsgs.c (U messages). Here ownmsgs and kcxmsgs denote the basic names of the corresponding message module specified in the GEN statement.
Example
GEN SYS,LANG=GB,MODULE=ownmsgs (for the english K and P message module)
GEN XPROG,LANG=GB,MODULE=kcxmsgs (for the english U message module)