With tacdadm INFORM you can display information about message queues. UTM always provides the following items of information about individual messages in the queue:
the job ID which you require, for example, when deleting a message
the user ID with which the message was generated
the time at which the message was generated
with time-driven messages, the start time as of which the message should be processed
information as to whether a positive or negative confirmation job belongs to the message.
In detailed information mode (LIST=LONG), openUTM also provides user information written with DPUT NI.
The lists containing the information returned by openUTM can be very extensive in some instances. For this reason, you have the options of:
rerouting the output to a printer (OUT)
restricting the output by specifying the job ID of the message at which the output list should start. The lists should be in ascending order of job ID. When you enter a job ID in CONT, the list starts with this message. No information is then provided about messages whose job ID occurs earlier in the alphabetic list.
tacdadm
INFORM
,DESTINATION=destination
[ ,CONT=dputid ]
[ ,DEST-TYPE = { LTERM | TAC | USER | QUEUE } ]
[ ,LIST={ SHORT| LONG } ]
[ ,OUT={ KDCDISP | ltermname } ]
INFORM | Summary list of which messages in a message queue are to be Output. | |
DESTINATION=destination | ||
Name of the recipient of a message about which openUTM is to provide information. destination specifies the message queue. For destination you must specify the name of a TAC, an LTERM partner, a user ID or the name of a temporary queue. | ||
DEST-TYPE= | Specifies the type of the recipient (destination).Possible entries are: | |
LTERM or TAC | The recipient is a TAC, a TAC queue or an LTERM partner. | |
USER | The recipient is the queue of a user ID. | |
QUEUE | The recipient is a temporary queue. | |
CONT=dputid | Controls the scope of output. For dputid you can enter the job ID of the message with which the list of information is to start. The list only contains information about messages whose job ID occurs later in the alphabet than dputid and about the message with the job ID specified in dputid. | |
LIST= | Specifies the scope of information which openUTM is to output. | |
SHORT | The user information generated with DPUT NI is not output at the same time. | |
LONG | The user information written with DPUT NI is not output at the same time. Default: SHORT | |
OUT= | Indicates where openUTM is to output the information. | |
KDCDISP | openUTM outputs the information to the terminal at which the information was requested or openUTM passes the information to the client which requested the information. | |
ltermname | openUTM outputs the information to a printer. For ltermname , enter the name of the LTERM partner assigned to the printer. |
Result
For LIST=SHORT
User-id DPUT-id Gen-time Start-time Pos/Neg Dest. user1 dput-id time1 time2 p/n/p n dest1
Key to terms:
User-id | User ID or “*NONE“, if the user who generated the message has been deleted. |
DPUT-id | Job ID of the message |
Gen-time | |
| Time when the message was generated. Enter time in the following manner: |
Start-time | |
This is output only for time-driven messages (DPUT messages). | |
Pos/Neg | Specifies whether a positive or negative confirmation job exists. The display field contains a “p” if a positive confirmation job exists and an “n” if a negative confirmation job exists. “p n” indicates that both a positive and a negative confirmation job exist. |
Dest. | Recipient of the message. For the dead letter queue, the original destination of the message is specified here, i.e. the name of an asynchronous TAC, a TAC queue, a LPAP partner or an OSI-LPAP partner. Otherwise, the field is empty. |
For LIST=LONG
In addition to the information output for LIST=SHORT, the first 79 bytes of user information are output (in the next line - DPUT NI message). The following information appears on the output:
User-id DPUT-id Gen-time Start-time Pos/Neg Dest. user dput-id time1 time2 p/n/p n dest1 User info: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx