Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

MSG-DEST - define user-specific messages destinations

This statement allows you to define up to four additional user-specific message destinations for the UTM messages.

For this purpose, openUTM provides the unoccupied UTM message destinations, USER-DEST-1, USER-DEST-2, USER-DEST-3 and USER-DEST-4. MSG-DEST allows you to assign these UTM message destinations to concrete destinations. These destinations may be:

  • a USER queue, or in other words, 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.

You can also assign several message destinations of the same type, for example, three LTERM partners and one USER queue. By defining the USER or TAC queue as the user specific message destination you can ensure that the UTM messages are output to the WinAdmin or WebAdmin administration workstation. More information can be found in the openUTM manual ”Messages, Debugging and Diagnostics” as well as in the online help of WinAdmin and WebAdmin, keyword „message collector“.

MSG-DEST

 msgdest 
 ,NAME=name
 ,DEST-TYPE={ LTERM | USER-QUEUE | TAC }
 [ ,MSG-FORMAT={ FILE | PRINT } ]

msgdest

Name of the UTM message destination to which you wish to assign a user specific message destination. Possible values are:

USER-DEST-1, USER-DEST-2, USER-DEST-3 or USER-DEST-4.

msgdest must also be assigned, using KDCMMOD, to the messages you wish to output to this user-specific message destination. For more information see section "User-specific message destinations" and the description of KDCMMOD in the openUTM manual ”Messages, Debugging and Diagnostics”.

NAME=

name

Name of the user-specific message destination. Possible values are:

  • Name of a UTM user ID. This must be generated in a USER statement.

  • Name of an asynchronous TAC. This must be generated in a TAC statement with TYPE=A.

  • Name of a TAC queue. This must be generated in a TAC statement with TYPE=Q.

  • BS2000 systems:
    Name of an LTERM partner. This must be generated in an LTERM application and may not be assigned to a PTERM with PTYPE=UPIC-R.

  • Unix, Linux and Windows systems:
    Name of an LTERM partner. This must be generated in an LTERM application and may not be assigned to a PTERM with PTYPE=UPIC-R or UPIC-L.

All messages that are linked via KDCMMOD to msgdest are then also output to the destination specified in name.

User-specific message destinations should not be locked or dynamically deleted because otherwise no more messages will be output at this destination.

DEST-TYPE=

Specifies the type of the message destination in name:

    LTERM

The message destination specified in name is an LTERM partner.

    TAC

The message destination specified in name is an asynchronous TAC or a TAC queue.

    USER-QUEUE

The message destination specified in name is a USER queue.

MSG-FORMAT=

Specifies the format in which the message is passed to the message destination.

    FILE

The format corresponds to the data structures for the MSGTAC program. So only message inserts without messages texts are passed, the message inserts are not converted to a printable format.

    PRINT

The format corresponds to the output format of the UTM tool KDCPSYSL. So the message is prefixed with the date and time, followed by the message text with the text inserts and additional inserts. All inserts are formatted printable.

KDCPSYSL is described in the openUTM manual “Using UTM Applications”.

Default: FILE