CICS TSQ are task independent why you need

Temporary storage provides a means for storing data records in queues. Like files these records are identified by a unique symbolic name. Temporary storage queues do not have to be predefined to CICS. So these are called Temporary storage queues. Like scratch pad memory. You can read top 27 CICS interview questions here.

CICS TSQ concept
Stockphotos.io

Temporary storage queues are not directly attached to a task. This means that temporary storage queues are task independent. Once a temporary queue is written, it remains intact after the the task that created it has been terminated.

The popular commands in TSQ

  • The WRITEQ TS command allows you to write records to a temporary storage queue. IF the queue exists with this command is issued, one will be created and the records will be written to it.
  • The READQ TS command allows you to read records, either sequentially or randomly from a temporarily storage queue.
  • Records in a TSQ can be updated and even re-written even by using the REWRITE option of the WRITEQ TS command
  • The DELETEQ TS command allows you to delete an entire TSQ. Individual records cannot be deleted
  • The queue name specified in TSQ must not exceed eight characters in length

Also read: How to modify VSAM file properties in CICS

The sample code for TSQ

WRITEQ TS QUEUE (queue name)
FROM (data area)
LENGTH (data value)
ITEM (data area)
MAIN/AUXILARY
SYSID (name)

READQ TS QUEUE (queue name)
INTO  (data area)
LENGTH (data value)
ITEM (data area)
NUMITEMS (data area)
SYSID (name)

WRITE TS QUEUE (queue name)
FROM  (data area)
LENGTH (data value)
ITEM (data area)
MAIN/AUXILARY
SYSID (name)

DELETEQ TS QUEUE (queue name)
SYSID (name)

Advertisements

Author: Srini

Experienced software developer. Skills in Development, Coding, Testing and Debugging. Good Data analytic skills (Data Warehousing and BI). Also skills in Mainframe.

Comments are closed.