![[z/OS]](../images/ngzos.gif)
Installing the WebSphere BBOC, BBO$ and BBO# transactions in CICS
You can install the WebSphere® Application Server transactions, BBOC, BBO$ and BBO#, to support optimized local adapters with the Customer Information Control System (CICS®) product. The system administrator must install and configure the transactions on CICS before the transactions are used. Then you can activate the optimized local adapters CICS Link server in the CICS environment.
Before you begin
About this task
The adapter is designed to run in a CICS region as a resource manager. In CICS, the Task Related User Exit (TRUE) is the primary vehicle used by resource providers. TRUE support provides the boundary between the CICS application threads and the external resource manager threads. Currently, DB2®, WebSphere MQ, and TCPIP sockets execute in CICS using the TRUE support. The optimized local adapters support TRUE.
Applications that run under CICS and use the optimized local adapter APIs invoke the target stub routine. The target stub routine starts the CICS DFHRMCAL support program and passes the name of the TRUE routine and the parameters. CICS dispatches the TRUE on one of the CICS maintained OPENAPI TCBs and executes until the API call completes. The call then goes back to CICS with the output parameters.
The CICS TRUE support also provides notification across transaction boundaries, such as when the application ends, abends, or issues an explicit sync point call to CICS. For details on how this support is used for propagation of transaction context to WebSphere Application Server, and two-phase commit, see the topic, WebSphere Application Server transactions BBOC, BBO$, BBO#.