Exploiting Open Transaction Environment (OTE)

The CICS®-DBCTL interface can be defined as threadsafe and CICS can run the CICS-DBCTL task-related user exit (TRUE) on an L8 open task control block (open TCB).

The open transaction environment (OTE) is supported in IMS™ version 12 with PTFs for APAR PM29194 applied and in IMS version 13 with PTFs for APAR PM29195 applied. Later releases of IMS require no PTFs. To activate IMS to use OTE, parameter OPENTHRD=CCTL needs to be specified in the DRA startup table (DFSPZP). If specified, then during connect processing CICS enables the CICS-DBCTL TRUE as an OPENAPI TRUE.

An open API TRUE is run on an L8 open TCB, which is dedicated for use by the calling CICS task. Running an application on an open TCB improves throughput and performance by reducing the use of the QR TCB. Threadsafe CICS applications that run on an L8 open TCB and use threadsafe CICS-DBCTL commands now avoid up to four TCB switches for each call to IMS. For more information about CICS IMS applications and the OTE, see Enabling CICS IMS applications to use the open transaction environment (OTE) through threadsafe programming.

If you do not specify OPENTHRD=CCTL, then CICS runs the CICS-DBCTL TRUE on the QR TCB and IMSDRA TCBs will be utilised.

When using IMS Version 12 or later with OPENTHRD=CCTL, you must change the way you calculate CICS and IMSprocessor times, for more information see, DBCTL monitoring data returned to CICS.



dfht45h.html | Timestamp icon Last updated: Monday, 5 June 2017