If you intend to use Adabas Transaction Manager through the CICS Resource Manager Interface (RMI), use the following installation procedure in conjunction with the installation procedure for the Adabas task-related user exit (TRUE) described in the Adabas Installation for z/OS documentation.
Note:
A supported level of IBM’s CICS is needed, with RMI configured in it.
The steps needed for a successful installation are as follows:
| Step | Description |
|---|---|
| 1 | Perform the standard installation procedure for Adabas Transaction Manager, and verify the installation. |
| 2 | Follow the steps for the installation of the Adabas TRUE, with the changes described below. |
| 3 | Establish CICS definitions for Adabas Transaction Manager RMI programs. |
| 4 | Copy the Adabas Transaction Manager RMI modules into a CICS RPL library. |
| 5 | Define client runtime controls for the CICS system. |
| 6 | Activate the Adabas Transaction Manager CICS Resource Manager Interface (RMI). |
The following is the general RMI installation procedure. All steps are required for a successful installation.
Install and verify the execution of the transaction manager and client proxy without activating the RMI.
This process is fully described in the Adabas Installation for z/OS documentation. However, the installation process for the RMI differs in a few points from that described. Follow the instructions below as you go through the Adabas TRUE installation process.
To activate the RMI:
Set the following value in the LGBLSET macro:
| RMI=YES | activate the CICS Resource Manager Interface (RMI) |
Optionally, if the CICS high performance stub routine is to be generated, set the following values in the ADAGSET macro:
| RMI=YES | activate the CICS Resource Manager Interface (RMI) |
| TRUE=YES | run as a task-related user exit (TRUE) |
When linking the Adabas command-level link component, you must link in the Adabas System Coordinator stub module.
To establish CICS definitions for the RMI programs:
Use DFHCSDUP or the CEDA RDO entry panels to add the definitions delivered in member DFHDUP in the supplied JOBS library.
Note:
If storage protection is active in your CICS system, EXECKEY(CICS)
should be specified for the PROGRAM definitions.
The following programs, supplied in the Adabas Transaction Manager load library, must be made available in the DFHRPL DD concatenation of your CICS JCL procedure:
ATMRMIRS
ATMORID
Use Adabas Transaction Manager Online Services to define the required client runtime controls for the CICS job.
The required controls are described in section
Parameters. Some special
considerations are necessary when running with the RMI active. Define a set of
client runtime controls for the CICS job. Pay particular attention to the
Client-side
TransactionManager,
TransactionModel
and TransactionControl,
as well as the GenerateExternalSyncpoint
client controls.
To activate the CICS Resource Manager Interface:
Ensure that the Adabas System Coordinator daemon, within which the Adabas Transaction Manager is running, is active.
Start CICS.
