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 OS/390 and z/OS documentation.
Note:
CICS/ESA version 4.1 or above or CICS/TS version 1.2 or above is
required.
The steps needed for a successful installation are as follows:
| Step | Description |
|---|---|
| Before proceeding with the installation, ensure that all necessary preparation has been completed as described in section Before You Install. | |
| 1 | Perform 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 | Enable the required CICS facilities. |
| 6 | Define job parameters for the CICS system. |
| 7 | 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.
The actual installation depends on your particular requirements and the specific contents of the release package provided by Software AG for your site. Information in the release package is intended for your system. If that information differs from the information in this section, use the release package information or contact Software AG technical support for assistance.
It is strongly recommended that you first install and verify the execution of the Adabas Transaction Manager daemon and proxy without activating the RMI.
This process is fully described in the Adabas Installation for OS/390 and 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 installation process.
to activate the RMI:
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.
When you assemble and link the Adabas task-related user exit, include the Adabas Transaction Manager RMI interface module in the link step. Sample job ATMI080X can be adapted for this purpose.
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 ATM751.JOBS dataset.
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 ATM load library, must be made available in the DFHRPL DD concatenation of your CICS JCL procedure:
ATMRMIR0
ATMRMIRS
ATMORID
Adabas Transaction Manager uses the External CICS Interface (EXCI) to trigger the re-synchronization of incomplete transactions during restart. Therefore, the CICS system in which you are installing the RMI must have interregion communication enabled, and must be enabled for EXCI, the external EXEC CICS interface, which requires a generic connection. Refer to the relevant IBM documentation for details.
If your installation uses a security system, such as RACF, ensure that the User ID under which Adabas Transaction Manager executes has authorization to use EXCI.
Use Adabas Transaction Manager Online Services to define the required job parameters for the CICS job.
The required parameters are described in section
Parameters. Some special
considerations are necessary when running with the RMI active. Define a set of
job parameters for the CICS job. Pay particular attention to the parameters
LCLSYNC,TRANMODE and TRNCTL, as
well as the SYNCONxx parameters.
to activate the CICS Resource Manager Interface:
Ensure that the CICS EXCI load library is available in the STEPLIB concatenation of your Adabas Transaction Manager job or JCL procedure.
Start CICS.
Ensure that the Adabas System Coordinator daemon is executing.
Start the Adabas Transaction Manager daemon.
