Version 4.2.6
 —  Installation  —

Installing Natural under z/OS

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

The following topics are covered:

See also z/OS Environment in the Natural Operations documentation.

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 z/OS

The installation tape contains the datasets listed in the table below. The sequence of the datasets and the number of library blocks needed 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.LOAD Natural load modules
NATvrs.OBJS Natural object modules
NATvrs.SRCE Natural source modules and 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

Copying the Tape Contents to a z/OS Disk

If you are using SMA, refer to the System Maintenance Aid documentation (included in the current edition of the Natural documentation CD).

If you are not using SMA, follow the instructions below.

This section explains how to:

The JCL in this dataset is then used to copy all datasets from tape to disk.

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

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

Step 1 - Copy Dataset COPY.JOB from Tape to Disk

The dataset COPY.JOB (Label 2) contains the JCL to unload all other existing datasets 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=tape-volume),
// LABEL=(2,SL)
//SYSUT2 DD DSN=hilev.COPY.JOB,
// DISP=(NEW,CATLG,DELETE),
// UNIT=3390,VOL=SER=volume,
// SPACE=(TRK,(1,1),RLSE),
// DCB=*.SYSUT1
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
// 

where:

hilev is a valid high level qualifier
tape-volume is the tape volume name, for example: T12345
volume is the disk volume name

Step 2 - Modify COPY.JOB on Your Disk

Modify the COPY.JOB on your disk to conform to your local naming conventions and set the disk space parameters before submitting this job:

Step 3 - Submit COPY.JOB

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

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 z/OS host:

    ftp host-name

    Where host-name is the name of the z/OS host.

  4. Enter your z/OS host login ID and password.

  5. Once the FTP session has been established, specify the z/OS file system and dataset prefix for the license key file:

    ftp>cd 'hilev'

    Switch to binary data mode (the license key file must retain its ASCII format during the transfer):

    ftp>binary
  6. Specify that the dataset for the license key file must be written with RECFM=FB and LRECL=80.

    ftp>quote site RECFM=FB LRECL=80 BLKSIZE=4000

    Note:
    RECFM=F is also supported for product license key files.

  7. Copy the license key file as a dataset on the z/OS system.

    ftp>put natvr.xml NATvrs.LICS

    This command will create a dataset called hilev.NATvrs.LICS.

    If you requested a prefix of NATURAL, the dataset name would be: NATURAL.NATvrs.LICS.

    The dataset will have RECFM=FB, LRECL=80, and the license key information stored in the dataset will be in ASCII format.

  8. Stop your FTP session by entering:

    ftp>quit

Top of page

Installation Procedure for Natural under z/OS

Step 1: Convert and Assemble the License Key File

Using PROGRAM NATLICAM, convert dataset hilev.NATvrs.LICS into an Assembler input file.

Assemble/link into a linkable module. This module is linked (Job I060) to the Natural nucleus.

Step 2: Copy Natural Modules to an APF Library

Step 3: Create and Start the Global Buffer Pool

Step 4: Load the FNAT System File

Step 5: Load the FUSER System File

Step 6: Load the Scratch-Pad File

Step 7: Load the FDIC System File

Step 8: Load the FSEC System File

Step 9: Assemble the Natural z/OS Interface Module

Step 10: Create the Natural Configuration Module

Step 11: Create the Parameter Module

Step 12: Link the Natural Nucleus

When linking the Natural nucleus, you have the following alternatives:

Link a batch front-end (Job I060, Step 0020) and link a shared nucleus (Job I060, Step 0105), or link a non-shared nucleus (Job I060, Step 0020).

Step 13: Delete Natural System Objects

Step 14: Load the System Programs

Step 15: Load the Error Messages

Step 16: Load the Examples

Step 17: Create and Format the Roll File

Step 18: Create and Start the Roll Server

Step 19: Create and Start the Authorized Services Manager

Step 20: Create Sample JCL for Natural RPC Server

Top of page

Installation Verification for Natural under z/OS

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