Install System Maintenance Aid Using Starter System

This section describes how to install SMA using the SMA Starter System and assumes that Adabas and Natural have not been previously installed.

The SMA Starter System can be used to quickly and easily install SMA in a new environment. For this purpose, Adabas und Natural under TSO are needed and will be installed. The SMA Starter System essentially consists of a CLIST which is used to generate four install jobs. These jobs must be executed in the same order as generated in order to complete the installation. Following successful installation, all subsequent Software AG products which are to be installed using SMA can be installed and configured as described in the section Installing Software AG Products with SMA.

• Prerequisites

• Required Products and Data Sets

• Copying the Tape Contents to a z/OS Disk

• Installation Steps

Prerequisites

The SMA Starter System requires the following:

• TSO (including ISPF) must be installed.

• The SMA Starter System requires approximately 320 cylinders of space in the Adabas database to store the Natural and SMA objects supplied by Software AG.

• A free SVC number for the temporary Adabas SVC must be available.

• APF authorization is needed for 2 data sets (see Installation Step 4 below).

Required Products and Data Sets

The following products and data sets are needed for an SMA first time installation:

Products

Data Sets for Adabas (ADA)

Data Sets for Natural (NAT)

Data Sets for the Natural TSO Monitor interface (NTI)

Data Sets for the System Maintenance Aid (SMA)

There are more data sets and products on the installation medium then the ones mentioned above. Please ignore these additional data sets and products. Verify the medium contents using the Software AG Product Delivery Report which accompanies the medium. After the data sets have been copied from the medium to disk (see Copy step described below), they will be extended with a high level qualifier (hilev). This high level qualifier must also be used in Step 1 of the installation described below.

Example:

If 'SAG' is used as a high-level qualifier (hilev) and the SMA version on medium is '211', the following libraries will be copied:

 SAG.SMA211.CLST
 SAG.SMA211.SYSF
 SAG.SMA211.INPL
 SAG.SMA211.ERRN
 

Copying the Tape Contents to a z/OS Disk

This section explains how to:

• Copy data set COPY.JOB from tape to disk.

• Modify this data set to conform with your local naming conventions.

The JCL in this data set is then used to copy all data sets from tape to disk (except the data set SMTvrs.TABS).

If the data sets for more than one product are delivered on the tape, the data set COPY.JOB contains the JCL to unload the data sets for all delivered products from the tape to your disk.

After completing the above, you will have to perform the individual install procedure for each component.

Copying the Installation Tape to Disk under z/OS

If you are already using SMA and wish to use SMA to copy the installation tape for the new SMA version, refer to the section Installing Products.

If you are not using SMA, you must perform the following as described in this section:

• Step 1: Copy Data Set COPY.JOB from Tape to Disk
• Step 2: Modify COPY.JOB for Conformance with Local Naming Conventions
• Step 3: Submit COPY.JOB to Unload Data Sets

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

The data set COPY.JOB (label 2) contains the JCL to unload all other data sets from tape 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 volume serial number

Step 2: Modify COPY.JOB for Conformance with Local Naming Conventions

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 3: Submit COPY.JOB to Unload Data Sets

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

Installation Steps

Perform the following installation steps:

• Step 1: Invoke the CLIST

• Step 2: Enter the Parameters

• Step 3: Check the Information Screen

• Step 4: Give APF Authorization to Data Sets

• Step 5: Submit Jobs JOBI001, JOBI002 and JOBI003

• Step 6: Start Adabas

• Step 7: Submit Job JOBI004

• Step 8: Invoke SMA

Step 1: Invoke the CLIST

Enter the ISPF command mode and invoke the CLIST MENU from the source library that you just copied with the command:

EX '<hilev>.SMAvrs.CLST(MENU)'

The following screen will appear:

===================================================
============ SMA Initial Installation =============
===================================================

>> Please enter High Level Qualifier (<hilev>) or '.' to exit:

The CLIST requests the high level qualifier (<hilev>) of the source library from which it was called. Enter the <hilev> and press Enter. (This is necessary because in the CLIST language it is not possible to determine the library from which the CLIST was called.).

