Version 4.2.6
 —  Installation  —

Installing Natural under z/VSE

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

The following topics are covered:

See also z/VSE 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/VSE

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 Licence 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 Example Natural system file
NATvrs.LIBR LIBR backup file
NATvrs.LIBJ Installation jobs
NATvrs.LDEL Instructions to delete Natural system objects of Version 4.1
NATvrs.INPL Natural system objects
NATvrs.EXPL Natural example objects
NATvrs.ERRN Natural error messages

The dataset type and the space each dataset requires on disk is shown in the Report of Tape Creation.

Copying the Tape Contents to a z/VSE 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 member 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 member COPYTAPE.JOB contains the JCL to unload the datasets for all delivered products from the tape to your disk, except the datasets that you can directly install from tape, for example, Natural INPL objects.

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

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

The dataset COPYTAPE.JOB contains the JCL to unload all other existing datasets from tape to disk. To unload COPYTAPE.JOB, use the following sample JCL:

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

where:

nnn is the tape address
lib.sublib is the library and sublibrary of the catalog

Step 2 - Modify COPYTAPE.JOB

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

Step 3 - Submit COPYTAPE.JOB

Submit COPYTAPE.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/VSE host:

    ftp host-name

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

  4. Enter your z/VSE host login user and password.

  5. Once the FTP session has been established, specify the z/VSE sublibrary for the license key file:

    ftp>cd lib.sublib
  6. Switch to binary data mode (the license key file must retain its ASCII format during the transfer):

    ftp>bin
  7. Copy the license key file as a member into the specified sublibrary.

    ftp>put natvr.xml NATvrs.LICS

    This command will create a member NATvrs.LICS in the specified sublibrary.

  8. Stop your FTP session by entering:

    ftp>quit

Top of page

Installation Procedure for Natural under z/VSE

Step 1: Convert and Assemble the License Key File

Convert member NATvrs.LICS in sublibrary lib.sublib with PROGRAM NATLICAV in an Assembler input file.

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

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 z/VSE Interface Module

Step 8: Create the Natural Configuration Module

Step 9: Create the Parameter Module

Step 10: Link the Natural Nucleus

(Job I060, Step 0020)

The following alternatives exist:

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

The Natural z/VSE batch front-end requires RMODE(24) due to the use of z/VSE macros which have this restriction. Therefore the use of a shared nucleus is highly recommended, as a non-shared nucleus would also require RMODE(24).

Step 11: Link the Global Buffer Pool Modules

Step 12: Delete Natural System Objects

Step 13: Load the System Programs

Step 14: Load the Error Messages

Step 15: Load the Examples

Top of page

Installation Verification for Natural under z/VSE

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