+

Search Tips   |   Advanced Search

(ZOS) Install the WebSphere BBOC, BBO$ and BBO# transactions in CICS

We 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 we can activate the optimized local adapters CICS Link server in the CICS environment.

We must reference the CICS Information Center for more detailed information about using the CICS product.

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, IBM 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 WAS, and two-phase commit, see the topic, WAS transactions BBOC, BBO$, BBO#.


Tasks

  1. Ensure that the load modules and DLLs required for CICS are copied. All of the load modules and DLLs required for CICS must be copied from the WAS HFS/zFS to a partitioned data set for use under CICS.

    The load modules and DLLs are copied when running the copyZOS.sh script during product installation. For more information about how to run the copyZOS.sh script, read the topic, Enabling the server environment to use optimized local adapters.

  2. Place the resulting data set in the CICS DFHRPL concatenation. We must be complete this step before the adapters can be activated under CICS.
  3. All of the WAS programs running under CICS are reentrant, reusable, and thread-safe, and defined with the concurrency parameter set to threadsafe. For use under CICS, they can be placed in a logical partition with the UseLPACopy program property set to yes.

  4. Start CICS to activate the adapters. A Program List Table Post-Initialization (PLTPI) program is provided, used to automatically start the TRUE program during CICS startup. If we do not use the PLTPI, a CICS transaction, BBOC, is provided. This transaction can be used to start, stop, enable, and disable tracing for the TRUE module. The TRUE program name is BBOATRUE, which is activated using the BBOC transaction with the START_TRUE parameter.

    When CICS security is enabled, the user ID where the BBOC START_TRUE and STOP_TRUE parameters run must have authority to issue EXEC CICS ENABLE PROGRAM(BBOATRUE) and DISABLE PROGRAM(BBOATRUE) EXITALL. Messages issued by WAS modules under CICS are routed to the BBOQ extra partition transient data queue (TDQ). This is allocated under DD BBOOUT in the CICS region.

We have activated the WAS transactions in CICS.


Subtopics


Related:

  • Optimized local adapters on WAS for z/OS
  • Optimized local adapters for z/OS APIs
  • Planning to use optimized local adapters for z/OS
  • Enable the server environment to use optimized local adapters
  • WAS transactions BBOC, BBO$, BBO#