The second phase installs the components that are specific to the particular TP monitor in use at your site. Separate procedures are used to install Adabas Review under each of the supported TP monitors:
Com-plete
CICS
TSO or TSS (batch)
IMS/DC
This document covers the following topics:
This section describes the installation of Adabas Review under Com-plete, as well as tailoring and other recommendations for Adabas Review client reporting support under Com-plete.
To install the Com-plete components of Adabas Review for use with the
Adabas 8 Com-plete link routine:
Modify the member LCOGBL found in the ADAvrs.MVSSRCE library, and set the following LGBLSET parameters according to your requirements:
| Parameter | Description | Syntax |
|---|---|---|
| REVHID | Specifies the preferred Adabas Review hub ID.
This value can be checked during the Adabas TP monitoring installation or
during the monitor activate process.
If REVHID is set to zero (0), the preferred Adabas Review hub ID is dynamic. When the hub ID is dynamic, it cannot be checked during the Adabas TP monitoring installation and the call to turn on client reporting must supply the correct Adabas Review hub ID to use. If REVHID is specified, REVIEW=YES must also be specified. If REVHID is specified and REVIEW=NO is also specified, the assembly of the globals table will abort with condition code 16 and the following message is given: REVHID requires REVIEW=YES This parameter is not valid in VSE environments. The parameter exists in VSE environments, but should be set to "0". |
REVHID=hubid |
| REVIEW |
Indicates whether or not Software AG's Adabas Review performance monitor is installed and active. REVIEW=YES will automatically activate the Adabas Review performance monitor for all clients. REVIEW=COR requires COR=YES and indicates that client activation of the Adabas Review performance monitor will be deferred to the setting of the Adabas System Coordinator's client runtime control "Review". Refer to the Adabas System Coordinator documentation for more information on this client runtime control. |
REVIEW={NO | YES | COR}
|
| REVREL |
This parameter is redundant and will be dropped in a future Adabas version. Please remove any use of this parameter from your LGBLSET input. Continued use of this parameter will result in the following informational MNOTE message: REVREL= is redundant and is no longer required. The assembly of the globals table is unaffected. |
REVREL={ } |
| RVCLNT | Indicates whether Adabas Review client reporting
should be allowed. When client reporting is allowed, it can be activated by the
ADARUN RVCLIENT parameter in a batch environment (ADARUN PROGRAM=USER). The
default is NO.
If RVCLNT=YES is specified, REVIEW=YES must also be specified. If RVCLNT=YES is specified and REVIEW=NO is also specified, the assembly of the globals table will abort with condition code 16 and the following message is given: RVCLNT=YES requires REVIEW=YES This parameter is not valid in VSE environments. The parameter exists in VSE environments, but should be set to "NO". |
RVCLNT={YES|NO} |
For example, the following keywords indicate that Adabas Review support should be installed and, specifically, support for Adabas Review 4.6 and later.
REVIEW=YES REVREL=46
Assemble and link the modified LCOGBL member into a load library and make it available for the next step.
Re-link the Adabas Version 8 Com-plete link routine using sample job LREVLCO in the Review JOBS data set, replacing the LCOGBL module with the one prepared in steps 1 and 2 and including the RDBLXCOM Review module for Com-plete.
Restart Adabas and Com-plete, and verify that an Adabas or WAL load library with the modules ADATMZ, ADALNKR, and CCSTCK is specified for the Com-plete startup job.
Initialize and test Adabas Review.
See Starting Adabas Review for information about initializing and verifying the installation of the online portion of Adabas Review.
Support for client reporting is provided when you follow the basic installation steps for Adabas Review under Com-plete . This section repeats those instructions and provides additional input specific to client monitoring support.
To install the Adabas Review client reporting components for use with
the Adabas 8 Com-plete link routine:
Edit the LCOGBL link globals member found in the ADAvrs.MVSSRCE library. For client monitoring support, we recommend that you set the following LGBLSET keywords in this way:
| Keyword | Recommended Setting | Discussion |
|---|---|---|
| OPSYS | ZOS | Specifies z/OS as the operating system. |
| TPMON | COM | Specifies Com-plete as the TP monitoring environment. |
| GEN | CSECT | Specifies that a CSECT should be generated for processing. |
| RENT | YES | Indicates that the globals module is reentrant. |
| GBLNAME | LCOGBL | Indicates that the name of the link globals module is LCOGBL. |
| REVIEW | YES | Indicates that Adabas Review is installed and active. |
| REVREL | -/- |
This parameter is redundant and will be dropped in a future Adabas version. Please remove any use of this parameter from your LGBLSET input. Continued use of this parameter will result in the following informational MNOTE message: REVREL= is redundant and is no longer required. The assembly of the globals table is unaffected. |
| RVCLNT | YES | Indicates whether Adabas Review client reporting should be allowed. When client reporting is allowed, it can be activated by the ADARUN RVCLIENT parameter in a batch environment (ADARUN PROGRAM=USER). |
| REVHID | default hub ID or zero | Identifies the preferred Adabas Review hub ID. |
Assemble and link the modified LCOGBL member into a load library and make it available for the next step.
Re-link the Adabas Version 8 Com-plete link routine using sample job LREVLCO in the Review JOBS data set, replacing the LCOGBL module with the one prepared in steps 1 and 2 and including the RDBLXCOM Review module for Com-plete.
Note:
The REVEXIT2 code that handles Adabas Review client reporting is
distributed with the RDBLXCOM load module.
Restart Adabas and Com-plete, and verify that an Adabas or WAL load library with the modules ADATMZ, ADALNKR, and CCSTCK is specified for the Com-plete startup job.
Client reporting support is installed.
When client reporting is installed, it is not automatically activated. Instead, you must manually activate it in one of the following ways.
Use the Client Management screen in SYSREVDB to activate it online.
Set the ADARUN RVCLIENT parameter to "ACTIVE" to activate it when you want to run client reports in batch environments.
Call the batch module REVCLRP, specifying its RVCLFUNC parameter as "ON" to activate it within your own application program.
Once client reporting for Review is activated, storage for client reporting data is obtained from the client thread. To reduce the number of invocations of the Adabas Review Trans-port facility, the data is buffered. An additional 32K of storage from each active thread is required to support the buffered client data.
We also recommend that you run with Com-plete threads in key 08. Mixed thread keys may be used but there will be a performance penalty on every Adabas call as the Adabas Review exit switches between storage keys for the Com-plete kernel, key 08, and the key of the thread where the client reporting data is stored and back to Com-plete’s key again before returning control to ADALCO. Com-plete will use key 08 for threads when the THREAD-GROUP keyword is set as follows:
THREAD-GROUP=(DEFAULT,(DEF04,004,14,10,20,8))
Specifying "8" or "N" in the last subparameter indicates that Com-plete should obtain and run all thread storage in key 8. For more information, consult the Com-plete documentation.
If only Natural application programs are run under Com-plete, these will usually run in key 8 if the SKEY=ON Natural parameter is specified. This parameter causes Natural to switch into key 8 even if the thread itself was not defined to run key 8. SKEY=ON is the recommended setting for Natural running under Com-plete if Review client reporting is used.
This section provides instructions for installing the CICS components of Adabas Review with the Adabas 8 CICS link routine.
The ACITMZ module is required to execute the target discovery process in a CICS environment. This module is invoked from Natural Review code to assist in the location of Adabas Review hubs.
To install the CICS components of Adabas Review for use with the Adabas
Version 8 CICS link routine:
Modify the member CICSGBL found in the ACIvrs.MVSSRCE library, and set the following LGBLSET parameters according to your requirements:
| Parameter | Description | Syntax |
|---|---|---|
| REVHID | Specifies the preferred Adabas Review hub ID.
This value can be checked during the Adabas TP monitoring installation or
during the monitor activate process.
If REVHID is set to zero (0), the preferred Adabas Review hub ID is dynamic. When the hub ID is dynamic, it cannot be checked during the Adabas TP monitoring installation and the call to turn on client reporting must supply the correct Adabas Review hub ID to use. If REVHID is specified, REVIEW=YES must also be specified. If REVHID is specified and REVIEW=NO is also specified, the assembly of the globals table will abort with condition code 16 and the following message is given: REVHID requires REVIEW=YES This parameter is not valid in VSE environments. The parameter exists in VSE environments, but should be set to "0". |
REVHID=hubid |
| REVIEW |
Indicates whether or not Software AG's Adabas Review performance monitor is installed and active. REVIEW=YES will automatically activate the Adabas Review performance monitor for all clients. REVIEW=COR requires COR=YES and indicates that client activation of the Adabas Review performance monitor will be deferred to the setting of the Adabas System Coordinator's client runtime control "Review". Refer to the Adabas System Coordinator documentation for more information on this client runtime control. |
REVIEW={NO | YES | COR}
|
| REVREL |
This parameter is redundant and will be dropped in a future Adabas version. Please remove any use of this parameter from your LGBLSET input. Continued use of this parameter will result in the following informational MNOTE message: REVREL= is redundant and is no longer required. The assembly of the globals table is unaffected. |
REVREL={ } |
| RVCLNT |
Indicates whether Adabas Review client reporting should be allowed and available for activation. RVCLNT=YES requires REVIEW=YES and indicates Adabas Review client reporting is allowed and available for the manual activation of all clients. Refer to the Adabas Review documentation for the means of activation. RVCLNT=COR requires REVIEW=YES or COR and indicates Adabas Review client reporting is allowed and activation is deferred to the setting of the Adabas System Coordinator's client runtime control "Client Monitor". Refer to the Adabas System Coordinator documentation for more information on this client runtime control. |
RVCLNT={NO|YES|COR}
|
For example, the following keywords indicate that Adabas Review support should be installed and, specifically, support for Adabas Review 4.6 and later.
REVIEW=YES REVREL=46
Assemble and link-edit the CICSGBL member. Be sure to include the Adabas Review exits in the link-edit with CICSGBL. In addition, be sure to include CICS module DFHEAI. A sample job, LREVLCIC, is provided in the Review JOBS data set to assist you.
Note:
The RDBLXCIC module contains the REVEXIT2 program necessary
to support Adabas Review client reporting. Consequently, when the globals table is
relinked, the necessary program is present to support Adabas Review client reporting.
The Adabas Review exits include REVEXIT1 and REVEXIT2. To obtain data for all Adabas Review fields (TP monitor-specific and Natural-specific fields) that are obtained in the Adabas client address space (ADALNK), the REVEXIT1 entry point of the Adabas Review exit REVEXIT and the ADALNK routines from Adabas are used. To obtain data for all client reporting fields, the REVEXIT2 entry point of REVEXIT and the ADALNK routines must also be used.
These exits should be linked with ADALNK during installation, with the appropriate Adabas link globals table parameters (LGBLSET). The link globals table parameters specified via LGBLSET identify which exit entry points (REVEXIT1 or REVEXIT2) are called. If the LGBLSET parameter REVIEW=YES is set, then the exit is called by ADALNK before the Adabas call as entry point REVEXIT1; if the LGBLSET parameters RVCLNT and REVHID are also specified, then the exit is also called after the Adabas call as entry point REVEXIT2.
The modules used to perform the linkage between REVEXIT and ADALNK are provided with your Adabas Review installation with names in the format RDBLXsys, where sys is a three-character code representing the link environment (for example, MVS for z/OS environments, COM for Com-plete environments, IMS for IMS environments. For more information about performing this linkage, read the appropriate Adabas Review installation documentation.
Install ACITMZ.
To install ACITMZ, complete the following steps:
Copy the ACITMZ load module from the distribution library to a library in the CICS DFHRPL concatenation.
Using the DFHCSDUP utility or the CICS CEDA transaction, install the program definition for ACITMZ. A sample definition, DEFCTMZ, is provided in the ACIvrs.MVSSRCE data set to assist you.
Follow the instructions in the Installing the Version 8 CICS Link Routines in the Adabas Installation Manual if this is the first time the CICS link routines are being installed in this CICS system.
Restart Adabas and CICS.
Initialize and test Adabas and Review.
Read Starting Adabas Review for information about initializing and verifying the installation of the online portion of Adabas Review.
This section provides instructions for installing the TSO components of Adabas Review with the Adabas 8 TSO/batch link routine.
Important:
If an ADALNK batch routine has been linked or modified by
Adabas Review modules, it cannot be used in any application startups of Adabas utility
jobs or Adabas, Entire System Server, Adabas Review Hub, or Entire Net-Work
nuclei.
To install the batch/TSO components of Adabas Review for the
Adabas 8 TSO/batch link routine:
Modify the member LNKGBLS found in the ADAvrs.MVSSRCE library, and set the following LGBLSET parameters according to your requirements:
| Parameter | Description | Syntax |
|---|---|---|
| REVHID | Specifies the preferred Adabas Review hub ID.
This value can be checked during the Adabas TP monitoring installation or
during the monitor activate process.
If REVHID is set to zero (0), the preferred Adabas Review hub ID is dynamic. When the hub ID is dynamic, it cannot be checked during the Adabas TP monitoring installation and the call to turn on client reporting must supply the correct Adabas Review hub ID to use. If REVHID is specified, REVIEW=YES must also be specified. If REVHID is specified and REVIEW=NO is also specified, the assembly of the globals table will abort with condition code 16 and the following message is given: REVHID requires REVIEW=YES This parameter is not valid in VSE environments. The parameter exists in VSE environments, but should be set to "0". |
REVHID=hubid |
| REVIEW |
Indicates whether or not Software AG's Adabas Review performance monitor is installed and active. REVIEW=YES will automatically activate the Adabas Review performance monitor for all clients. REVIEW=COR requires COR=YES and indicates that client activation of the Adabas Review performance monitor will be deferred to the setting of the Adabas System Coordinator's client runtime control "Review". Refer to the Adabas System Coordinator documentation for more information on this client runtime control. |
REVIEW={NO | YES | COR}
|
| REVREL |
This parameter is redundant and will be dropped in a future Adabas version. Please remove any use of this parameter from your LGBLSET input. Continued use of this parameter will result in the following informational MNOTE message: REVREL= is redundant and is no longer required. The assembly of the globals table is unaffected. |
REVREL={ } |
| RVCLNT |
Indicates whether Adabas Review client reporting should be allowed and available for activation. RVCLNT=YES requires REVIEW=YES and indicates Adabas Review client reporting is allowed and available for the manual activation of all clients. Refer to the Adabas Review documentation for the means of activation. RVCLNT=COR requires REVIEW=YES or COR and indicates Adabas Review client reporting is allowed and activation is deferred to the setting of the Adabas System Coordinator's client runtime control "Client Monitor". Refer to the Adabas System Coordinator documentation for more information on this client runtime control. |
RVCLNT={NO|YES|COR}
|
For example, the following keywords indicate that Adabas Review support should be installed and, specifically, support for Adabas Review 4.6 and later.
REVIEW=YES REVREL=46
Assemble and link-edit the modified LNKGBLS member into a load library and make it available for the next step.
Note:
Note: The RDBLXMVS module contains the REVEXIT2 program
necessary to support Adabas Review client reporting. Consequently, when the globals
table is relinked, the necessary program is present to support Adabas Review client
reporting.
Relink the Adabas Version 8 TSO/batch link routine using sample job LREVLNK in the Review JOBS data set, replacing the LNKGBLS module with the one prepared in steps 1 and 2 and including the RDBLXMVS Review module for TSO.
Note:
If you elect to use the link routine ADALNKR, link the
batch Review routine RDBLXMVS to ADALNKR using sample job LREVLNKR in the
Review JOBS data set. The RDBLXMVS module contains the REVEXIT2 program
necessary to support Adabas Review client reporting. Consequently, when the globals
table is relinked, the necessary program is present to support Adabas Review client
reporting.
The Adabas Review exits include REVEXIT1 and REVEXIT2. To obtain data for all Adabas Review fields (TP monitor-specific and Natural-specific fields) that are obtained in the Adabas client address space (ADALNK), the REVEXIT1 entry point of the Adabas Review exit REVEXIT and the ADALNK routines from Adabas are used. To obtain data for all client reporting fields, the REVEXIT2 entry point of REVEXIT and the ADALNK routines must also be used.
These exits should be linked with ADALNK during installation, with the appropriate Adabas link globals table parameters (LGBLSET). The link globals table parameters specified via LGBLSET identify which exit entry points (REVEXIT1 or REVEXIT2) are called. If the LGBLSET parameter REVIEW=YES is set, then the exit is called by ADALNK before the Adabas call as entry point REVEXIT1; if the LGBLSET parameters RVCLNT and REVHID are also specified, then the exit is also called after the Adabas call as entry point REVEXIT2.
The modules used to perform the linkage between REVEXIT and ADALNK are provided with your Adabas Review installation with names in the format RDBLXsys, where sys is a three-character code representing the link environment (for example, MVS for z/OS environments, COM for Com-plete environments, IMS for IMS environments. For more information about performing this linkage, read the appropriate Adabas Review installation documentation.
Restart Adabas and TSO, and verify that an Adabas or WAL load library with the modules ADATMZ, ADALNKR, and CCSTCK is specified for the batch/TSO startup job.
Initialize and test Adabas Review.
Read Starting Adabas Review for information about initializing and verifying the installation of the online portion of Adabas Review.
This section provides instructions for installing the IMS/DC components of Adabas Review for the Adabas 8 IMS/DC link routine.
To install the IMS/DC components of Adabas Review for the Adabas 8 IMS/DC
link routine:
Modify the LNIGBL member found in AIIvrs.MVSSRCE, setting the following LGBLSET keywords:
| Parameter | Description | Syntax |
|---|---|---|
| REVHID | Specifies the preferred Adabas Review hub ID.
This value can be checked during the Adabas TP monitoring installation or
during the monitor activate process.
If REVHID is set to zero (0), the preferred Adabas Review hub ID is dynamic. When the hub ID is dynamic, it cannot be checked during the Adabas TP monitoring installation and the call to turn on client reporting must supply the correct Adabas Review hub ID to use. If REVHID is specified, REVIEW=YES must also be specified. If REVHID is specified and REVIEW=NO is also specified, the assembly of the globals table will abort with condition code 16 and the following message is given: REVHID requires REVIEW=YES This parameter is not valid in VSE environments. The parameter exists in VSE environments, but should be set to "0". |
REVHID=hubid |
| REVIEW | Indicates whether or not Software AG’s Adabas Review performance monitor is installed and active. |
REVIEW={NO | YES} |
| REVREL |
This parameter is redundant and will be dropped in a future Adabas version. Please remove any use of this parameter from your LGBLSET input. Continued use of this parameter will result in the following informational MNOTE message: REVREL= is redundant and is no longer required. The assembly of the globals table is unaffected. |
REVREL={ } |
| RVCLNT | Indicates whether Adabas Review client reporting
should be allowed. When client reporting is allowed, it can be activated by the
ADARUN RVCLIENT parameter in a batch environment (ADARUN PROGRAM=USER). The
default is NO.
If RVCLNT=YES is specified, REVIEW=YES must also be specified. If RVCLNT=YES is specified and REVIEW=NO is also specified, the assembly of the globals table will abort with condition code 16 and the following message is given: RVCLNT=YES requires REVIEW=YES This parameter is not valid in VSE environments. The parameter exists in VSE environments, but should be set to "NO". |
RVCLNT={YES|NO} |
For example, the following keywords indicate that Adabas Review support should be installed and, specifically, support for Adabas Review 4.6 and later.
REVIEW=YES REVREL=46
Assemble and link-edit the modified LNIGBL member into a load library and make it available for the next step.
Modify and link the Natural IMS/DC interface using sample job LREVLNI in the Review JOBS data set. Include the following in the link of the Natural IMS interface modules:
ADALNI and ADALNK
Note:
Do not link any Adabas Review link routine exits to ADALNI and
ADALNK prior to this step. Also, do not code REVIEW=YES in the LNKGBLS table
linked with ADALNK for the Natural IMS module.
RDBLXIMS, the Adabas Review IMS/DC link routine exit.
The Adabas Review exits include REVEXIT1 and REVEXIT2. To obtain data for all Adabas Review fields (TP monitor-specific and Natural-specific fields) that are obtained in the Adabas client address space (ADALNK), the REVEXIT1 entry point of the Adabas Review exit REVEXIT and the ADALNK routines from Adabas are used. To obtain data for all client reporting fields, the REVEXIT2 entry point of REVEXIT and the ADALNK routines must also be used.
These exits should be linked with ADALNK during installation, with the appropriate Adabas link globals table parameters (LGBLSET). The link globals table parameters specified via LGBLSET identify which exit entry points (REVEXIT1 or REVEXIT2) are called. If the LGBLSET parameter REVIEW=YES is set, then the exit is called by ADALNK before the Adabas call as entry point REVEXIT1; if the LGBLSET parameters RVCLNT and REVHID are also specified, then the exit is also called after the Adabas call as entry point REVEXIT2.
The modules used to perform the linkage between REVEXIT and ADALNK are provided with your Adabas Review installation with names in the format RDBLXsys, where sys is a three-character code representing the link environment (for example, MVS for z/OS environments, COM for Com-plete environments, IMS for IMS environments. For more information about performing this linkage, read the appropriate Adabas Review installation documentation.
Read Starting Adabas Review for information about initializing and verifying the installation of the online portion of Adabas Review.