Generating a user-specific message module with KDCMMOD

The KDCMMOD tool is available for generating a user-own message module. From the message definition file and a user-generated modification definition it creates an ASSEMBLER source program from which, after compilation, the application-specific message module is generated. This is linked to the program units present in an application.

An application-specific module is checked for validity by openUTM in the start phase and is then used additionally with the system message module.

In cases where the application-specific module cannot be accessed, the system message module is accessed instead (e.g. when terminating a UTM task). The system message module is present in the UTM system code.

Users can also create a number of their own message modules and link them into the application, but only one module can be the application-specific message module. The message module that acts as the application-specific message module is specified by means of the LOCALE parameter in the KDCDEF MESSAGE statement during UTM generation. This application-specific message module is also referred to as the standard message module. All other message modules are user-specific message modules. The message destinations are always taken from the standard message module.

You will find more information on this topic, e.g. how to link your own message modules with the application program, in the openUTM manual “Using UTM Applications on BS2000 Systems”.

The KDCMMOD tool stores the generated ASSEMBLER source program in the file 
SRC.ASSEMB.object-module-name, where object-module-name denotes the name of the message module specified in the GEN statement.

The following can be specified or modified:

• the natural language in which the messages are to be generated

• the fixed message texts

• the message destinations

• message attributes

• control characters.

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.