About Transient Data Queues (TDQ)

Transient Data Queues (TDQs) that the region requires are set up when the region and file manager are set up.

Queue services describes how to you can use the CICS® Application Programming Interface (API) to queue data for subsequent internal or external processing. Selected data, specified in the application program, can be routed to or from predefined symbolic destinations, either intrapartition or extrapartition.

Destinations are intrapartition if associated with a facility that is allocated to the region; they are extrapartition if associated with an external destination. Extrapartition queues are ASCII files that are in the operating system's file structure. The external destinations of these queues must be defined in the Transient Data Definitions (TDD). Extrapartition queues are not managed by the file manager; they are accessed through EXEC CICS APIs.

Each CICS region requires three files for TDQs: one holds logically recoverable TDQ data, one holds physically recoverable TDQ data, and one holds nonrecoverable TDQ data. These files are placed onto the file manager that is specified with the Region Definitions (RD) DefaultFileServer attribute when the file manager is set up. If you use the procedures that are described in Working with a file manager in a CICS region, the files are given the required names, indices, and structure.

Table 1 lists the TDQ file and index names for a CICS region that is using an SFS server.

Table 2 lists the TDQ file and index names for a CICS region that is using DB2®.

Table 3 lists the TDQ file and index names for a CICS region that is using Oracle.