TAC queues

By generating transaction codes with TYPE=Q (queue) you define permanent Message Queues with fixed names.

The TAC queue with the fixed name KDCDLETQ is called the dead letter queue. openUTM uses this TAC queue to save queued messages sent to transaction codes, TAC queues, LPAP or OSI-LPAPM partners that can not be processed or delivered (see "TAC - define the properties of transaction codes and TAC queues").

TAC queues may be locked for reading or writing (see "Access list concept").

TAC statement in section "TAC - define the properties of transaction codes and TAC queues" The following operands are important for the generation of a queue defined using TAC statements:

• tacname

  Name of the TAC.

• TYPE=Q

  TYPE=Q must be specified for TAC queues. A Message Queue is generated. It is possible to use an FPUT or DPUT call to write a message to a queue of this nature, or to use a DGET call to read a message from the queue.

• ADMIN=

  Specifies whether access to this queue requires administration authorization.

• DEAD-LETTER-Q=

  Specifies whether queued messages in this message queue are to be saved in the dead letter queue if not processed correctly when the maximum number of attempts to redeliver the message (MAX statement, REDELIVERY parameter) has been reached.

• QLEV=

  QLEV can be used to ensure that the page pool is not overloaded by jobs for this TAC queue.
  QLEV specifies the maximum number of asynchronous messages that may be in the Message Queue of this transaction code.

• QMODE=

  Determines the behavior of openUTM in the event that the maximum permitted number of messages is already saved in a queue and thus the queue level is reached.

• Q-READ-ACL=

  The key set defines the authorizations that permit reading or deletion of messages in this queue.

• Q-WRITE-ACL=

  The key set defines the authorizations that permit writing messages to this queue.

• STATUS=

  Specifies whether the message queue is locked or released when the application is started.