CICSintermediate
Temporary Storage and Transient Data Queues
Understand CICS's two queuing mechanisms — temporary storage (TS) queues and transient data (TD) queues — and when each is the right tool.
CICS provides two distinct queuing mechanisms for temporarily holding data outside of a program's own working-storage, and interviewers ask about both together specifically because their similar-sounding names mask genuinely different purposes and access patterns — mixing them up is a common and telling mistake.
A TS queue is a shared corkboard where you can pin, re-read, and even swap out any numbered note at any time; a TD queue is a mail slot that automatically rings a bell (triggers a transaction) the moment enough letters pile up, and each letter is gone the moment someone actually reads it.
Key Concepts
1
Temporary Storage (TS) queues are general-purpose scratchpad storage, addressed by a queue name, holding an ordered series of numbered items that a program can write, read (by item number or sequentially), and rewrite — commonly used to pass data between tasks that aren't directly linked, to build up a multi-item scrollable list across separate pseudo-conversational screens (a classic 'page down through search results' pattern), or as lightweight temporary storage that outlives a single task without needing a full VSAM file.
2
Transient Data (TD) queues are more specialized: they're designed for sequential, mostly write-once/read-once processing, and are commonly used to trigger automatic follow-on processing — CICS can be configured to automatically start a designated transaction the moment data is written to a TD queue (a trigger level), making TD queues a natural fit for things like automatically kicking off a batch-like extract program once enough queued records accumulate, or serving as an error/logging queue (like the built-in CSMT queue used for CICS's own system messages).
3
A sharp interview distinction: TS queues are read-many, rewrite-capable, and addressed by item number for flexible access patterns (like scrolling through paged results); TD queues are essentially a FIFO pipe optimized for sequential processing and triggering downstream transactions automatically, not for arbitrary re-reads of arbitrary items.