IBM Support

TDQ triggering intermittently stops working when using pipeline devices in CICS

Troubleshooting


Problem

You have a intrapartition transient data queue (TDQ) defined in your CICS Transaction Server for z/OS (CICS TS) region with a non-zero TRIGGERLEVEL and ATIFACILITY equal to TERMINAL. The terminal is a 3600 pipeline device. When records are written to the TDQ it normally triggers the transaction but occasionally the triggering stops working.

Symptom

You do not receive any messages or abends. This seems to occur when there is a slowdown in the network that causes input from VTAM to queue up and CICS to receive a flood of work.

You take the terminal out of service but this does not fix the problem. You also try discarding and reinstalling the TDQ but the only thing that fixes the problem is reading the TDQ to QZERO.

In this particular case, a product from FDR was being used. Input was coming in on output only devices causing the TDQ to get backed up. CICS thought a transaction was triggered but the transaction was not in the region.

[{"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Transient Data","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"5.1;4.2;4.1;3.2;3.1","Edition":"","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
08 October 2025

UID

swg21179382

Page Feedback