Installing Natural on BS2000

This document describes the steps for installing Natural (product code NAT) on BS2000.

Related Topic:

For information on how to run Natural in a BS2000 environment, see the relevant section in the Operations documentation.

Notation vrs or vr:

When used in this document, the notation vrs or vr represents the relevant product version (see also Version in the Glossary).


Prerequisites

See General Prerequisites and System Support.

Installation Medium

The installation medium contains the following files required for product installation:

File Name Contents
ICSvrs.MOD Load modules and object modules for International Components for Unicode for Software AG (ICS)
MLCvrs.JOBS Sample installation jobs for Software AG's mainframe license check software

The vrs in the library name represents the version of the license check software, which is not necessarily the same as the version of Natural.

For detailed information on the license check software, see Software AG Mainframe Product Licensing.

MLCvrs.MOD Load modules and object modules for Software AG's mainframe license check software including the LICUTIL license utility

The vrs in the library name represents the version of the license check software, which is not necessarily the same as the version of Natural.

For detailed information on the license check software and the LICUTIL utility, see Software AG Mainframe Product Licensing.

NATvrs.LICS Product license file

For information on the license file and product licensing, see Software AG Mainframe Product Licensing.

NATvrs.SRC Source modules
NATvrs.SYSF Natural system file definitions
NATvrs.MOD Load modules and object modules
NATvrs.MAC Macros
NATvrs.JOBS Sample installation jobs
NATvrs.INPL Natural objects
NATvrs.EXPL Natural example objects

Note:
The file NATvrs.JOBS will be converted automatically into an LMS library when it is copied from the installation medium to disk.

Copying Files to a BS2000 Disk

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 use System Maintenance Aid (SMA), refer to the copy job instructions provided in the System Maintenance Aid documentation.

  • 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.

Installation Procedure

Be sure to read Installation Process and Major Natural Features and Naming Conventions for Installation Procedures before you start the installation procedure.

Step 1: Prepare, Convert, Assemble and Link the License File

(Job I010, Steps 0110, 0111, 0112)

You must install a valid Natural license file.

For detailed information on the license file and product licensing, see Software AG Mainframe Product Licensing.

  1. Copy the license file from the supplied installation medium to disk or transfer it from the PC as described in Transferring a License File from PC to a BS2000 Host Using FTP in Software AG Mainframe Product Licensing.

  2. Check, convert, assemble and link the license file:

    Step 0110 Check license file NATvrs.LICS. This job runs the CHECK function of the LICUTIL license utility (see below).
    Step 0111 Convert license file into an assembler source. This job runs the MAKE function of the LICUTIL license utility (see below).
    Step 0112 Assemble and link the assembler source to generate load module ANATLIC. This module is then linked to the nucleus in Job I060.

    The functions and option settings provided by LICUTIL are described in Using the License Utility: LICUTIL in Software AG Mainframe Product Licensing.

Step 2: Load the FNAT System File Definition

(Job I050, Step 0100)

Skip this step if you want to use an existing Natural FNAT system file.

Load the new Natural FNAT system file definition:

  1. Specify the database ID and file number of the Adabas file where to load the new FNAT system file definition by using the Adabas ADALOD utility.

    In addition, you must specify this database ID and file number in the Natural parameter module as described in Step 9: Build the Natural Parameter Module.

  2. Load the FNAT system file definition contained in the NATvrs.SYSF file by using the Adabas ADALOD utility.

    The following ADALOD utility parameter must not be changed:

    ISNREUSE=YES

    The following ADALOD utility parameter setting is recommended:

    USERISN=YES

    If you reorganize an FNAT file or if you unload from or load data to the FNAT file (for example, by using ADAULD/ADALOD), you must specify the parameter USERISN=YES for the ADALOD utility to avoid Natural errors NAT7397 and NAT9988 which require that you re-INPL the Natural FNAT system file.

    If you specify the parameter USERISN=YES when you load a new FNAT system file, and you unload data from this FNAT file, the ADALOD utility assumes USERISN=YES as a default setting when reloading the data into the FNAT file.

Step 3: Load the FUSER System File Definition

(Job I050, Step 0101)

Skip this step if you want to use an existing Natural FUSER system file.

Load the new Natural FUSER system file definition:

  1. Specify the database ID and file number of the Adabas file where to load the new FUSER system file definition by using the Adabas ADALOD utility.

    In addition, you must specify this database ID and file number in the Natural parameter module as described in Step 9: Build the Natural Parameter Module.

  2. Load the FUSER system file definition contained in the NATvrs.SYSF file by using the Adabas ADALOD utility.

    The following ADALOD utility parameter must not be changed:

    ISNREUSE=YES
  3. If you want to use existing Natural applications, copy all user-written objects to the empty FUSER.

  4. If you want to use Natural Application Programming Interfaces (APIs), see Using a Natural API in the SYSEXT Utility documentation for further guidance.

Step 4: Load the Scratch-Pad File Definition

This step is only required if you want to use read-only system files. See also Natural Scratch-Pad File in the Operations documentation.

You can skip this step if you want to use an existing Natural scratch-pad file.

This step is not supported by System Maintenance Aid (SMA).

