This document describes the installation of Adabas on z/OS systems.

• Step 1: Check, Prepare, and Install the Product License File (SMA job number I007)

• Step 2: Allocate and Format the Adabas Database (SMA Job Number I030)

• Step 3: Define the Global Database Characteristics (SMA Job Number I030)

• Step 4: Load the Demonstration Files (SMA Job Number I050)

• Step 5: Customize and Start the Adabas Nucleus and Test Adabas Communications (SMA Job Number I040)

• Step 6: Load Adabas Online System Add-On Product, If Appropriate (SMA Job Number I061)

---

Step 1: Check, Prepare, and Install the Product License File (SMA job number I007)

You must install a valid license file on all mainframe platforms in which your Software GmbH mainframe product is installed. The license file is provided as an XML document (encoding is US-ASCII) and must remain in that format -- even on the mainframe. It must not be modified. Any modification of the license file will invalidate the digital signature and the license check will fail. In the event of a check failure, please contact your technical support representative.

For a list of license file names, load modules and DD/Link names, refer to Adabas and Add-on Licenses.

In this step, you will prepare the license file (obtain it from e-mail or the installation tape and store it on your z/OS system) and then install it:

Preparing the Product License File

The product license file is supplied on the individual customer installation tape or separately via an e-mail attachment. Before you can install the license, you must transfer it from e-mail or the installation tape and store it on a z/OS system. This section describes how to do this for a license distributed either by e-mail or on the installation tape.

To prepare the license file from an e-mail attachment, complete the following steps:

1. Transfer the license to z/OS, as described in Transferring a License File from PC to a z/OS Host Using FTP.

2. Verify that the transferred license file is stored in an Adabas source library (with RECFM=F or FB and LRECL=80), taking care to preserve its format as ASCII.

To prepare the license file from the installation tape, complete the following steps:

• Verify that the license file is stored from the tape into an Adabas source library (with RECFM=F or FB and LRECL=80), taking care to preserve its format as ASCII.

Installing the Product License File

Once the license file has been prepared, you can install it in one of two ways:

• You can convert the license to a load module (ADALIC) that is then loaded by the Adabas nucleus.

• You can reference the license file in the Adabas nucleus startup job by DD statement.

The following describes both methods.

To convert the license file to a load module, complete the following steps:

1. Review and modify sample job ASMLICAM, as follows:

   • Change the STEPLIB DD statement to point to the license load library (MLCvrs.LOAD).

   • Change the SYSUT1 DD statement to point to the data set containing the Adabas license file you transferred to z/OS earlier.

   • Specify an appropriate user load library for the L.SYSLMOD DD statement.

     Note
     This user load library must also be included in the STEPLIB concatenation for the Adabas nucleus (ADANUC).

2. Submit sample job ASMLICAM. This job runs the MAKE function of the LICUTIL utility to convert the license text file to an assembler source module. ASMLICAM then links and assembles the assembler source to generate a load module called ADALIC, which is stored in the specified user load library (L.SYSLMOD DD statement). For more information about the LICUTIL utility, read Using The License Utility: LICUTIL

3. Update your Adabas ADANUC nucleus job to reference the user load library so ADALIC will be loaded by the Adabas nucleus, as described in Step 5: Customize and Start the Adabas Nucleus and Test Adabas Communications.

To reference the license file in the Adabas nucleus startup job, complete the following steps:

1. Make sure any previously created ADALIC load module is inaccessible to the Adabas load library being used by your nucleus job. Adabas first tries to load ADALIC and, if unsuccessful, it reads from a DDLIC data set referenced in ADANUC.

2. Update your Adabas ADANUC nucleus jobs to reference the license, as described in Step 5: Customize and Start the Adabas Nucleus and Test Adabas Communications.

Step 2: Allocate and Format the Adabas Database (SMA Job Number I030)

Customize and run the ADAFRM utility job to allocate and format the Adabas database. The following must be customized:

• Data set names for the database and libraries;

• Volumes for libraries and data sets for the database;

• Space allocation for data sets for the database;

