Installation: Phase 2

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 supported TP monitor: Com-plete, CICS, and batch.

This document covers the following topics:


Install Adabas Review under Com-plete

Start of instruction setTo install the Com-plete components of Adabas Review for use with the Adabas 8 Com-plete link routine:

  1. Edit the LCOGBL link globals member found in the ADAvrs.LIBR library, setting the REVIEW and REVREL 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
  2. Use the JCS contained in the sublibrary member LREVLCO.X to set and assemble the LCOGBL module and link this to make the ADALCO phase with the Adabas Review link routine exit.

    Note:
    The target of the link in this step must be a sublibrary in the Com-plete LIBDEF PHASE search concatenation.

  3. Restart Adabas and Com-plete and verify that the modules ADATMZ, ADALNKR, and CCSTCK are included in the LIBDEF concatenation for the Com-plete startup job.

  4. Initialize and test Adabas Review.

    Refer to section Starting Adabas Review for information about initializing and verifying the installation of the online portion of Adabas Review.

Install Adabas Review under CICS

Start of instruction setTo install the CICS components of Adabas Review for use with the Adabas 8 CICS link routine:

  1. Modify the member CICSGBL found in the ADAvrs.LIBR library, and set the REVIEW and REVREL 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
  2. Modify the sample job LREVLCIC.X to set the SVC, DBID, library, and sublibrary information and submit it.

  3. Restart Adabas and CICS.

  4. Initialize and test Adabas Review.

    Refer to section Starting Adabas Review for more information about initializing and verifying the installation of the online portion of Adabas Review.

Install Adabas Review under Batch

This section provides instructions for installing the batch components of Adabas Review with the Adabas batch link routines.

Important:
If an ADALNK batch link routine has been linked or modified by Software AG product modules or user exits, 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.

Start of instruction setTo install the batch components of Adabas Review for the Adabas 8 batch link routine:

  1. Edit member LNKGBLS.A in the Adabas distribution sublibrary. Provide values for the LOGID, SVC, GBLNAME, and other keywords to suit your installation requirements. Be sure to set the REVIEW and REVREL 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}
    REVIEW=YES
    REVREL=46
    OPSYS=VSE

    Note:
    If you elect to use the reentrant link routine, edit member LNKRGBL.A in the Adabas distribution sublibrary.

  2. Edit the ALNKLNK8.X member found in the Adabas 8 sublibrary. This member will assemble and catalog the LNKGBLS.A module and link it and any desired exits with the LNKVSE8.OBJ module to create the ADALNK.PHASE member for Adabas 8. The ALNKLNK8.X member includes sample link-edit control cards to support UES by including the LNKUES.OBJ. module with the ASC2EBC and EBC2ASC translation tables. Modify the link-edit control cards to include any additional Software AG exit or user exits, as specified in the updated LNKGBLS.A member.

    Note:
    If you elect to use the reentrant link routine, edit member ALNKLNR8.X in the Adabas distribution sublibrary.

  3. Provide the ADALNK.PHASE member in the LIBDEF search chain for the job step that will require Adabas database access or Software AG services.

    Note:
    If you elect to use the reentrant link routine, provide the ADALNKR.PHASE member in the LIBDEF search chain for the job step that will required Adabas database access or Software AG services.

  4. Restart Adabas and verify that the modules ADATMZ, ADALNK, ADALNKR, and CCSTCK are included in the LIBDEF concatenation for the batch startup job.

  5. Initialize and test Adabas Review.

    Refer to section Starting Adabas Review for more information about initializing and verifying the installation of the online portion of Adabas Review.