z/OS Systems Installation

#### Search Results

Search

# z/OS Systems Installation

This section describes the preparation for and installation of Adabas Parallel Services on z/OS systems.

Important
Before proceeding with the installation, ensure that the prerequisite environment has been established. Review the earlier sections of this part of the documentation for detailed information.

The installation procedure outlined in this section corresponds to the jobs that SMA creates to install the product.

- Step 1: APF-Authorize All Load Libraries

- Step 2: Customize ADACOM

- Step 3: Create a Startup Procedure for ADACOM

- Step 4: Create a Startup Procedure for Each Cluster Nucleus

- Step 5: Modify the z/OS Common Storage (CSA) Key

- Step 6: Start Adabas Parallel Services

## Step 1: APF-Authorize All Load Libraries

Ensure that Adabas Parallel Services runs authorized.

To run authorized, the Adabas version load libraries and all other load libraries in the STEPLIB concatenation must be APF-authorized. .

- Ensure that all load libraries referenced in the STEPLIB concatenation for your Entire Net-Work, ADACOM, and Adabas cluster nuclei startup procedures are defined to the operating system as authorized libraries. If this is not done, ADACOM or the cluster nuclei will not initialize and may abnormally terminate, usually with an ABENDS047 or ABENDS306.

  Either copy the base Adabas modules and the Adabas Parallel Services modules to an existing APF-authorized library or APF-authorize the Adabas load library unloaded from the base Adabas installation tape

## Step 2: Customize ADACOM

Make any needed additions and modifications to the ADACOM member.

Read ADACOM Initialization Parameters for more information about specifying values for ADACOM parameters.

## Step 3: Create a Startup Procedure for ADACOM

An ADACOM initialization task is provided. This task must be active on the operating system image before any Adabas Parallel Services cluster nucleus is started. All load libraries in the STEPLIB concatenation of ADACOM must be APF-authorized.

ADACOM allocates the nucleus table for monitoring the active nuclei and the user table for monitoring users in the extended CSA (ECSA) above the 16MB line.

