In addition to the message destinations, CONSOLE, SYSOUT etc., there are also four so called user-specific message destinations. The user can define up to four message destinations of their own. These message destinations are named using USER-DEST-number and may be user queues, TAC queues, asynchronous TACs or LTERM partners.
Messages indicating warning level violations cannot however always be delivered to their user-specific message destination.
The new KDCDEF statement, MSG-DEST, is used to agree the user-specific message destinations.
 | MSG-DEST statement in section "MSG-DEST - define user-specific messages destinations" |
msg-destination
Refers to the message destination with the specification USER-DEST-number (number=1..4). Message destinations must be assigned to the messages using the KDCMMOD.
NAME=
Specifies the name of a user or TAC queue or an asynchronous TAC or LTERM partner to which the messages are to be sent (this name must be defined using a TAC, USER or LTERM statement).
DEST-TYPE=
Type of message destination (USER queue, TAC or LTERM).
If you want to forward K and P messages from your application to the WinAdmin or WebAdmin administration workstation, you must specify a TAC queue or a USER queue here.
MSG-FORMAT=
Specifies the format of the messages that are to be sent. Only the inserts of a non printable format (FILE; default) or the inserts and messages texts of a printable format (PRINT) are transferred.
Assigning the message destination USER-DEST-number
Messages that openUTM is to output to a message destination, USER-DEST-number, must also be assigned to this message destination using the utility KDCMMOD (MODMSG statement).