Load the new Natural scratch-pad system file definition:

  1. Specify the database ID and file number of the Adabas file where to load the scratch-pad file by using the Adabas ADALOD utility.

    In addition, you must specify this database ID and file number in the Natural parameter module as described in Step 9: Build the Natural Parameter Module.

  2. Load the scratch-pad system file definition contained in the NATvrs.SYSF file by using the Adabas ADALOD utility.

    The following ADALOD utility parameter must not be changed:

    ISNREUSE=YES

Step 5: Load the FREG System File Definition

(Job I050, Step 0104)

This step is only required if registry information must be available to control concurrent user sessions limited with the Natural profile parameter UCONMAX (see the Parameter Reference documentation).

You can skip this step if you want to use an existing Natural FREG system file.

This step is not supported by System Maintenance Aid (SMA).

Load the new Natural FREG system file definition:

  1. Specify the database ID and file number of the Adabas file where to load the FREG system file by using the Adabas ADALOD utility.

    In addition, you must specify this database ID and file number in the Natural parameter module as described in Step 9: Build the Natural Parameter Module.

  2. Load the FREG system file definition contained in the NATvrs.SYSF file by using the Adabas ADALOD utility.

    The following ADALOD utility parameter must not be changed:

    ISNREUSE=YES

Step 6: Load the FDIC System File Definition

(Job I050, Step 0103)

Skip this step:

  • if you want to install Predict. In this case, use the corresponding installation step described in the Predict Installation documentation.

  • if you want to use an existing Natural FDIC system file.

Load the new Natural FDIC system file definition:

  1. Specify the database ID and file number of the Adabas file where to load the new FDIC system file definition by using the Adabas ADALOD utility.

    In addition, you must specify this database ID and file number in the Natural parameter module as described in Step 9: Build the Natural Parameter Module.

  2. Load the FDIC system file definition contained in the NATvrs.SYSF file by using the Adabas ADALOD utility.

    The following ADALOD utility parameter must not be changed:

    ISNREUSE=YES

Step 7: Load the FSEC System File Definition

(Job I050, Step 9900)

Skip this step, if you do not use Natural Security.

Step 8: Assemble the Natural BS2000 Stub Module and Batch Driver

(Job I055, Steps 0216 - 0218)

  • Assemble the following source modules:

    ANATSTUB Natural BS2000 stub module
    ANATFRNT Natural BS2000 non-reentrant part of the Natural batch interface
    ANATRENT Natural BS2000 reentrant part of the Natural batch interface

    These source modules are contained in the library job-library.

Step 9: Build the Natural Parameter Module

(Job I060, Step 0010)

Build the Natural parameter module for batch mode.

  1. Modify the settings of the Natural profile parameters supplied with this job, if required. The parameters and corresponding macros (if applicable) are described in the Parameter Reference documentation. The most important parameter/macro settings are described below.

    • Adapt the following parameters:

      FNAT=(database-id,file-number)
      FUSER=(database-id,file-number)
      FDIC=(database-id,file-number)

      where database-id and file-number are either the database ID and file number you specified when loading the new FNAT, FUSER and FSEC system files (see Step 2, Step 3 and Step 6, respectively), or the database ID and file number of your existing Natural system files.

      These parameters are supplied with the NTPRM macro described in the Operations documentation.

    • If you want to to limit the number of concurrent users with the Natural profile parameter UCONMAX, proceed as follows:

      Supply the following parameter with the NTPRM macro:

      FREG=(database-id,file-number)

      where database-id and file-number are either the database ID and file number you specified when loading the new Natural FREG system file (see Step 5), or the database ID and file number of your existing Natural FREG system file.

    • If you want to use read-only system files, proceed as follows:

      Supply the following parameter with the NTPRM macro:

      ROSY=ON

      Specify the NTLFILE macro (see the parameter LFILE):

      NTLFILE 212,database-id,file-number

      where database-id and file-number are the database ID and file number you specified when loading the new Natural scratch-pad file (see Step 4), or the database ID and file number of your existing Natural scratch-pad file.

  2. Assemble the Natural parameter module.

Step 10: Link and Start the Optimize Monitor Buffer Pool

(Job I060, Step 1230)

This step is only required if you want to use the Optimize Monitor Buffer Pool described in Optimize Monitor Buffer Pool in the Operations documentation.

  1. Link the NATO4182 program for the Optimize Monitor Buffer Pool.

  2. Create and start the job E.START.O4IBP (supplied with Step 1230) before using Natural. See Starting the Optimize Monitor Buffer Pool in the Operations documentation.

Step 11: Link the Nucleus

