Actions on the UTM side

On the UTM side, you must make sure that UTM messages are actually sent to a queue from which they can then be retrieved by WebAdmin. This requires the following steps:

• Define messages with the message destination USER-DEST-1...4
  Specify the (additional) message destination USER-DEST-1 (or USER-DEST-2...4) for all messages that WebAdmin is to be able to retrieve. You can do this using the MODMSG statement and the UTM utility KDCMMOD.

• Create a new message module
  You can use the KDCMMOD utility to create a separate message module for the UTM application (on the basis of the file containing the MODMSG statements).

• Generate the separate message module
  If openUTM is to be able to use the created message module, you must generate it using the KDCDEF MESSAGE statement.

• Link the message destination USER-DEST-1...4 with a queue object
  This is done using the KDCDEF statement MSG-DEST. Here the NAME and DEST-TYPE parameters define the queue to which the corresponding UTM messages are to be sent. In the case of MSG-FORMAT, you should specify PRINT.

Example:
Source for KDCMMOD:
GEN SYS, LANG=D, MODULE=OWNMSG
*
MODMSG 036, COMPRESSION = NO, USER-DEST-1 = YES
ENDMSG
.
.
.
END

KDCDEF input:
MESSAGE LIB=$XYZ.OML.MSG, MODULE=OWNMSG
*
MSG-DEST USER-DEST-1, NAME=MSGQUEUE, DEST-TYPE=TAC, MSG-FORMAT=PRINT
*
TAC MSGQUEUE, TYPE=Q, QLEV=500, QMODE=WRAP-AROUND