Retrieve information about a transient data queue.
INQUIRE TDQUEUE >>-INQUIRE TDQUEUE(data-value)----------------------------------> .-----------------------------. V | >----+-------------------------+-+----------------------------->< +-ATIFACILITY(cvda)-------+ +-ATITERMID(data-area)----+ +-ATITRANID(data-area)----+ +-ATIUSERID(data-area)----+ +-BLOCKFORMAT(cvda)-------+ +-BLOCKSIZE(data-area)----+ +-DATABUFFERS(data-area)--+ +-DDNAME(data-area)-------+ +-DISPOSITION(cvda)-------+ +-DSNAME(data-area)-------+ +-EMPTYSTATUS(cvda)-------+ +-ENABLESTATUS(cvda)------+ +-ERROROPTION(cvda)-------+ +-INDIRECTNAME(data-area)-+ +-INDOUBT(cvda)-----------+ +-INDOUBTWAIT(cvda)-------+ +-IOTYPE(cvda)------------+ +-MEMBER(data-area)-------+ +-NUMITEMS(data-area)-----+ +-OPENSTATUS(cvda)--------+ +-PRINTCONTROL(cvda)------+ +-RECORDFORMAT(cvda)------+ +-RECORDLENGTH(data-area)-+ +-RECOVSTATUS(cvda)-------+ +-REMOTENAME(data-area)---+ +-REMOTESYSTEM(data-area)-+ +-REWIND(cvda)------------+ +-SYSOUTCLASS(cvda)-------+ +-TRIGGERLEVEL(data-area)-+ '-TYPE(cvda)--------------'
Conditions: ENDCOND, ILLOGIC, NORMAL, NOTAUTH, QIDERR
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The INQUIRE TDQUEUE command retrieves information about a particular transient data queue.
You define transient data queues to CICS using transient data resource definitions. There are two basic types: intrapartition and extrapartition. Intrapartition queues are managed and stored entirely by CICS, and are subject to automatic task initiation (ATI). ATI means that when the number of items on the queue reaches the value in the TRIGGERLEVEL option, CICS automatically creates a task to process the queue.
An extrapartition queue is an MVS sequential data set (or a spool file). Extrapartition queues are not subject to ATI, and consequently the associated options produce null values. Furthermore, if the data set is not open, CICS may not be able to determine some of the values, such as BLOCKFORMAT and RECORDFORMAT. Null values, explained in Null values, are returned in such cases.
Two other types of queue exist: indirect and remote, both of which point, eventually, to one of the basic types.
An indirect queue points to another queue on the same CICS system, and is essentially an alias for the other queue. When you name an indirect queue in an INQUIRE TDQUEUE command, CICS returns only the TYPE value (which is INDIRECT) and the name of the queue to which the indirect definition points (the INDIRECTNAME value). You need a second INQUIRE TDQUEUE against the INDIRECTNAME value to determine the characteristics of the underlying queue.
A remote queue is one defined on another CICS system. When you inquire about such a queue, the local CICS system returns only the information it maintains locally about the queue: the TYPE (REMOTE), the system on which it is defined (the REMOTESYSTEM value), its name there (REMOTENAME), and whether it is available to applications on the local system (its ENABLESTATUS).
You can also browse through the transient data queues defined in your system by using the browse options (START, NEXT, and END) on INQUIRE TDQUEUE commands. See Browsing resource definitions for general information about browsing, including syntax, exception conditions, and examples.
If the security manager is not active, the value returned is that of the default user ID and not any value that has been included in the installed definition.
If the system cannot find volume information for the data set on the DD statement, in the catalog, or passed with the data set from a previous step, the system assumes that the data set is being created in this job step. For a new data set, MOD causes the read/write mechanism to be positioned at the beginning of the data set.
This parameter overrides the WAIT option defined on the UOW’s transaction definition. See the CICS® Resource Definition Guide for an explanation of the interactions of in-doubt attributes on the TDQUEUE and TRANSACTION definitions.