The WebSphere® Application Server for z/OS® optimized local adapters support has some Customer Information Control
System (CICS®)-specific installation and setup requirements.
Use this task to prepare your CICS environment to make
outbound calls to Enterprise JavaBeans
(EJB) applications that are deployed on your local WebSphere Application Server and to be the target of calls from applications that run on WebSphere Application Server.
Before you begin
If you need more information about CICS, see the CICS product documentation.
Procedure
- Add the CICS resource definitions for the WebSphere server to the CICS DFHSCD.
Run the copyZOS.sh OLASAMPS dataset_name script to copy out the OLA samples
and CSDUPDAT member to an MVS™ Partitioned Data Set (PDS). Then,
run the CSDUPDAT.jclsamp sample job to add the CICS resource
definitions for WebSphere Application Server to the CICS DFHCSD. Or, you can log on to CICS
and use the CEDA transaction, or equivalent, to define the WebSphere Application Server adapter task-related user exit (TRUE) program, WebSphere PLTPI, and new transaction identifiers for the
optimized local adapters.
- Add the optimized local adapters external modules data set to the CICS DFHRPL DD.
You need to add the data set that was created using the copyZOS.sh script and
place it in the CICS DFHRPL DD concatenation in your CICS JCL procedure.
The copyZOS.sh script is run when you enable your server environment to use
optimized local adapters. See the topic, Enabling your server environment for optimized local
adapters, for more information about running the copyZOS.sh script.
- Set up security.
If you are using RACF®, confirm that the job to define the
CBIND class to RACF for the target WebSphere server has run.
In a non-RACF System Authorization Facility (SAF) environment, execute the equivalent commands or
jobs that set up this support for the Independent Software Vendor (ISV) security product that you
use.
You must grant read access to the CBIND class for the WebSphere server to the CICS region user ID.
- Activate the optimized local adapters TRUE program.
Refer to the sample job located in the product HFS directory,
/<smpe-root>/mso/OLA/samples/DFHPLTOL.jclsamp which shows how to enable
the optimized local adapters TRUE exit during CICS startup.
The program added for this purpose is called BBOACPLT. Update the CICS startup parameters to specify to PLT suffix. Ensure that the data set created using the
copyZOS.sh script is included in the CICS
DFHRPL DD concatenation located in the CICS startup JCL.
If you do not want to add the Program List Table for Post Initialization (PLTPI), you can use the
BBOC transaction to activate the adapter TRUE program. When CICS is started, log on and issue BBOC START_TRUE to enable the exit and BBOC STOP_TRUE to
stop the exit. BBOC can also be invoked from a sequential (TYPE=SDSCI) terminal when CICS is started. Refer to the CICS documentation for more information about setting up and using sequential terminals during
CICS start up.
When CICS security is enabled, the user ID where the BBOC
START_TRUE and STOP_TRUE executes must have authority to issue EXEC CICS ENABLE PROGRAM(BBOATRUE) and DISABLE PROGRAM(BBOATRUE) EXITALL.
- Activate the optimized local adapters CICS Link
server in the CICS environment.
You must install the CICS Link transactions, BBO$ and
BBO#, that are provided by WebSphere Application Server as described in the
topic, Installing the WebSphere BBOC, BBO$ and BBO#
transactions in CICS.
When you issue BBOC_START_SRVR on a CICS terminal, the
optimized local adapters Link server task is activated.
- Restart the CICS region after these changes are
made, or, run the BBOC transaction to activate the WebSphere Application Server adapter TRUE program.
A new BBOC error message displays on the CICS BBOQ
extra-partition transient queue log (under DD BBOOUT) indicating that the optimized local adapters
support is ready for use.
- Set up workload management
(WLM).
Results
You have activated support for the optimized local adapters so that the CICS applications can begin to register and make calls using the optimized
local adapters APIs.