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
You need to reference the CICS information center for more
detailed information about using the CICS product.
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 exploit the optimized
local adapter APIs invoke the target stub routine. The target stub
routine invokes 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 SYNCPOINT call to CICS. For details on how this support
is used for propagation of transaction context to WebSphere Application Server, and two-phase commit, refer to the topic, WebSphere Application Server transactions BBOC, BBO$, BBO#.
Procedure
- Ensure that the load modules and DLLs that are required
for CICS are copied. All of the load modules and DLLs
that are required for CICS must be copied from the WebSphere Application Server HFS/zFS to a partitioned dataset for use under CICS.
The
load modules and DLLs are copied when you run the olaInstall.sh script
during product installation. For more information about how to run
the olaInstall.sh script, read the topic, Enabling the server
environment to use optimized local adapters.
- Place the resulting data set in the CICS DFHRPL concatenation.
You must be complete this step before the adapters can be activated
under CICS.
- All of the WebSphere Application Server 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.
- Start CICS to activate the adapters. A Program
List Table Post-Initialization (PLTPI) program is provided, that can
be used to automatically start the TRUE program during CICS startup.
If you 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 WebSphere Application Server modules under CICS
are routed to the BBOQ extra partition transient data queue (TDQ).
This is allocated under DD BBOOUT in the CICS region.
Results
You have activated the WebSphere Application Server transactions
in CICS.