For messages created by UTM, UTM provides four further freely available message destinations that can be used to control administrative activities. These message destinations are referred to as USER-DEST-1, USER-DEST-2,
USER-DEST-3 and USER-DEST-4 and can be explicitly assigned the following objects:
a USER queue (the message queue of a user ID)
a TAC queue
an asynchronous TAC or
an LTERM partner that is not assigned to a UPIC client
These message destinations allow you to read messages in a TAC or USER queue, for example, via the KDCS program interface using the DGET function. By means of this function and corresponding follow-up processing you can design MSGTAC-like programs that respond specifically to a message.
By assigning a USER or TAC queue to a user-specific message destination you can, for example, output UTM messages at the WinAdmin or WebAdmin administration workstation (see the openUTM manual ”Messages, Debugging and Diagnostics” or the online help for WinAdmin/WebAdmin, keyword „message collector“).
The user-specific message destinations are configured by means of the generation statement MSG-DEST. You can obtain specific information on a message destination by means of the KC_GET_OBJECT statement and the KC_MSG_DEST_PAR object type.
You assign a message to a message destination by means of the KDCMMOD utility. The openUTM manual ”Messages, Debugging and Diagnostics” describes which messages can be assigned to the user-specific message destinations.
When a message occurs for which USER-DEST-n is defined as the message destination, UTM creates an asynchronous job to this message destination.
If the asynchronous job is rejected because, for example, the assigned object is disabled, the message is lost to the message destination. If there is another message for the message destination, openUTM tries again to create an asynchronous job for this message destination.
If an asynchronous TAC is assigned to a message destination USER-DEST-n, openUTM starts the program that is assigned to the TAC once for each message created. In contrast to the situation with MSGTAC, only one message can ever be read by means of FGET in a program run. In the KB header, KDCMSGUS is defined as the user and KDCMSGLT as the LTERM for this program unit run.