TD Queue Intra Partition Configuration File

Previous Next JavaScript must be enabled to correctly display this content

3.10 TD Queue Intra Partition Configuration File

The following table 4‑8 lists and defines intra partitions TD queues available to the CICS application.

The filename is tdqintra.desc.

Table 3-8 TD Queue Parameters

Field Name	Type	Values	Description
`TDQUEUE`	`X(4)`	`Mandatory`	Specifies the 1- to 4-character name of a transient data queue.
`GROUP`	`X(10)`	`Mandatory`	The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
`DESCRIPTION`	`X(60)`	`Optional`	A small textual zone for description of the resource.
`RECOVSTATUS`	`X(8)`	`NO \| LOGICAL`	Specifies if the queue is logically recoverable or not. If a queue is logically recoverable, its elements will be written to tuxedo /Q in the context of the transaction and will be rolled back with the rest of the transaction in case of a rollback. If the queue is non-recoverable, then each enqueue in the /Q queue will be permanent and not rolled back in case of a rollback or abort.
`TRANSID`	`X(4)`	`Optional`	Specifies the name of the transaction that is to be automatically initiated when the trigger level is reached. Transactions are initiated in this way to read records from the queue. If the TRANSID attribute is not specified (or if TRIGGERLEVEL(0) is specified), you must use another method to schedule transactions to read records from transient data queues.
`TRIGGERLEVEL`	`X(1)`	`1 \| n`	Specifies the number of records to be accumulated before a task is automatically initiated to process them. (This number is known as the trigger level.) If you specify the TRANSID attribute, TRIGGERLEVEL defaults to 1. Specify a trigger level of 0 if you want to disable ATI processing. If you do not specify a transaction ID, the trigger level is ignored. For logically recoverable transient data queues, the ATI task is not attached until the task commits forward. This may mean that the trigger level is far exceeded before ATI occurs.
`USERID`	`X(8)`	`Optional`	Specifies the userid you want CICS to use for security checking when verifying the trigger-level transaction specified in the TRANSID field.
`WAIT`	`X(1)`	`YES \| NO`	INACTIVE field accepted only in the resource loading.
`WAITACTION`	`X(6)`	`REJECT \| QUEUE`	INACTIVE field Accepted only in the resource loading.
`QSPACENAME`	`X(15)`	`Mandatory`	New mandatory CICS Runtime argument, specifying the name of the tuxedo /Q QSPACE into which this queue is physically stored. Consult your Tuxedo /Q documentation for more information on qspaces and queue administration.
`TRT`	`X(1)`	`S \| I`	New optional CICS Runtime argument, allowing integrators and customers to make their own specific implementation of intra-partition queues. No value or S (for Standard) will invoke normal CICS Runtime TSQueue functionalities Setting the value I, will trigger the call to a function `td_intra_actions_int`, which must be provided by the integrator.
`ATIFACILITY`	`X(1)`	`T`	Indicates a `TERMINAL` when it is set to `T`.
`FACILITYID`	`X(4)`	`Optional`	The terminal name when `ATIFACILITY` is set to `T`.

Parent topic: CICS Runtime Configuration Files