The daily edition.

Scope: Rocket Enterprise Server 12.0, using the Enterprise Developer 12.0 for Eclipse UNIX manual (Linux/UNIX).

An intrapartition transient data queue can automatically start a transaction when enough records have accumulated. This is useful when processing should begin at a defined record count: the queue definition identifies both the threshold and the transaction to run. In DEFINE TDQUEUE, these controls are TRIGGERLEVEL and TRANSID, and they apply to intrapartition queues. DEFINE TDQUEUE

The distinction between queue types matters. Intrapartition queue contents are temporary and accessible only to transactions. Extrapartition queues exchange data with non-CICS programs; indirect queues are aliases pointing to another queue. The automatic transaction controls belong to the intrapartition definition, so choosing a destination type is part of configuring the processing mechanism. DEFINE TDQUEUE

Rocket provides this concrete definition in its manual:

DEFINE TDQUEUE(D010) GROUP(SAMPGRP)
DESCRIPTION(Sample intrapartition DCT)
       TYPE(INTRA) RECOVSTATUS(NO) TRANSID(TTAB) TRIGGERLEVEL(25)

Here, D010 accumulates 25 records before the specified transaction, TTAB, is run. The same definition explicitly selects non-recoverable operation with RECOVSTATUS(NO). Triggering and recovery are therefore separate choices in this documented example. DEFINE TDQUEUE

In ESCWA, the Transient Data Queue page exposes the equivalent settings under Intra-Partition Triggering: enter the transaction name and the record-count trigger level, whose maximum is 32767. A configured terminal must already be defined to MSS. Use Apply to save changes and Install to install the resource. Crucially, leaving the transaction unspecified or setting the trigger level to zero means another mechanism must schedule the transactions that read the destination. Zero does not mean “start immediately.” Transient Data Queue

Recovery adds a separate prerequisite. The ESCWA Recoverable control concerns abnormal termination of MSS or the transaction processing the destination, and only takes effect for an intrapartition queue. The command reference further specifies that RECOVSTATUS(PHYSICAL) and RECOVSTATUS(LOGICAL) are synonymous here; either recoverable setting also requires _FILESHAREID, because MSS recovery is handled by Fileshare. Transient Data Queue DEFINE TDQUEUE

For operational inspection, the Active Transient Data Queue page displays the destination type, recoverability, trigger item count, transaction, and terminal, and offers a DCT dump. These expose the queue’s processing and recovery settings together. Active Transient Data Queue

Takeaway: Configure the transaction and a nonzero trigger count for automatic initiation; configure recoverability and its Fileshare dependency separately. DEFINE TDQUEUE