(Job I060, Steps 3801, 3802)

  1. Link the environment-dependent nucleus LNATFRNT (Step 3801) for batch Natural.

    The list of modules to be linked for the environment-dependent nucleus is supplied with Step 3801.

    Note:

    • If the parameter ILCS=CRTE is specified for the assembly of the reentrant part of the BS2000 batch driver, the BINDER statements for the masking of symbols have to be specified as follows:

      INCLUDE-MODULES ELEMENT=(IT0SL#),LIB=$TSOS.SYSLNK.CRTE
      RESOLVE-BY-AUTOLINK LIB=($TSOS.SYSLNK.CRTE)
      MODIFY-SYMBOL-VISIBILITY                      -
                SYMBOL-NAME = *ALL,                 -
                SYMBOL-TYPE = *DEFINITIONS,         -
                VISIBLE = *YES                  
      MODIFY-SYMBOL-VISIBILITY                      -
                SYMBOL-NAME = CMPRMTB,              -
                SYMBOL-TYPE = *DEFINITIONS,         -
                VISIBLE = *NO(KEEP-RES=*YES)

      VISIBLE = *YES: Necessary to prevent duplicate loading of the CRTE routines.

      VISIBLE = *NO(KEEP-RES=*YES): The entry CMPRMTB in the Natural parameter module has to be masked if the Natural parameter module is bound to the environment-dependent nucleus.

  2. Link the environment-independent nucleus LNATSHAR (Step 3802).

    The list of modules to be linked for the environment-independent nucleus is supplied with Step 3802.

    Ensure that the Natural profile parameter NUCNAME (see the Parameter Reference documentation) specified in the Natural parameter module contains the name of the module resulting from this link step.

Using a Sort Program

If you want to use a sort program (either Natural's internal one or an external one), include the module NAT2SORT.

It is also possible to place NAT2SORT in a load library from where it can be loaded dynamically at runtime; this requires that NAT2SORT is specified with the Natural profile parameter RCA (described in the Parameter Reference documentation).

Step 12: Start All Pools

(Job I061, Step 0001)

  • Start the job E.START.ALL which is contained in the library job-library.

    To end all pools, start the job E.END.ALL which is contained in the library job-library.

Step 13: Load New Natural Objects and Natural Error Messages

(Job I061, Step 0100)

  • Load the Natural objects and Natural error messages from the NATvrs.INPL file into the Natural system files by using the Natural INPL utility.

    The Natural error messages comprise short and long message texts and the German (ULANG=2) short message texts. You can use the ERRUPPER program of the Natural SYSERR utility to convert the message texts to upper case.

    For details on the ULANG profile parameter and ERRUPPER, see the Parameter Reference and the Utilities documentation, respectively.

Step 14: Load the Natural Example Objects

(Job I061, Step 0103)

  • Load the Natural example objects from the NATvrs.EXPL file into the Natural system file by using the Natural INPL utility.

Step 15: Allocate and Format the Editor Work File

(Job I081, Step 1900)

  1. Allocate the editor work file (see also Editor Work File in the Operations documentation) by issuing the command:

    /FILE file-name,LINK=CMEDIT,SPACE=...
  2. Execute the formatting program (NATEDFM2, NATvrs.MOD) by entering FORMAT to format and load the control record in the editor work file.

Installation Verification

This section provides instructions for verifying the successful installation of Natural.

Test Batch Natural

You can use the following procedure to invoke Natural in batch mode and check whether the Natural system files are available:

/   SET-PROCEDURE-OPTIONS         DATA-ESCAPE-CHAR = *STD
/        ADD-FILE-LINK  DDLIB,    ADALNK.LIB
/        ADD-FILE-LINK  DDLNKPAR, ADALNK.PARMS
/        ADD-FILE-LINK  CMEDIT,   EDTWORK
/   START-PROGRAM  NATBATCH
EDIT
WRITE 'TESTBAT'
END
.END
SAVE TESTBAT
RUN
FIN
/   EXIT-PROCEDURE

This procedure starts Natural (using the Adabas link routine ADALNK), creates the example program TESTBAT, and executes the program with the system command RUN.

Start Natural

Start a Natural session according to the procedure that applies to your TP monitor interface; see also Installation Verification described for the Natural TIAM Interface and the Natural openUTM Interface.

Test Online Natural

You can use the following verification procedure to test Natural system functions in online mode and check whether the Natural system files are available.

  1. Log on to the Natural user library SYSTEM:

    LOGON SYSTEM
  2. Enter the following Natural system command:

    MAINMENU
  3. Select Development Functions and enter the following:

    C in the Code field,
    P in the Type field, and
    TEST in the Name field.

  4. In the editing area of the program editor, type the following:

    WRITE 'HELLO'
    END
  5. Save the source code and exit the program editor.

  6. In the Development Functions menu, enter the following:

    L in the Code field and
    TES* in the Name field.

  7. On the LIST Objects in a Library screen, enter the RU line command for the TEST program.

  8. Enter the following Natural system command:

    SYSDDM
  9. In the SYSDDM utility menu, enter the following:

    R in the Code field and
    EMPLOYEES in the DDM Name field.

  10. After pressing ENTER, enter the following:

    C in the Code field,
    the appropriate Natural system file number in the FNR field,
    the appropriate database ID in the DBID field, and
    Y in the Replace field.

    The specified DDM has been adapted to your environment.

  11. Repeat Steps 9 and 10 for the VEHICLES DDM.

  12. You can check whether the DDMs EMPLOYEES and VEHICLES are now available in your environment by logging on to the Natural system library SYSEXSYN and executing the example programs (for example, AEDEX1R) with the system command RUN.