Version 8.2.2	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

• The Installation Medium

• Installation Overview

• System Programming Considerations

• Installation Procedure

• Installing Adabas System Coordinator in multi-task batch environments

The Installation Medium

Review the Software AG Product Delivery Report that accompanies the release package before restoring the release data to disk. Information in this report supersedes the information in this documentation.

The installation medium contains the following data sets in the sequence indicated in the report:

where vrs in data set names represents the version, revision, and system maintenance level of the product.

Installation Overview

The steps needed for a successful installation are as follows:

System Programming Considerations

In a multi-systems environment a Coordinator daemon is normally defined for each system. In a parallel sysplex daemons use the IBM XCF facility to communicate. All COR daemons are defined (in the COR configuration file) with the same group name, and this name is used as the XCF group name. The group name selected must be unique to the COR daemon group, and must not be the same as the group name (CLUGROUPNAME) selected for any Adabas Cluster Services database.

The Adabas System Coordinator daemon must execute:

• from an authorized load library; and

• at a higher priority than the TP monitors, databases, and jobs it is used to coordinate.

Installation Procedure

Following is the general Adabas System Coordinator installation procedure. 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.

Step1: Copying the Medium Contents to Disk

If you are using System Maintenance Aid (SMA), refer to the SMA documentation (included on the current edition of the Natural documentation CD). If you are not using SMA, perform steps 1a, 1b and 1c as described in this section:

• Step 1a: Copy Data Set COPY.JOB from Medium to Disk
• Step 1b: Modify COPY.JOB
• Step 1c: Submit COPY.JOB

Note:
If the data sets for more than one product are delivered on the medium, the data set COPY.JOB contains the JCL to unload the data sets for all delivered products from the medium to your disk. After that, you will have to perform the individual install procedure for each component.

Step 1a: Copy Data Set COPY.JOB from Medium to Disk

The data set COPY.JOB (label 2) contains the JCL to unload all other existing data sets from medium to disk. To unload COPY.JOB, use the following sample JCL:

//SAGTAPE JOB SAG,CLASS=1,MSGCLASS=X
//* ---------------------------------
//COPY EXEC PGM=IEBGENER
//SYSUT1 DD DSN=COPY.JOB,
// DISP=(OLD,PASS),
// UNIT=(CASS,,DEFER),
// VOL=(,RETAIN,SER=<Tnnnnn>),
// LABEL=(2,SL)
//SYSUT2 DD DSN=<hilev>.COPY.JOB,
// DISP=(NEW,CATLG,DELETE),
// UNIT=3390,VOL=SER=<vvvvvv>,
// SPACE=(TRK,(1,1),RLSE),
// DCB=*.SYSUT1
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
// 

where:

<hilev>  is a valid high level qualifier 
<Tnnnnn> is the tape number 
<vvvvvv> is the desired volser  

Step 1b: Modify COPY.JOB

Modify the COPY.JOB to conform with your local naming conventions and set the disk space parameters before submitting this job:

• set HILEV to a valid high level qualifier

• set LOCATION to a storage location

• set EXPDT to a valid expiration date

Step 1c: Submit COPY.JOB

Submit COPY.JOB to unload all other data sets from the medium to your disk.

Step 2: Load (INPL) the SYSCOR Application (Job I061)

Use sample job CORI061 to load the SYSCOR online administration and error messages file into Natural.

Step 3: Load the Configuration File and Prepare SYSCOR (Job I050)

System Coordinator and related products operate according to definitions contained in the configuration file. You must allocate a new Adabas file for the Version 8.2 configuration file and load CORvrl.SYSF into it using the supplied sample job CORI050. The online services will guide you through the steps required to make the new file ready for use, including conversion from previous versions of System Coordinator.

To load the configuration file

1. Load the Adabas System Coordinator configuration file from the distribution medium using the standard Adabas load utility ADALOD. Use sample job CORI050. If you are using an alternate configuration file you need to run this job to initialize both files.

