Install System Maintenance Aid

This section describes how to install SMA and assumes that Adabas and Natural have already been previously installed.

SMA is an application completely written in Natural. SMA data is stored in an Adabas database.

SMA can be installed easily into an existing Adabas/Natural environment.

Prerequisites

SMA requires the following Software AG products:

  • A supported version of Natural must be installed. For the supported operating systems and versions, refer to the Product Version Availability section of Software AG's Empower web site at https://empower.softwareag.com/.

  • A supported version of Adabas must be installed. For the supported operating systems and versions, refer to the Product Version Availability section of Software AG's Empower web site at https://empower.softwareag.com/.

Copying Data Sets from the Installation Medium

Installation Medium

The product installation medium (e.g., tape or CD-ROM) contains the data sets listed in the table below. The sequence of the data sets is shown in the Software AG Product Delivery Report which accompanies the installation medium.

Data Set Description
SMAvrs.INPL SMA programs
SMAvrs.SYSF SMA system file
SMAvrs.JOBS Library with SMA example jobs (z/OS and BS2000/OSD)
SMAvrs.LIBJ Sublibrary with SMA example jobs (z/VSE only)

The notation vrs in data set names represents the version number of the product.

The data set type and the space each data set requires on disk is shown in the Software AG Product Delivery Report.

Copying Data Sets to Disk under z/OS

Copy the data sets from the supplied installation medium to your disk before you perform the individual installation procedure for each component to be installed.

The way you copy the data sets depends on the installation method and the medium used:

  • If you are already using SMA, refer to the section Installing Software AG Products with SMA.

  • If you are not using SMA and want to copy the data sets from CD-ROM, refer to the README.TXT file on the CD-ROM.

  • If you are not using SMA and want to copy the data sets from tape, follow the instructions in this section.

This section explains how to copy all data sets from tape to disk.

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

  • Modify the following sample job according to your requirements:

    //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=tape-volser),
// LABEL=(2,SL)
//SYSUT2 DD DSN=hilev.COPY.JOB,
// DISP=(NEW,CATLG,DELETE),
// UNIT=3390,VOL=SER=disk-volser,
// SPACE=(TRK,(1,1),RLSE),
// DCB=*.SYSUT1
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//

    where:

    tape-volser is the VOLSER of the tape, for example: T12345,
    hilev is a valid high-level qualifier, and
    disk-volser is the VOLSER of the disk.

  • Execute the job to copy the data set COPY.JOB to your disk.

Step 2: Modify hilev.COPY.JOB on Your Disk

  • Modify hilev.COPY.JOB according to your requirements:

    Set EXPDT to a valid expiration date, for example, 99365.

    Set HILEV to a valid high-level qualifier, for example, USERLIB.

    Set LOCATION to a storage location, for example, STORCLAS=ABC or UNIT=3390,VOL=SER=USR123.

Step 3: Submit COPY.JOB

  • Execute hilev.COPY.JOB to copy single, multiple, or all data sets to your disk.

Copying Data Sets to Disk under z/VSE

Copy the data sets from the supplied installation medium to your disk before you perform the individual installation procedure for each component to be installed.

The way you copy the data sets depends on the installation method and the medium used:

  • If you are already using SMA, refer to the section Installing Software AG Products with SMA.

  • If you are not using SMA and want to copy the data sets from CD-ROM, refer to the README.TXT file on the CD-ROM.

  • If you are not using SMA and want to copy the data sets from tape, follow the instructions in this section.

This section explains how to copy the data sets .LIBJ, .LIBR and .LICS (if supplied) from tape to disk. All other data sets can be installed directly from the tape.

Step 1: Copy Data Set COPYTAPE.JOB to Disk

  • Modify the following sample job according to your requirements:

    * $$ JOB JNM=LIBRCAT,CLASS=0,                                          + 