- The following is a sample job for running ADACOM:

      //ADACOM PROC
      //*-------------------------------------------------------------*
      //*     ADABAS PARALLEL SERVICES ADACOM Vv.r.s STARTUP          *
      //*-------------------------------------------------------------*
      //ASMvrs EXEC PGM=ADARUN,REGION=4M,TIME=1440
      //STEPLIB  DD DISP=SHR,DSN=ADABAS.Vvrs.LOAD
      //*
      //COMPRINT DD SYSOUT=*
      //DDPRINT  DD SYSOUT=X
      //DDCARD DD *
      ADARUN PROGRAM=ADACOM
      /*
      //DDKARTE DD *
      ADACOM SVC=sv1,DBID=dbid1,NU=150
      ADACOM SVC=sv1,DBID=dbid2,NU=150,F=Y
      ADACOM SVC=sv2,DBID=dbid1,NU=500
      ADACOM SVC=sv2,DBID=dbid3,NU=500
      /*

  The COMPRINT DD statement must be specified when running ADACOM. It defines an output data set for all general messages printed by ADACOM. For each SVC/DBID set specified in the ADACOM task, two subtasks are attached and SYSOUT data sets are dynamically allocated to receive all messages specific to that combination. The DD-name of the SYSOUT data sets are "Pssddddd" and "Dssddddd", where ss represents the last two digits of the SVC number and ddddd are the five digits of the DBID.

  ADACOM can also be installed as a started task; no special considerations apply.

  You may also want to add the ADACOM task's start command to member COMMNDxx of SYS1.PARMLIB; this enables the ADACOM task to begin automatically at IPL.

## Step 4: Create a Startup Procedure for Each Cluster Nucleus

Complete the following steps:

1. Customize a startup procedure to execute ADARUN.

   For each Adabas cluster nucleus, customize the appropriate startup parameters and execute ADARUN from the Adabas load library.

2. The following sample JCL (job ASMNUC in the MVSJOBS data set) executes the Adabas ADARUN program to implement session parameters for an Adabas Parallel Services cluster nucleus.

   Note that the Adabas Parallel Services library is concatenated ahead of the Adabas library in the STEPLIB.

       //ADANUC    JOB   MSGCLASS=X,TIME=1440
       //*----------------------------------------------------------
       //*   THIS IS A STARTUP JOB FOR A PARALLEL SERVICES NUCLEUS
       //*
       //*   THE ADARUN PARMS HAVE TO BE CUSTOMIZED
       //*   DEPENDING ON THE USER'S ENVIRONMENT
       //*   DETAILS ARE PROVIDED IN THE OPERATIONS MANUAL
       //*--------------------------------------------------------
       //NUC      EXEC PGM=ADARUN,REGION=10M
       //STEPLIB DD   DISP=SHR,DSN=ADABAS.Vvrs.LOAD     <=== ADABAS LOAD
       //DDASSOR1  DD   DISP=SHR,DSN=EXAMPL.DByyy.ASSOR1  <=== ASSO
       //DDDATAR1  DD   DISP=SHR,DSN=EXAMPL.DByyy.DATAR1  <=== DATA
       //DDWORKR1  DD   DISP=SHR,DSN=EXAMPL.DByyy.WORKR1  <=== WORK
       //DDPLOGR1  DD   DISP=SHR,DSN=EXAMPL.DByyy.PLOGR1  <=== PLOG1
       //DDPLOGR2  DD   DISP=SHR,DSN=EXAMPL.DByyy.PLOGR2  <=== PLOG2
       //DDDRUCK   DD   SYSOUT=X
       //DDPRINT   DD   SYSOUT=X
       //MPMDUMP   DD   SYSOUT=X
       //DDCARD    DD   *
       ADARUN PROG=ADANUC
       ADARUN CLUSTER=LOCAL
       ADARUN MODE=MULTI
       ADARUN SVC=num               <--- INSERT YOUR SVC NUMBER
       ADARUN DBID=yyy              <--- INSERT YOUR DATABASE ID
       ADARUN NUCID=nnnnn           <--- INSERT YOUR NUCLEUS ID
       ADARUN CLUCACHESIZE=size     <--- INSERT YOUR CACHE SIZE
       ADARUN CLULOCKSIZE=size      <--- INSERT YOUR LOCK SIZE
       ADARUN DEVICE=3390
       ADARUN CT=60
       ADARUN OPENRQ=NO             ---> DEFAULT = YES
       ADARUN PLOGRQ=NO             ---> DEFAULT = YES
       ADARUN LBP=900000
       ADARUN LFIOP=300000
       ADARUN LCP=10000
       ADARUN LFP=12000
       ADARUN LWP=350000
       ADARUN LI=10000
       ADARUN LS=20000
       ADARUN LU=65535
       ADARUN LP=1500
       ADARUN NAB=16
       ADARUN NISNHQ=1000           ---> FOR BATCH NATURAL INPL
       ADARUN NT=8
       ADARUN TT=600
       ADARUN TNAA=600
       ADARUN TNAE=600
       ADARUN TLSCMD=300
       ADARUN DUALPLS=6750          ---> 50 CYL
       ADARUN DUALPLD=3390
       ADARUN LOGGING=NO
       /*

## Step 5: Modify the z/OS Common Storage (CSA) Key

If necessary, modify the z/OS Common Storage (CSA) key.

With z/OS version 1.9, the default setting of the ALLOWUSERKEYCSA parameter has been changed to NO, prohibiting the allocation of CSA storage in a non-privileged storage key. In past releases of Adabas Parallel Services, its data structures in common storage (PLXCB and subordinate control blocks) were stored in user key storage. Due to the change of the ALLOWUSERKEYCSA default, you must either change the ALLOWUSERKEYCSA setting in z/OS 1.9 to YES or accept the ALLOWUSERKEYCSA default setting in z/OS 1.9 (NO). If you accept the default, you will need to modify your Adabas Parallel Services installation and the Adabas Parallel Services and ADACOM startup procedures to use a system key.

For more information, read Modifying the z/OS Common Storage (CSA) Key

## Step 6: Start Adabas Parallel Services

To start Adabas Parallel Services, complete the following steps:

1. Start the ADACOM initialization task on the operating system image that is hosting the Adabas Parallel Services cluster environment.

2. Start the Adabas Parallel Services cluster nuclei in any order.

   The Adabas Parallel Services cluster is now ready to process user requests.

   Rules for subsequent starts of Adabas Parallel Services are described in Restart/Recovery Processing .

### On this page

- Step 1: APF-Authorize All Load Libraries
- Step 2: Customize ADACOM
- Step 3: Create a Startup Procedure for ADACOM
- Step 4: Create a Startup Procedure for Each Cluster Nucleus
- Step 5: Modify the z/OS Common Storage (CSA) Key
- Step 6: Start Adabas Parallel Services