2. If Natural Security is installed, define the libraries SYSCOR and SYSMPvrs (where vrs is the version you are installing, for example 821) and protect as required. You may define MENU as the startup transaction for SYSCOR. DO NOT define a startup transaction for SYSMPvrs.

3. Use the following parameter to define the Natural session where SYSCOR is to be used:

   LFILE=(152,dbid,fnr<,passw><,ciph>)

   where dbid and fnr define the primary Adabas System Coordinator file.

   Alternatively, assemble the Natural parameter module with:

   NTFILE ,ID=152,DBID=dbid,FNR=fnr

To convert a previous version’s definitions to version 8 format

1. Logon to library SYSCOR and enter MENU. SYSCOR will detect that the configuration file is new and will guide you through the steps required to copy and convert the definitions from a previous version.

2. Repeat this procedure for each configuration file to be converted. The procedure only needs to be done once for each configuration file, regardless of how many products use it. Other products may have additional conversion requirements.

Step 4: Assemble the Configuration Module (Job I055)

Adabas System Coordinator parameters are located in the configuration file. At job start, the Adabas System Coordinator needs to know the location of this file. This information is kept in the configuration module.

Create the configuration module by assembling the CORMCFG parameters defining the SVC, database, and file number of the Adabas System Coordinator configuration file.

Name the resulting load module CORCFG (this is required).

Use sample job CORI055.

Step 5: Add the System Coordinator to the Adabas Client (Jobs I060, I080x)

Link the appropriate Adabas System Coordinator client component with your Adabas link modules.

The stub modules are called CORS0n where n is a subsystem suffix.

The modified link module is for use by client jobs only.

Adabas System Coordinator is compatible with Version 8 link modules. You must re-assemble the LNKGBLS table, specifying the parameter COR=YES in the LGBLSET macro.

The load library contains the kernel modules CORKRN and CASKRN, which must also be available to all client jobs that will use the Adabas System Coordinator.

If you are migrating from a previous version, you must ensure that you use the new load library modules. It is not possible to use the Version 8.2 link module stub with Coordinator modules from a previous version. If you need to run multiple versions in a TP monitor client, please see the Versioning Tool section for more information.

Notes:

1. You must use the linkage editor options specified in the sample jobs.
2. The sample install jobs referenced below may not match what is needed for the release of Adabas used at your site. Please refer to your Adabas installation documentation and JCL to ensure you use the appropriate JCL for your release, adjusted for the needs of the sample jobs supplied here.

Step 6: Define a System Coordinator Group

Define your System Coordinator group and member(s). This is required if you intend to use:

• Adabas Fastpath

• clustered applications with dynamic transaction routing.

Job parameters for each product also contain settings that are relevant to the operation of the Adabas System Coordinator. For more information, see SYSCOR Administration.

Step 7: Install the CICS Node Error Program (Optional)

The node error program CORNEP is used by sites running CICS command-level applications in CICS/ESA or CICS Transaction Server for z/OS. It is not an essential component, but it does improve efficiency when reclaiming user memory after user sessions terminate.

CORNEP must be called as a started task (with Transaction ID ANEP) from the real CICS node error program DFHZNEP. If you do not use DFHZNEP, a sample is provided on the source library. If you do use DFHZNEP, you will need to implement the code for starting CORNEP into your own DFHZNEP as shown in the provided sample source.

Following are the required CICS resource definition parameters for CORNEP:

Language: Assembler
RESident: No
Datalocation: Any
EXECKey: User

Note:
To use CORNEP, assemble your Adabas link module with PARMTYP=ALL on the ADAGSET (Version 7 link module) or LGBLSET (Version 8 link module) macro.

Note:
CORNEP must be called only from DFHZNEP.

Step 8: Create Startup Procedures for the System Coordinator Daemon(s)

The following is a job example for running a Adabas System Coordinator daemon:

