Transient Data Queue List (5.3.1)

Related Tpoics

The Transient Data Queue List screen is used to view a list of active CICS transient data queues. In addition to the transient data queue names, Code Debug CICS also displays:

Type of queue
Remote system ID
Indirect queue name
Status of the queue
Automatic transaction initiation (ATI) information.

Access this screen by typing the number 1 on the Transient-Data-Menu-5-3, typing 3.1 on the File-Utility-Menu-5, or as described in Transferring Between Screens.

Transient Data Queue List Screen (5.3.1)

-------------------------- TRANSIENT DATA QUEUE LIST (5.3.1) -------------C024
COMMAND ===>                                                   SCROLL ===> CSR
MODULE: CWDEMCB2 CSECT: CWDEMCB2          COMPILED: 28 MAY 2003 - 11.11.29

LINE COMMAND: S (Select)

      QUEUE            REMOTE INDIR           TRIGGER            ATI    ATI
SEL NAME     TYPE    SYSTEM NAME   STATUS    LEVEL    COUNT    TRAN   TERM
-------------------------------------------------------------------------------
_   CADL   INDIRECT          CSSL
  _   CADO   INDIRECT          CSSL
  _   CAFF   EXTRA                    ENA OPE
  _   CAIL   INDIRECT          CSSL
  _   CCPI   INDIRECT          CSSL
  _   CCSE   INDIRECT          CCSO
  _   CCSO   EXTRA                    ENA OPE
  _   CCZM   INDIRECT          CSSL
  _   CDBC   INDIRECT          CSSL
  _   CDB2   INDIRECT          CSSL
  _   CDUL   INDIRECT          CSSL
  _   CEJL   INDIRECT          CSSL
  _   CESE   EXTRA                    ENA OPE
  _   CESO   EXTRA                    ENA OPE
  _   CIEO   INDIRECT          CSS

Input Fields

SEL

Enter S in the field to display/update a single record from a queue with the Edit-Transient-Data-Queue-Record-5-3-2 screen.

STATUS

Status of extrapartition or intrapartition transient data queues. Authorized users can change these fields to open or close a queue, or disable or enable a queue. Valid entries are:

DIS: Disables access to the queue by CICS
ENA: Enables access to the queue by CICS
CLO: Closes the queue for access by CICS
OPE: Opens the queue for access by CICS.

Important

Authorized users can overtype the values using the first position of the request (for example, O for OPE, C for CLO).

Output Fields

QUEUE NAME

Name of the queue that can be accessed from the CICS system. Queues can be indirect, that is, point to another queue. In this case, the queue that is accessed is shown in the INDIR NAME field. An indirect queue can point to another indirect queue.

If the opened transient data queue is indirect to another queue, Code Debug CICS displays the indirect TO queue name. When you access the Edit-Transient-Data-Queue-Record-5-3-2 screen, Code Debug CICS follows the indirect chain to obtain the correct attributes of the target queue.

TYPE

Type of transient data queue. Valid entries are:

EXTRA: Extrapartition transient data queue that allows data storage in sequential data sets that are considered external to the CICS system. These queues allow users to write data to a sequential data set, then process the data by programs external to the CICS system, such as batch programs. With input queues, data created by programs external to the CICS system can be read and processed by programs in the CICS system.
INDIRECT: Indirect queue that allows the merger of several transient data queues into one physical destination.
INTRA: Intrapartition transient data queue that is held in one physical data set known to CICS. Intrapartition queues are used to transmit data from one program or task in the CICS system to another. This type of queue can also be associated with a transaction that processes the queue. When a preset number of records exists in the queue (trigger level), CICS automatically starts this transaction, and can then sequentially process the data in the queue. In addition, the transaction may be associated with a terminal, allowing different queues to be started at different terminals but use the same program.
REMOTE: Remote transient data queue that is processed by another CICS system. Requests for a remote queue cause CICS intercommunication facilities to start a task on the remote system to process the queue.

REMOTE SYSTEM

Name of the remote system if the queue resides in a remote CICS system.

INDIR NAME

Name of the queue if it is listed as INDIRECT or REMOTE in the TYPE field. The values depend on the queue type:

Indirect: Name of the queue that the input/output is directed from or to. The use of indirect queues allows several unique queues to actually process through one physical queue.
Remote: Name of the queue that is processed on the remote system.

ATI area

ATI fields are displayed for intrapartition transient data queues that use the CICS ATI facility. If specified by the system programmer, entries in this queue can cause CICS to automatically initiate processing of a program when the trigger level has been reached. The trigger level is a specified number of records in the queue that triggers CICS to automatically start program execution. The program then processes the records in the queue. The ATI area fields are:

TRIGGER LEVEL

The number of records in the queue required to have CICS initiate the transaction associated with the queue. See ATI TRAN field. If no value is displayed, the default of 1 is assumed.

COUNT

Current count of records in the queue.

ATI TRAN

Transaction code associated with this queue. This transaction automatically starts when the trigger level of the queue is reached.

ATI TERM

Terminal ID at which the ATI transaction is initiated. If blank, the ATI TRAN is started as a non-terminal task.