• The Adabas SVC number, the database ID, and database device type(s);

• Sizes of the data sets for each ADAFRM statement.

Step 3: Define the Global Database Characteristics (SMA Job Number I030)

Customize and run the ADADEF utility job to define the global definition of the database. The following must be customized:

• Data set names of the database and libraries;

• The Adabas SVC number, the database ID, and database device type(s);

• ADADEF parameters.

Step 4: Load the Demonstration Files (SMA Job Number I050)

Customize and run the job:

• ADALODE to load the sample demo file EMPL;

• ADALODV to load the sample demo file VEHI;

• ADALODM to load the sample demo file MISC; and

• ADALODP to compress and load the sample Personnel (PERC) demo file and its associated LOB demo file.

  Note
  The Personnel demo file must be installed on a UES-enabled database because it includes wide-character format (W) fields.

For each job, the following items must be customized:

• Data set names for the database and libraries;

• The Adabas SVC number, the database ID, and database device type(s);

• ADALOD parameters.

Step 5: Customize and Start the Adabas Nucleus and Test Adabas Communications (SMA Job Number I040)

Customize and run an appropriate ADANUC job to start the Adabas nucleus. (This processing will also test basic Adabas communications.) The following modifications to the ADANUC job must be made:

1. Our licensing requires that the modules LICMAIN and LICUTIL be loaded when your nucleus starts up. These modules are distributed in the MLCvrs.LOAD library. You must either:

   • Copy LICMAIN and LICUTIL into ADAvrs.LOAD; or

   • Concatenate MLCvrs.LOAD with ADAvrs.LOAD. A sample job, ADANUCS, demonstrates how to do this.

2. Verify that the appropriate product/sub product license file is correctly referenced in the ADANUC job.

   Do either of the following:

   • Verify that the license load module(s) installed in Step 1: Check, Prepare, and Install the Product License File, is/are stored in a load library that is accessible to the Adabas load library. Add the user load library in which license load module(s) reside(s) to the STEPLIB concatenation of the Adabas nucleus job or copy the licensing library into ADAvrs.LOAD.

   • Verify that there is/are no appropriate product/sub product load module(s) accessible to the Adabas load library and that the following DD statement is included in the ADANUC job for each appropriate product/sub product utilized:

     //DDLIC     DD  DISP=SHR,DSN=dsn
     //DDLAZPAD  DD  DISP=SHR,DSN=dsn
     //DDLACF    DD  DISP=SHR,DSN=dsn
     //DDLADE    DD  DISP=SHR,DSN=dsn
     //DDLAEZ    DD  DISP=SHR,DSN=dsn
     //DDLALA    DD  DISP=SHR,DSN=dsn
     //DDLALS    DD  DISP=SHR,DSN=dsn
     //DDLASM    DD  DISP=SHR,DSN=dsn
     //DDLAOS    DD  DISP=SHR,DSN=dsn

     where dsn is the data set name of the license file loaded from the tape (in ASCII format). Note that dsn could reference a member in a partitioned data set.

     Note
     Adabas first tries to load the license load module and, if unsuccessful, it reads from the DDLccccc data set.

     For a list of license file names, load modules and DD/Link names, refer to Adabas and Add-on Licenses.

3. Data set names for the database and libraries must be customized for your installation.

   Note
   Be sure to include appropriate user load libraries.

4. The Adabas SVC number, the database ID, and database device type(s) must be customized for your installation.

5. ADARUN parameters must be customized for your installation.

Step 6: Load Adabas Online System Add-On Product, If Appropriate (SMA Job Number I061)

Customize and run the job ADAINPL to load the Adabas Online System (AOS) into a Natural system file using the appropriate batch version of Natural (read the Adabas Online System documentation to determine its Natural requirements). The following items must be customized:

• Data set names of the database and libraries;

• The Adabas SVC number, the database ID, and device type(s);

• The Natural INPL parameters and system file number.

Alternatively, install the AOS demo version delivered with Adabas: see the section Installing the AOS Demo Version.