>> Please enter the 3 digit SMA version (i.e.211) or '.' to exit:

This next line asks you for the version of the SMA (for example: '211') which is used on the product installation medium. Enter the 3-digit version of SMA and press Enter.

Step 2: Enter the Parameters

A screen similar to the following will now appear:

*****************************************************************************
Please enter the following parameters:

NATURAL Version (ie: 424): ...
ADABAS Version  (ie: 813): ...

Adabas SVC numb.(ie: 249): ...

Tape Volume  (ie: T12345): T.....

Job Line 1.. //JOB@JNR JOB ACCT,REGION=4M,MSGLEVEL=(1,1),
Job Line 2.. // CLASS=G,MSGCLASS=X
Job Line 3.. /*JOBPARM LINES=9999

Note: @JNR in Job Line 1 is used as a parameter, which will
be replaced during generation with the job number.
It is recommended to leave it untouched.
*****************************************************************************
Enter '.' to exit or 'OK' to start job generation:

Enter the following parameters:

Example:

*****************************************************************************
Please enter the following parameters:

NATURAL Version (ie: 424): 424
ADABAS Version  (ie: 813): 813

Adabas SVC numb.(ie: 249): 232

Tape Volume  (ie: T12345): T23545

Job Line 1.. //SAG@JNR JOB ACCT,REGION=4M,MSGLEVEL=(1,1),
Job Line 2.. // CLASS=O,MSGCLASS=Z
Job Line 3.. //*JOBPARM LINES=9999

Note: @JNR in Job Line 1 is used as a parameter, which will
be replaced during generation with the job number.
It is recommended to leave it untouched.
*****************************************************************************
Enter '.' to exit or 'OK' to start job generation:

After you entered all the necessary parameters, enter 'OK' and press Enter.

The SMA Starter System for z/OS now generates the JCL (JOBI001-JOBI004) and creates the following 3 libraries:

There will be 4 jobs generated into library <hilev>.SMAvrs.JCL:

JOBI001: Prepare the necessary license keys

JOBI002: Installs the Adabas Components

JOBI003: Installs the Natural Components

JOBI004: Load Data into the Adabas System Files

Step 3: Check the Information Screen

After successful generation of the installation jobs into the library hilev.SMAvrs.JCL, the following information screen will appear:

Now perform the following steps to complete the installation:
-------------------------------------------------------------
(Step 4) The following libraries needs APF authorization:
         >> hilev.SMAvrs.SMALOAD
         >> hilev.ADAvrs.LOAD

(Step 5) Submit the jobs JOBI001-003 in lib hilev.SMAvrs.JCL.

(Step 6) Start ADABAS with the procedure hilev.SMAvrs.SMASRCE(ADATASK).

(Step 7) Submit the job JOBI004 in lib hilev.SMAvrs.JCL.

(Step 8) Start SMA with the CLIST hilev.SMAvrs.SMASRCE(SMA).
-------------------------------------------------------------
Enter '.' to exit:

This screen gives you information of what to do next (see also Steps 4-8 below).

Step 4: Give APF Authorization to Data Sets

The Adabas SVC installation requires that the data sets hilev.SMAvrs.SMALOAD and hilev.ADAvrs.LOAD are APF authorized. Please contact your system administrator to perform this step.

Step 5: Submit Jobs JOBI001, JOBI002 and JOBI003

JOBI001 will prepare the license key files for Natural and Adabas. JOBI002 will prepare the Adabas components. JOBI003 will prepare the Natural components.

Step 6: Start Adabas

Copy the procedure created as member ADATASK in library hilev.SMAvers.SMASRCE to the z/OS user proclib where started tasks reside. Then start the Adabas database from that library.

Step 7: Submit Job JOBI004

JOBI004 will load all necessary data into the SMA system files.

Step 8: Invoke SMA

Enter TSO command mode. Enter EX 'hilev.SMAvrs.SMASRCE(SMA)' to start the TSO CLIST and invoke SMA. SMA is now installed and can be used to install other SAG products.