//SYSCO1 PROC
//*----------------------------------------------------------------*
//* System Coordinator SYSCO Vv.r.s. STARTUP *
//*----------------------------------------------------------------*
//SYSCO1 EXEC PGM=SYSCO,REGION=0M,TIME=1440
//STEPLIB DD DISP=SHR,DSN=SAG.CORvrs.LOAD
// DD DISP=SHR,DSN=ADABAS.Vvrs.LOAD
//SYSUDUMP DD SYSOUT=*
//CORDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDCARD DD DISP=SHR,DSN=SAG.CORvrs.SRCE(CORCNTL)
//*

The file referenced by the DDCARD statement should contain the following control statements:

PRODUCT=CAS

PRODUCT=AFP (If FASTABM is to be run)

FORCE=NO

If SYSCO terminates abnormally, it may be necessary to specify FORCE=YES on restart.

Step 9: Create System Coordinator daemon disk files

Some products require a daemon disk file. This is described in the relevant product documentation. Tailor and run job CORI040 to create each required disk file. Examples of products for which you might need to create disk files are:

• System Coordinator’s latency file for latency management of TP systems.

• Adabas Transaction Manager’s recovery file.

Step 10: Define Runtime Controls for Client Jobs and TP Systems

System Coordinator can be installed for all client jobs, but will be inactive until runtime controls are defined. Controls are defined in the SYSCOR Natural application, using the Maintenance menu. Refer to the Online Services section for further information.

Alternatively, you can delay this task until you have installed the appropriate add-on product(s). You may then use any of the supplied maintenance applications (SYSAFP, SYSAVI or SYSATM).

Installing Adabas System Coordinator in multi-task batch environments

Multi-task batch environments have special requirements. These are discussed below for the most common environment types.

• Installing the Adabas System Coordinator with the Adabas SQL Gateway in z/OS

• Installing Adabas System Coordinator with Natural RPC Batch Server

• Installing Adabas System Coordinator with the Adabas SOA Gateway

• Installing Adabas System Coordinator in 3rd party or in-house multi-task server environments

• Installing Adabas System Coordinator with NIM

Installing the Adabas System Coordinator with the Adabas SQL Gateway in z/OS

• Background
• Common Installation Steps
• Basic Multi-Thread (not APF authorized) Install
• Authorized Multi-Thread Install

Background

The Adabas SQL Gateway uses z/OS UNIX Systems Services to run as a multi-threaded server. This requires re-entrant operation which has additional installation considerations for products based upon Adabas System Coordinator such as Adabas Fastpath, Adabas Vista and Adabas Transaction Manager. Specifically, it is important that a single copy of the Adabas Link Module (ADALNKR) containing the System Coordinator interface (CORS07) is used, and that this module is linked with the attributes specified in the sample CORI080H job.

The Adabas SQL Gateway uses z/OS UNIX Systems Services to run either in basic or authorized multi-threaded server mode. This choice affects the method of installation of the Adabas System Coordinator as the base for Adabas Fastpath, Adabas Vista, Adabas Transaction Manager, etc.

Specifically, it is important that a single copy of the Adabas Link Module (ADALNKR) containing the System Coordinator interface (CORS07) is used, and that this module is linked as specified in the sample CORI080H job.

There are two ways to run the Adabas SQL Gateway which directly affect the way Adabas System Coordinator must be installed:

• Basic multi-thread (not APF authorized): When the Adabas SQL Gateway runs without APF authorization it does not activate its low-level RACF interface.

• Authorized multi-thread (APF authorized): In its authorized state the Adabas SQL Gateway activates its RACF interface.

Common Installation Steps

The following steps are required for both installation types:

1. Complete normal SQL Gateway installation (and make sure it works correctly in isolation) before adding the System Coordinator interface. (See the Installation for z/OS section of the Adabas SQL gateway documentation).

2. Assemble the Adabas Link routine globals module LNKGBLS and link ADALNKR using sample job CORI080H.

3. Modify the Server Job CNXADA. Include the Coordinator load library, plus any installed add-on product libraries (Fastpath, Vista, ATM), in the STEPLIB concatenation. For the authorized installation, all libraries must be APF-authorized.

