TRUEs and types of TCB used

A task-related user exit (TRUE) can run on the main CICS® QR TCB or an open TCB depending on the program attributes of the TRUE.

A Quasirent TRUE is enabled with the QUASIRENT option. Quasirent TRUEs are always invoked on the QR TCB instead of an open TCB. If a Quasirent TRUE is to invoke an external resource manager, it must manage its own set of subtask TCBs. Typically, the subtask TCB is posted to access the external resource manager, while the CICS task running on the QR TCB in the TRUE is put into a CICS dispatcher wait until the subtask completes its work. The CICS dispatcher wait allows the CICS dispatcher to dispatch another CICS task on the QR TCB in the meantime. The reason for this architecture is that external resource managers cannot be invoked directly by a caller on the QR TCB, because any operating system wait issued by the external resource manager would halt the QR TCB, and the whole of CICS.

A TRUE that is enabled with the THREADSAFE option will run on whatever TCB the task is running on at the time when the TRUE is invoked. This could be the QR TCB or an open TCB.

A TRUE that is enabled with both the THREADSAFE and OPENAPI options or with both the REQUIRED and OPENAPI options will always run on an L8 open TCB. A TRUE that is enabled with the REQUIRED but not the OPENAPI option will always run on a key 8 open TCB. This key 8 open TCB could be an L8, a T8, or an X8 open TCB, depending on the language of the calling application. For more information about open TCB modes, see Open TCB management.



true-tcb-type.html | Timestamp icon Last updated: Sunday, 4 June 2017