Version 4.2.6
 —  Installation  —

Installing Natural under BS2000/OSD

This document describes step by step how to install Natural under the operating system BS2000/OSD using Adabas system files.

The following topics are covered:

For installation-related information on Unicode and code page support, refer to Configuration and Administration of the Unicode/Code Page Environment in the Unicode and Code Page Support documentation.

Notation vrs or vr: If used in the following document, the notation vrs or vr stands for the relevant version, release, system maintenance level numbers. For further information on product versions, see Version in the Glossary.


Prerequisites

Top of page

Installation Tape for Natural under BS2000/OSD

The installation tape contains the datasets listed in the table below. The sequence of the datasets, the dataset type, the number of library blocks needed and the space each dataset requires on disk are shown in the Report of Tape Creation which accompanies the installation tape.

Dataset Name Contents
NATvrs.LICS Natural License Key File. For further information on license key file, license key file installation, product license check and product license check FAQs, see Licensing Natural.

If a license key file is supplied as an e-mail attachment, see Transferring the License Key File from PC to Host with FTP.

NATvrs.SYSF Empty Natural system file
NATvrs.ERRN Natural error messages
NATvrs.MOD Natural module library
NATvrs.SRC Natural source modules
NATvrs.MAC Natural macros
NATvrs.JOBS Example installation jobs
NATvrs.LDEL Instructions to delete Natural system objects of Version 4.1
NATvrs.INPL Natural system objects
NATvrs.EXPL Natural example objects

Note:
The dataset NATvrs.JOBS will be converted automatically into an LMS-library when it is copied from tape to disk.

Copying the Tape Contents to a BS2000/OSD Disk

If you are not using System Maintenance Aid (SMA), use the procedure described below. In this procedure, the values specified below must be supplied.

To copy the datasets from tape to disk, perform the following steps:

1. Copy the 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 Report of Tape Creation. To convert this sequential file into an LMS-library, execute the following commands:

/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
volser is the VOLSER of the tape (see Report of Tape Creation)

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

To copy the procedure COPY.PROC to disk, call the procedure P.COPYTAPE in the library SRVvrs.LIB:

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

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

3. Copy all Product Files from Tape to Disk

To copy all Software AG product files from tape to disk, enter the procedure COPY.PROC:

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

If you use a TAPE-C4 device, you may omit the parameter DEVT. The result of this procedure is written to the file L.REPORT.SRV.

Top of page

Transferring a License Key File from PC to Host with FTP

If a license key file is supplied as an e-mail attachment, you must transfer the attached license key file natvr.xml from the PC to the mainframe, using native FTP commands.

Warning:
Using utilities instead of native FTP commands for the license key file transfer may corrupt the license key and thus prevent Natural from execution later on. This applies for example to file transfer based on 3270 terminal emulations that do not provide a true binary file transfer, but convert specific characters.

To transfer a license key file from the PC to the mainframe, perform the following steps:

  1. Save the product license key file e-mail attachment on your PC hard disk.

  2. Open a command prompt window. In the command prompt window, change to the directory where you saved the product license key file.

  3. Start an FTP session for communication with the BS2000/OSD host:

    ftp host-name

    Where host-name is the name of the BS2000/OSD host.

  4. Enter your BS2000/OSD host login User and Password.

  5. Enter your BS2000/OSD host Account.

  6. Specify that the file for the license key file must be written with FCBTYPE=SAM and RECFORM=V.

    ftp>Literal file NATvrs.LICS,FCBTYPE=SAM,RECFORM=V
  7. Switch to binary data mode (the license key file must retain its ASCII format during the transfer):

    ftp>bin
  8. Write the license as a file on the mainframe system.

    ftp>put natvr.xml NATvrs.LICS

    This command will create a file called NATvrs.LICS.

    The file set will have RECFORM=V, and the license key information stored in the file set will be in ASCII format.

  9. Stop your FTP session by entering:

    ftp>quit

Top of page

Installation Procedure for Natural under BS2000/OSD

Naming Conventions

In the following text, the library name JOBLIB stands for

Note:
Software AG uses the following naming conventions for source elements in the library JOBLIB:

A<product-code><function> = Assembler sources
L<product-code><function> = Instruction for TSOSLNK/BINDER

Example: ANATFRNT, ANATRENT, ANATSTUB or LNATFRNT

Step 1: Convert the License Key File

  1. Convert Dataset NATvrs.LICS with PROGRAM NATLICAB in an Assembler input file.

    (Job I010, Step 0100)

    Convert license key file (NATvrs.LICS).

  2. Assemble license key module. This module is linked (Job I060) to the Natural nucleus.

    (Job I010, Step 0101)

    ANATLIC (Natural BS2000/OSD module NATLIC)

Step 2: Load the FNAT System File

Step 3: Load the FUSER System File

Step 4: Load the Scratch-Pad File

Step 5: Load the FDIC System File

Step 6: Load the FSEC System File

Step 7: Assemble the Natural BS2000/OSD Stub Module and Batch Driver

Step 8: Create the Parameter Module

Step 9: Link the Natural Nucleus

Step 10: Start All Pools

Step 11: Delete Natural System Objects

Step 12: Load the System Programs

Step 13: Load the Error Messages

Step 14: Load the Examples

Step 15: Allocate and Format the Editor Work File

Top of page

Installation Verification for Natural under BS2000/OSD

For base Natural, there are no specific installation verification procedures. After the last step of the installation procedure has been successfully performed, check that the following results are available:

Top of page