4. Define the SQL Gateway started task as job type multi-TCB to the desired product(s) in the appropriate administration center: Adabas System Coordinator (SYSCOR), Adabas Fastpath (SYSAFP), Adabas Vista (SYSAVI) and/or Adabas Transaction Manager (SYSATM). See the relevant product documentation for details. The Multi-TCB option is on the second screen of selectable runtime control types, accessible by selecting "more choices for type or" when adding the runtime control.

Basic Multi-Thread (not APF authorized) Install

for this type of operation:

1. Ensure that SQL Gateway basic multi-thread installation is completed before adding the System Coordinator interface.

2. Re-link the module named CNXRUNA with the REUS attribute, replacing ADALNK with ADAUSER. Here is a sample of the required JCL:

   //LKED   EXEC PGM=IEWL,PARM='REUS'                 
   //ADALIB   DD DSN=ADABAS.VVRS.LOAD,DISP=SHR    ... Adabas library ...   
   //SYSLMOD  DD DSN=PPP.CONNX.LOAD,DISP=SHR     ... Connx Library ...   
   //SYSPRINT DD SYSOUT=*                             
   //SYSLIN   DD *                                    
    REPLACE ADABAS		 ... Delete ADALNK entry ...                                       
    INCLUDE SYSLMOD(CNXRUNA)                               
    INCLUDE ADALIB(ADAUSER)
    ENTRY MAIN                              
    NAME CNXRUNA(R)
   /*
   

   The Linkage Editor will produce warning messages indicating that some Csects are not re-usable. These can be ignored.

3. Re-link the module named CNXADA0B with the REUS attribute, replacing ADALNK with ADAUSER. Here is a sample of the required JCL:

   //LKED   EXEC PGM=IEWL,PARM='REUS'                 
   //ADALIB   DD DSN=ADABAS.VVRS.LOAD,DISP=SHR    ... Adabas library ...   
   //SYSLMOD  DD DSN=PPP.CONNX.LOAD,DISP=SHR     ... Connx Library ...   
   //SYSPRINT DD SYSOUT=*                             
   //SYSLIN   DD *                                    
    REPLACE ADABAS 	    	... Delete ADALNK entry ...                                       
    INCLUDE SYSLMOD(CNXADA0B)                               
    INCLUDE ADALIB(ADAUSER) 
    ENTRY MAIN                              
    NAME CNXADA0B(R)
   /*
   

   The Linkage Editor will produce warning messages indicating that some Csects are not re-usable. These can be ignored.

   Do not specify the RENT atrribute for either of these modules. The linked modules must be re-usable but not re-entrant. Failure to do this will result in the System Coordinator failing with S0C4 (addressing) abends.

Authorized Multi-Thread Install

for this type of operation:

1. Ensure that SQL Gateway authorized multi-thread installation is completed before adding the System Coordinator interface.

2. Re-link the module named CNXRUNA with the RENT and AC=1 attributes, replacing ADALNK with CORLNKR. Here is a sample of the required JCL:

   //LKED   EXEC PGM=IEWL,PARM='RENT,AC=1'                 
   //CORLIB   DD DSN=SAG.CORVRS.LOAD,DISP=SHR   ... COR library ...   
   //SYSLMOD  DD    DSN=PPP.CONNX.LOAD,DISP=SHR  ... Connx Library ...   
   //SYSPRINT DD    SYSOUT=*                             
   //SYSLIN   DD    *                                    
    REPLACE ADABAS		 ... Delete ADALNK entry ...                                       
    INCLUDE SYSLMOD(CNXRUNA)                               
    INCLUDE CORLIB(CORLNKR)
    ENTRY MAIN                              
    NAME CNXRUNA(R)
   /*
   

3. Re-link the module named CNXADA0B with the RENT and AC=1 attributes, replacing ADALNK with CORLNKR. Here is a sample of the required JCL:

   //LKED   EXEC PGM=IEWL,PARM='RENT,AC=1'                 
   //CORLIB   DD DSN=SAG.CORVRS.LOAD,DISP=SHR   ... COR library ...   
   //SYSLMOD  DD    DSN=PPP.CONNX.LOAD,DISP=SHR   ... Connx Library ...    
   //SYSPRINT DD    SYSOUT=*                             
   //SYSLIN   DD    *                                    
    REPLACE ADABAS		 ... Delete ADALNK entry ...                                       
    INCLUDE SYSLMOD(CNXADA0B)                               
    INCLUDE CORLIB(CORLNKR) 
    ENTRY MAIN                              
    NAME CNXADA0B(R)
   /*
   

Installing Adabas System Coordinator with Natural RPC Batch Server

In order for execution with a Natural RPC Batch Server using multiple tasks you must do the following:

1. A multi-TCB type runtime control must be defined for the Natural RPC Batch Server job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.

2. Add module CORS07 to the re-link of the re-entrant Adabas link module: ADALNKR (see sample job CORI080H).

3. The resulting load module must be named according to the requirements of the Natural RPC Server (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.

4. The COR load library must be added to the STEPLIB concatenation of the Natural RPC Server Batch Server job

5. The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the Natural RPC Server Batch Server job.

6. Restart the Natural RPC Server Batch Server.

Installing Adabas System Coordinator with the Adabas SOA Gateway

In order for execution with the Adabas SOA Gateway you must do the following:

1. A multi-TCB type runtime control must be defined for the Adabas SOA Gateway job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.

2. Add module CORS07 to the re-link of the re-entrant Adabas link module: ADALNKR (see sample job CORI080H).

3. The resulting load module must be named according to the requirements of the Adabas SOA Gateway (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.

4. The COR load library must be added to the STEPLIB concatenation of the Adabas SOA Gateway job.

5. The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the Adabas SOA Gateway job.

6. Restart the Adabas SOA Gateway.

Installing Adabas System Coordinator in 3rd party or in-house multi-task server environments

This section applies to 3rd party and customer-written multi-task batch applications designed to use the re-entrant Adabas link module. Note: Quite obviously, these types of environments are unknown to Software AG so the information here is only a guideline on what may be appropriate, the specifics of what is actually appropriate are dictated by the design of the server in question. Therefore you must check with Software AG in case there are any other considerations before implementing.

In order for execution with 3rd party or in-house multi-task server environments you must do the following:

1. A multi-TCB type runtime control must be defined for the multi-task server job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.

2. Add module CORS07 to the re-link of the re-entrant Adabas link module: ADALNKR (see sample job CORI080H).

3. The resulting load module must be named according to the requirements of the multi-task server (for example, ADALNKR) and linked with the attributes specified in sample job CORI080H.

4. The COR load library must be added to the STEPLIB concatenation of the multi-task server job.

5. The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the multi-task server job

6. Restart the multi-task server.

Usually, the server application must ensure that either:

• the task which causes the COR environment to initialize (usually the first task to issue an Adabas call) stays active for the duration of the job

or

• the load modules required for the product are pre-loaded by a task which stays active for the duration of the job. The modules required for COR are listed above (under Job Type CICS Command Level) and each product names its required modules.

Installing Adabas System Coordinator with NIM

In order for execution with the TP system NIM you must do the following:

1. A multi-TCB type runtime control must be defined for the NIM job. Multi-TCB type option is on the second screen of selectable runtime control types…select more choices for type when adding the runtime control to see the multi-TCB choice.

2. Add module CORS07 to the re-link of the re-entrant Adabas link module: ADALNKR (see sample job CORI080N).

3. Add module NIMXFID (see sample job CORI080N).

4. The resulting load module must be named ADALNKR and linked with the attributes specified in sample job CORI080N.

5. The supplied module NIMUEXC must be installed as NIM user exit C, according to the requirements of NIM for using this exit.

6. The supplied module NIMUEXD must be installed as NIM user exit D, according to the requirements of NIM for using this exit.

7. The COR load library must be added to the STEPLIB concatenation of the NIM job.

8. The load library for the additional products being used (Fastpath, Vista, Transaction Manager etc) must be added to the STEPLIB concatenation for the NIM job

9. Restart NIM.

www.softwareag.com

Copyright © 2013 Software AG, Darmstadt, Germany.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT