Version 8.2.2
 —  Adabas System Coordinator Versioning Tool  —

Installation

The Versioning Tool modules, macros and sample jobs are supplied with Adabas System Coordinator. All files have the name prefix "VER".

The following table provides an overview of the steps required to install the Versioning Tool:

Step Description
1 Create versioning load libraries.
2 Assemble the database versioning table.

Note:
This step is required for database versioning only.

3 Assemble the Coordinator daemon versioning table.

Note:
This step is required for daemon versioning only.

4 Create client versioning tables(s) and link module(s) for batch clients.

Note:
This step is required for client versioning only.

5 Create client versioning tables(s) and link module(s) for CICS clients.

Note:
This step is required for client versioning only.

6 Apply co-requisite product maintenance.
7 Copy and rename required product modules into the versioning library.
8 Add the versioning libraries to required job control.

Start of instruction setTo install the Versioning Tool, perform the following steps:

  1. Create versioning load libraries.

  2. Assemble the database versioning table.

    Notes:

    1. This step is required for database versioning only.
    2. Database versioning is used when a database is accessed by client jobs that use different versions of System Coordinator and its co-products. For example, if you have a CICS job using System Coordinator version 8.2 and another using version 8.1 accessing the same databases, those databases need to use database versioning.

    Use sample job VERI055.

    The versioning table source consists of a number of VERDB macro statements. Here is an example:

    VERDB SUFFIX=81,VRL=812
    VERDB TYPE=END
    

    The database versioning table will have an entry for each version to be run. There are 2 parameters:

    Parameter Description
    SUFFIX= Identifies the suffix for all the required modules of all the products at that version.
    VRL= Denotes the version, release and maintenance level of the suffixed collection of modules. VRL needs to be set accurately because it is used internally by the software to ensure correct operation.

    The following rules apply:

  3. Assemble the Coordinator daemon versioning table (VERDMT).

    Note:
    This step is required for daemon versioning only.

    Use sample job VERI060.

    The daemon versioning table enables you to use the re-named Coordinator and product modules in the System Coordinator daemon. This ensures that the same modules at the same maintenance levels are available in both the Adabas and the System Coordinator daemon.

    Note:
    Multiple version support in the daemon is achieved by running a separate daemon for each required version. The Coordinator daemon does not support multiple versions in a single daemon instance.

    Note:
    This is an optional activity. You may still run the Coordinator daemon from the original product libraries, if desired.

    The versioning table source consists of a number of VERDM macro statements. Here is an example:

    VERDM SUFFIX=81,VRL=812,JOBNAME=SYSCO812
    VERDM TYPE=END
    

    The daemon versioning table will have an entry for each daemon to be run. There are 3 parameters:

    Parameter Description
    JOBNAME= Identifies the jobname of a System Coordinator daemon.
    SUFFIX= Identifies the suffix for all the required modules of all the products at that version.
    VRL= Denotes the version, release and maintenance level of the suffixed collection of modules. VRL needs to be set accurately because it is used internally by the software to ensure correct operation.
  4. Create client versioning table(s) and link module(s) for batch clients.

    Note:
    This step is required for client versioning only.

    Batch versioning configuration is managed using macro settings to produce a configuration module, loaded dynamically at runtime. Here is an overview of what must or can optionally be defined:

    There are various options for using a global module (generically referred to as LNKGBLS) when using versioning. These options accommodate sites wishing to:

    Here is an example versioning configuration:

    VERCL JOBTYPE=BATCH,       Batch defaults
          OVERIDES=YES,
          WTO=NO,
          LNKGBLXX=YES,
          BINDGBLS=IGNORED,
          DBID=DDCARD,
          SVC=DDCARD
    VERCL VRL=823,             8.2.3 module, the default
          DEFAULT=YES, 
          SUFFIX=82
    VERCL VRL=814,             8.1.4 module
          SUFFIX=81,
          LNKGBLXX=YES,
          BINDGBLS=IGNORED,
          DBID=15,
          SVC=ASIS
    VERCL JOBNAME=jobname,     Use 8.1.4
          BINDGBLS=IGNORED,
          DBID=15,
          SVC=ASIS
    VERCL TYPE=END             The end.
    

    Controls for the Default BATCH Settings

    This section describes the controls which can be used for the default BATCH settings:

    Control Description
    JOBTYPE=BATCH BATCH for batch configuration entries defaults.
    OVERIDES=YES|NO YES: Allow override settings for individual versioned elements.
    NO: The settings in this element cannot be overridden.
    WTO=YES|NO YES: Details of the configuration will appear on the console.
    NO: The configuration settings are silent.
    LNKGBLXX=YES|NO YES: A versioned global module LNKGBLxx (where xx is the suffix) is to be used, paired with the versioned link module of the same suffix. For re-entrant link modules, the versioned global module is named LNRGBLxx.
    NO: No versioned global module LNKGBLxx (where xx is the suffix) is to be used even when using a suffixed link module.
    BINDGBLS=IGNORED|REQUIRED IGNORED: Dynamically loaded global modules must be used, if one cannot be found an error is raised.
    REQUIRED: Dynamically loaded global modules are ignored in favor of using the module that is linked with the link module.
    DBID=DDCARD|ASIS|number DDCARD: The value from the ADARUN DBID= setting is to be propagated to the suffixed dynamic global module (if used).

    Note:
    In order for this ADARUN DBID= DDCARD propagation to occur the ADARUN LNKGNAME= setting must also be used.


    ASIS: The value in the global module (whichever one is used) is taken "as is"; any other values (such as ADARUN DBID=) is ignored.
    Number: A specific default database number.
    SVC=DDCARD|ASIS|number DDCARD: The value from the ADARUN SVC= setting is to be propagated to the dynamic global module that is suffixed (if used).

    Note:
    In order for this ADARUN SVC= DDCARD propagation to occur the ADARUN LNKGNAME= setting must also be used.


    ASIS: The value in the global module (whichever one is used) is taken "as is"; any other values (such as ADARUN SVC=) is ignored.
    Number: A default SVC number.

    Controls for the Versioned Link Module Entry Settings

    This section describes the controls which can be used for the versioned link module entry settings:

    Control Description
    VRL=814|823 814: This identifies an 8.1.4 link module.
    823: This identifies an 8.2.3 link module.
    DEFAULT=NO|YES YES: This identifies the default link module. Only one default link module is allowed. Do not define any jobs elements for the default link module; it is used by any job not specified to use another versioned link module.
    NO: This link module is only used by the jobs listed immediately following it.
    SUFFIX=xx xx: This identifies the two character suffix to be used when loading the link module and the global module (where appropriate).
    Example: SUFFIX=81 would cause ADALNK81 to be loaded (or ADALNR81 for reentrant operation). Also, where appropriate LNKGBL81 is loaded too in the situation where SUFFIX=81 is used.
    The following controls are only allowed if OVERIDES=YES is used. They default to the overall values specified on the JOBTYPE definition.
    LNKGBLXX=YES|NO YES: A versioned global module LNKGBLxx (where xx is the suffix) is to be used, paired with the versioned link module of the same suffix.
    NO: No versioned global module LNKGBLxx (where xx is the suffix) is to be used even when using a suffixed link module.
    BINDGBLS=IGNORED|REQUIRED IGNORED: Dynamically loaded global modules must be used, if one cannot be found an error is raised.
    REQUIRED: Dynamically loaded global modules are ignored in favor of using the module that is linked with the link module.
    DBID=DDCARD|ASIS|number DDCARD: The value from the ADARUN DBID= setting is to be propagated to the suffixed dynamic global module (if used).

    Note:
    In order for this ADARUN DBID= DDCARD propagation to occur the ADARUN LNKGNAME= setting must also be used.


    ASIS: The value in the global module (whichever one is used) is taken "as is"; any other values (such as ADARUN DBID=) is ignored.
    Number: A specific default database number.
    SVC=DDCARD|ASIS|number DDCARD: The value from the ADARUN SVC= setting is to be propagated to the dynamic global module that is suffixed (if used).

    Note:
    In order for this ADARUN SVC= DDCARD propagation to occur the ADARUN LNKGNAME= setting must also be used.


    ASIS: The value in the global module (whichever one is used) is taken "as is"; any other values (such as ADARUN SVC=) is ignored.
    Number: A default SVC number.

    Controls for Specific Job Name Entry Settings

    This section describes the controls which can be used for specific job name entry settings:

    Control Description
    JOBNAME=jobname This identifies the jobs that are to use the link module version identified prior to this job-name list.
    The following controls are only allowed if OVERIDES=YES is used. They default to the values specified on or inherited by the preceding link module definition.
    LNKGBLXX=YES|NO YES: A versioned global module LNKGBLxx (where xx is the suffix) is to be used, paired with the versioned link module of the same suffix.
    NO: No versioned global module LNKGBLxx (where xx is the suffix) is to be used even when using a suffixed link module.
    BINDGBLS=IGNORED|REQUIRED IGNORED: Dynamically loaded global modules must be used, if one cannot be found an error is raised.
    REQUIRED: Dynamically loaded global modules are ignored in favor of using the module that is linked with the link module.
    DBID=DDCARD|ASIS|number DDCARD: The value from the ADARUN DBID= setting is to be propagated to the suffixed dynamic global module (if used).

    Note:
    In order for this ADARUN DBID= DDCARD propagation to occur the ADARUN LNKGNAME= setting must also be used.


    ASIS: The value in the global module (whichever one is used) is taken "as is"; any other values (such as ADARUN DBID=) is ignored.
    Number: A specific default database number.
    SVC=DDCARD|ASIS|number DDCARD: The value from the ADARUN SVC= setting is to be propagated to the dynamic global module that is suffixed (if used).

    Note:
    In order for this ADARUN SVC= DDCARD propagation to occur the ADARUN LNKGNAME= setting must also be used.


    ASIS: The value in the global module (whichever one is used) is taken "as is"; any other values (such as ADARUN SVC=) is ignored.
    Number: A default SVC number.

    The resulting load module must be named VERC01 for standard batch or VERC09 for re-entrant batch and the versioning table load modules must be linked REUS, – not RENT. Sample job VERI065 shows how to assemble and link the versioning table.

    Copy the client versioning modules to the client versioning library

    Copy VERLNK01 to your client versioning library as ADALNK and VERLNR01 as ADALNKR, using sample job VERI085 (making sure the real ADALNK and ADALNKR are not lost). Certain fixed offsets in the Adabas link module contain information which is required by some callers of ADALNK. For example, length of the USER and Review extensions. If you use other than default values, you must zap the correct values into the ADALNK and ADALNKR copies of VERLNK01 and VERLNR01. Sample job VERI088 may be used to do this.

    Important:
    This library must not be made available to any target in the Software AG network which acts as a DBID – such as Adabas, Broker, Com-Plete, Entire System Server, Net-Work, System Coordinator daemon etc.

    Copy required link modules to the client versioning library

    Copy your existing ADALNK and LNKGBLS modules to the client versioning library, renaming them to have the appropriate suffix:

    ADALNKxx and LNKGBLxx for standard batch 
    ADALNRxx and LNRGBLxx for re-entrant batch
    
  5. Create client versioning table(s) and link module(s) for CICS clients.

    Note:
    This step is required for client versioning only.

    Messages Issued by Client Versioning

    The messages issued by client versioning (if you specify WTO=YES), have changed format slightly. The batch client versioning routines now only report the link module and options in use by this job, rather than all modules in the table, for example:

    +VER101I Jobname  Link Module Globals  SVC    DBID  
    +VER101I -------- ----------- -------- ------ ------
    +VER101I ADA81TST ADALNK81    BINDGBLS ASIS   ASIS  
    

    The CICS client versioning routine still lists the full table contents:

    +VER101I  Criteria Link Module
    +VER101I  -------- -----------
    +VER101I  Default  ADABASDF   
    +VER101I  DEMO     ADABASDE   
    +VER101I  N426     ADABAS81   
    

    If client versioning detects an error (for example, the required link module is not available), it issues a message and rejects all Adabas commands with response 101, subcode 87.

  6. Apply co-requisite maintenance.

    The following maintenance fixes must be applied before using versioning with these products:

    Product Maintenance Fix
    Adabas Version 742 AI742030
    Adabas System Coordinator Version 742 Install the COR L005 load library update
    Online Services INPL updates IS06
    Adabas Fastpath Version 742 AW742081
    Adabas Vista Version 742 AV742017
    Adabas SAF Security Version 742 AX742002
  7. Copy and rename required product modules into the versioning library.

    Customize and use the following sample jobs:

    Version 742: VERI080D

    Version 811: VERI080E

    Version 822: VERI080F

    The sample jobs indicate all of the modules that require copying and renaming. No other product modules should be renamed.

    Note:
    The System Coordinator module ADAPOB must not be renamed. If you have multiple versions of this module, ensure that the one in use is at the highest level.

  8. Add the versioning libraries to required job control.

    The versioning llibrary (the ALLVERS Library) must be added to the Joblib or Steplib concatenation of all Adabas server start-up jobs that require versioning support. The library should be added at the top of the concatenation, so that the special version of ADAPOP will be invoked at nucleus start-up.

    If you want to run the System Coordinator daemon from the same versioning load library, you should also add the ALLVERS library first in the daemon Joblib or Steplib concatenation.

    The ALLVERS load library and the client versioning load library must be added to the top of the Steplib concatenation for any batch jobs that require versioning support.

    For CICS, the client versioning load library and the ALLVERS load library must be added to the DFHRPL and Steplib concatentations.

Top of page