* $$ DISP=D,LDEST=(*,UID),SYSID=1                                       
* $$ LST CLASS=A,DISP=D                                                  
// JOB LIBRCAT                                                           
* *****************************************                              
*     STORE COPYTAPE.JOB IN LIBRARY                                    
* *****************************************                              
// ASSGN SYS004,nnn 
// MTC REW,SYS004                                                        
// MTC FSF,SYS004,4                                                      
ASSGN SYSIPT,SYS004                                                      
// TLBL IJSYSIN,'COPYTAPE.JOB'                                           
// EXEC LIBR,PARM='MSHP; ACC S=lib.sublib'
/*
// MTC REW,SYS004                                                                       
ASSGN SYSIPT,FEC                                                         
/*                                                                       
/&                                                                     
* $$ EOJ

    where:

    nnn is the tape address, and
    lib.sublib is the library and sublibrary in which the data set COPYTAPE.JOB is to be stored.

  • Execute the job to copy the data set COPYTAPE.JOB to disk.

    COPYTAPE.JOB contains the JCL required to copy the data sets .LIBJ, .LIBR and .LICS from tape to disk.

Step 2: Modify COPYTAPE.JOB on Your Disk

  • Modify COPYTAPE.JOB according to your requirements and set the disk space parameters as appropriate.

Step 3: Submit COPYTAPE.JOB

  • Execute COPYTAPE.JOB to copy the data sets .LIBJ, .LIBR and .LICS to your disk.

Copying Data Sets to Disk under BS2000/OSD

Copy the files (data sets) from the supplied installation medium to your disk before you perform the individual installation procedure for each component to be installed.

The way you copy the files depends on the installation method and the medium used:

  • If you are already using SMA, refer to the section Installing Software AG Products with SMA.

  • If you are not using SMA and want to copy the files from CD-ROM, refer to the README.TXT file on the CD-ROM.

  • If you are not using SMA and want to copy the files from tape, follow the instructions in this section.

This section explains how to copy all files from tape to disk.

Step 1: Copy Library SRVvrs.LIB from Tape to Disk

This step is not necessary if you have already copied the library SRVvrs.LIB from another Software AG installation tape. For further information, refer to the element #READ-ME in this library. The library SRVvrs.LIB is stored on the tape as a sequential file named SRVvrs.LIBS containing LMS commands. The current version vrs can be obtained from the Software AG Product Delivery Report.

  • Execute the following commands to convert SRVvrs.LIBS into an LMS library: 

    /IMPORT-FILE  SUPPORT=*TAPE(FILE-NAME=SRVvrs.LIBS,-
/   VOLUME=volser, DEV-TYPE=tape-device)
/ADD-FILE-LINK  LINK-NAME=EDTSAM, FILE-NAME=SRVvrs.LIBS,-
/   SUPPORT=*TAPE(FILE-SEQ=3), ACC-METH=*BY-CAT,-
/   BUF-LEN=*BY-CAT, REC-FORM=*BY-CAT, REC-SIZE=*BY-CAT
/START-EDT 
@READ  '/'
@SYSTEM 'REMOVE-FILE-LINK  EDTSAM'
@SYSTEM 'EXPORT-FILE  FILE-NAME=SRVvrs.LIBS'
@WRITE  'SRVvrs.LIBS'
@HALT
/ASS-SYSDTA  SRVvrs.LIBS
/MOD-JOB-SW  ON=1
/START-PROG  $LMS
/MOD-JOB-SW  OFF=1
/ASS-SYSDTA  *PRIMARY

    where:

    tape-device is the device type of the tape, for example, TAPE-C4, and
    volser is the VOLSER of the tape (see the Software AG Product Delivery Report).

Step 2: Copy the Procedure COPY.PROC from Tape to Disk

  • Call the procedure P.COPYTAPE in the library SRVvrs.LIB to copy the procedure COPY.PROC to disk: 

    /CALL-PROCEDURE  (SRVvrs.LIB,P.COPYTAPE), -
/   (VSNT=volser, DEVT=tape-device)

    If you use a TAPE-C4 device, you can omit the parameter DEVT.

Step 3: Copy all Product Files from Tape to Disk

  • Enter the procedure COPY.PROC to copy all product files to disk: 

    /ENTER-PROCEDURE  COPY.PROC, DEVT=tape-device

    If you use a TAPE-C4 device, you can omit the parameter DEVT.

    The result of this procedure is written to the file L.REPORT.SRV.

SMA Installation

The following steps are required for installation of SMA:

Step 1: Prepare the SMA System File

Creating a New SMA System File

If you want to create a new SMA system file, you can use job I050, step 1800.

This job loads the empty SMA system file (data set SMAvrs.SYSF) using the ADALOD utility.

Use the following options in this ADALOD step:

  USERISN=YES
  ISNREUSE=YES
  VERSION=6
  MAXISN=40000, DSSIZE=300B, NISIZE=300B, UISIZE=100B

Note:
Option USERISN is essential for the correct operation of SMA. For the Adabas nucleus, allow for approximately 500 ISNs to be kept in the hold queue: NH=2000 NI=500.

Using an Existing SMA System File

If you want to continue to use an existing SMA system file from SMA Version 1.3, you must migrate this system file to an SMA Version 2.1 system file.

Submit job I051, step 1800 to perform the migration from SMA Version 1.3 or 2.1.1.

Additionally, submit job I051, steps 1801 and 1802 to perform the migration from SMA Version 1.3.

Step 2: Load Natural Programs and Load Error Messages

Load the SMA Natural programs (SMAvrs.INPL) into the Natural system file using the Natural INPL utility (job I061, step 1800).

Step 3: Specify Natural Parameters

Whenever you invoke Natural to work with SMA, do either of the following:

  • append the following macro definition:

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

    in your Natural parameter module, where dbid is the database ID and fnr is the file number where you loaded the SMA data file. Then re-assemble and re-link the Natural parameter module.

  • or, use the dynamic parameter

    LFILE=(208,dbid,fnr)

The following Natural parameters should be specified:

ESIZE=64 MADIO=0 MAXCL=0

The PRINTER parameter should allow for at least 1 printer in online mode and 3 printers in batch mode. If no physical or logical printer is available, set Printer ID to DUMMY or blank in the SMA Profile. See SMA Profile in the section Menus and Line Commands for an explanation of this parameter.

SMA uses the Software AG Editor. For more information, refer to the section Installing the Software AG Editor in the Natural documentation.

Depending on the Natural TP environment, the following specification may also be necessary: 

RJESIZE=32

Step 4: SMA Under Natural Security

When using SMA with Natural Security, the following prerequisites must be fulfilled:

  • The library SYSSMA1 must be defined in Natural Security

  • SMA uses the Natural Command Processor, which must also be defined in Natural Security. This can be done by performing the following actions:

    • enter Natural Security Library Maintenance

    • modify library SYSSMA1

    • select Additional Options

    • select Functional Security

    • enter SMACPROC in the field Command Processor, and mark the Keyword default field. After pressing Enter, the field Functional security defined should be set to Yes, and Keyword default should be allowed.

    • exit Natural Security

Step 5: Load SMA Tables

Submit job TABLOAD to load the SMA tables from the product installation medium into the SMA system file.

Installation Verification

Perform the following steps to verify correct SMA installation:

  1. Invoke online Natural by entering the following command:

    LOGON SYSSMA1 
MENU 
A

  2. Adapt the GLOBAL parameters and the SMA profile.

  3. Use function Tabload from the SMA administration menu to load the TABS data from the installation medium.

  4. Enter the SMA Environment function, issue line command CO for your default environment, in the new environment mark the most current version of ADA to be installed.

  5. Enter the SMA Report function, invoke report P for the newly created environment, mark for printing.

  6. Submit a batch Natural job, with the following input:

    LOGON SYSSMA1 
MENU
SET ENV <your-new-environment>
GEN
FIN

  7. Enter online Natural again, enter the Environment function, and issue line command JO to see the jobs generated to install Adabas.

Note:
At this point, the generated JCL is intended only for installation verification testing.