The WebSphere® Application Server for z/OS® optimized local adapters support
has Information Management System (IMS™)-specific
installation and setup requirements. Use this task to prepare your IMS 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 the Application Server.
Before you begin
If you need more information about IMS, see the IMS product information center.
About this task
Procedure
- Create an external subsystem IMS procilib
member or update your existing member. Include the following
entry in this new proclib member:WOLA,BBOA,BBOAIEMT
When
this entry is activated, it results in a new external subsystem with
the name WOLA defined to IMS.
The language interface token is BBOA and the external subsystem table
module is called BBOAIEMT. The name subsystem name, WOLA, can be changed
to any four-character string, but the BBOA and BBOAIEMT cannot be
changed. After activating the entry, when you issue the IMS /DISPLAY SUBSYS command, you should see the
WOLA subsystem and its current status.
- Pass the SSM parameter in your IMS startup
data. The four-character string designates which IMS proclib member to use to start
external subsystems such as DB2®, MQ,
and WOLA, for example: SSM=WASZ. This four character
string example instructs IMS to
look for a member in its proclib with the name of <IMSID>WASZ,
and to use that name to activate external subsystems in the current IMS environment. For more information about
how to define external subsystems to IMS, reference
the IMS Customization Guide.
- Make a copy of the optimized local adapters external modules data set
and add it to your APF list and the IMS control
region STEPLIB and DFSESL DDs. It is recommended that you
make a copy of the data set that was created using the olaInstall.sh script.
Place the copy of the data set in the APF list and the IMS.STEPLIB and DFSESL.DD concatenations in your IMS JCL procedure. This data set
contains the OLA IMS external
subsystem interface exit modules.
The olaInstall.sh script
is run when you activate the server environment to use optimized local adapters. See
the topic, Enabling your server environment for optimized local adapters,
for more information about the script.
- Add the optimized local adapters external modules data set
to your Message Processing Region (MPR), Fast Path Region (IFP) or
Batch Message Processing (BMP) JCL's STEPLIB concatenation.
The external modules data set is created using the olaInstall.sh script.
It must be included in either the STEPLIB of the IMS-dependent region
(MPR, IFP, BMP) or available in the system link concatenation.
- 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
(IVS) security product that you use.
For more information, see
the topic, Security considerations using optimized local adapters
with IMS.
- Restart the IMS region
after these changes are made. New optimized local adapters
informational messages display on the IMS control
region log indicating that the optimized local adapters external subsystem
interface is started. Issue an nn,/DISPLAY SUBSYS WOLA and ensure
the status displays as CONN (connected).
Results
You have activated support for the optimized local adapters
so that the IMS applications
can begin to register and make calls using the optimized local adapters APIs.