The dead letter queue is made up of messages which could not be processed and which have not been redelivered. In order to process these messages after any errors have been corrected, they must be assigned either to their original destination or to a new destination.
DADM MA allows you to move multiple messages stored in the dead letter queue. The messages can be assigned to their original message queues or to a new destination of the same type (asynchronous TAC / TAC queue, LPAP partner, OSI-LPAP partner). If you specify a new destination, only the messages with the appropriate original destination (i.e. same type) are moved.
DADM MV allows you to move a single message from the dead letter queue. You must specify the job ID and the time at which the message was generated in order to identify the message.
To identify the destination, specify:
the TAC if the recipient of the messages with original destination TAC or TAC queue is to be an asynchronous program,
the name of a TAC queue if the recipient of the messages with original destination TAC or TAC queue is to be a service-controlled queue,
the name of an LPAP partner (but not a master LU61-LPAP) if the recipient of the messages with original destination LPAP is to be an LPAP partner,
the name of an OSI-LPAP partner (but not a master OSI-LPAP) if the recipient of the messages with original destination OSI-LPAP is to be an OSI-LPAP partner,
blanks if the messages are to be assigned to their original destination again.
If DADM MA is specified with KCLT=blank, messages whose destination no longer exists remain in the dead letter queue. You can assign these messages to asynchronous transaction codes or TAC queues as new destinations.
When moving messages from the dead letter queue, any QLEV that is defined and the STATUS of the recipient queue are ignored. This means that when moving messages, it is possible for the queue level to be exceeded and for messages to be sent to locked TACs.
The original destination of a message in the dead letter queue is available from the return information of the DADM RQ call.
|
|
