Version 4.2.6
 —  Installation  —

Installing Natural under VM/CMS

This document describes how to install Natural under VM/CMS.

The following topics are covered:

For information on how to run Natural in a CMS environment, refer to Natural under CMS 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

The following products must be installed:

Top of page

Preparing the VM System for Natural CMS

Natural is completely reentrant under CMS. It is recommended that Natural under CMS be installed as a Discontiguous Shared Segment (DCSS) to avoid unnecessary paging activity by VM.

For better performance, Natural uses a buffer pool in which Natural object programs are stored and executed. If you execute a Natural program, it is fetched from the database and stored in the buffer pool. If you subsequently invoke the same program, it will be executed directly in the buffer pool. Thus, repeated fetching from the database and accompanying IUCV overhead is avoided.

In a shared buffer pool, one Natural under CMS user can execute Natural programs that have been placed in the buffer pool by another Natural under CMS user. A shared buffer pool is implemented by installing the buffer pool in a writeable saved segment.

You are recommended to install two DCSSs: one for the Natural nucleus and one for the buffer pool. Of course, several buffer pools at different virtual addresses can be defined and several Natural nucleus DCSSs with different functionalities, for example, different static parameter settings (NATPARM) or different Assembler options of the CMS driver (NATCMS).

The buffer pool shared segment is defined as SN (see the corresponding step of the installation procedure) and the first Natural session automatically initializes the buffer pool. When the last Natural user in VM exits Natural, the use count of the shared segment becomes 0, the buffer pool is purged from CP storage, and the next Natural session has to initialize the buffer pool again.

To avoid repeated initialization, the use count can be artificially held at 1 by including the following statement line in the PROFILE EXEC of a disconnected service machine, segment being the name of the Natural buffer pool shared segment:

SEGMENT LOAD segment

In this way, the Natural buffer pool is initialized only once and immediately available to a Natural session as long as the disconnected server is running.

Top of page

Preparing the Adabas System for Natural

The Natural system programs are stored in the Natural system file FNAT. User-written Natural programs are stored in the Natural system file FUSER. These system files reside in Adabas files. The corresponding step of the installation procedure (see below) describes how these Adabas files can be built in an Adabas system running under CMS.

Top of page

Building the Natural CMS System

Building the Natural CMS system comprises the following steps:

The Natural nucleus should be built

The Natural system file is loaded directly from tape using the installation EXEC, NATINPL; see the corresponding step of the installation procedure.

The CMS driver NATCMS is included in the Natural module and in the saved segment. NATCMS ASSEMBLE consists of one macro that generates the driver.

Description of the Macro Parameters

For a detailed description of the macro parameters, refer to the corresponding step of the installation procedure. The driver NATCMS and the parameter module NATPARM are assembled during the installation process. Optionally, the modules NATTEXT, NATTXT2, NATTXT3, NATCONFG and NATPM can be modified and reassembled.

The list of text files to be included in the Natural module or DCSS is contained in REXX program NAT$LOAD EXEC (variable LOADLIST). To customize your Natural system, modify this EXEC with XEDIT by changing the LOADLIST as required.

User ID for Performing the Installation

The user ID used for performing the installation should have a minidisk of 80 cylinders on 3390-type disks or an SFS directory of 14000 blocks. CP privilege class E is needed to issue the command CP SAVESYS. The size of the virtual machine allowed for the user ID must be adequate to accommodate the highest address of the saved segments that you plan to generate.

Top of page

Installation Tape for Natural under CMS

The installation tape was created under z/OS; it has standard z/OS labels and headers. It contains the datasets listed in the table below. The sequence of the datasets is 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.TAPE CMS installation material. This dataset is in TAPE DUMP format and must be loaded onto the installation minidisk.
NATvrs.ERRN Natural error messages.
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 VM/CMS Disk

  1. On the Natural installation tape, a license key file is provided.

    If the sequence number of NATvrs.LICS, as shown by the Report of Tape Creation, is n, you must position over 3 n - 2 tape marks (that is, FSF 1 for the first dataset, FSF 4 for the second, etc.).

    FILEDEF IN TAP1 (RECFM FB LRECL 80 BLKSIZE 3120
    FILEDEF OUT DISK NATLIC DATA A (RECFM F LRECL 80 BLKSIZE 80
    MOVEFILE IN OUT
    
  2. To position the tape for the TAPE LOAD command, calculate the number of tape marks as follows:

    If the sequence number of NATvrs.TAPE, as shown by the Report of Tape Creation, is n, you must position over 3 n - 2 tape marks (that is, FSF 1 for the first dataset, FSF 4 for the second, etc.).

  3. Access the disk that is to contain the Natural installation files as disk A.

    The size of the disk must be at least 14000 4-KB blocks, for example, 80 cylinders on 3390-type disks.

  4. Ask the system operator to attach a tape drive to your virtual machine at address X'181' and mount the Natural installation tape.

  5. Position the tape by issuing the CMS command:

    TAPE FSF fsfs

    where fsfs is the number of tape marks and is calculated as described above.

  6. Load the Natural under CMS installation material by issuing the CMS command:

    TAPE LOAD * * A
  7. Keep the tape drive attached to your virtual machine, because the tape is still needed during the installation procedure.

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/VM host:

    ftp host-name

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

  4. Enter your z/VM host login ID and password; for example: <cmsmachine.by.user>

  5. Once the FTP session has been established, specify the CMS file system (SFS) or access a minidisk for the license key file:

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

    ftp>binary
  7. Specify that the dataset for the license key file must be written with RECFM FIX 80.

    ftp>quote site fix 80
  8. Write the license as a dataset on the z/VM system. For example, if the license key file name is natvrs.xml, you might enter:

    ftp>put natvr.xml

    This command will create a dataset called NATvr.LICS.

  9. Rename or copy the dataset as follows:

    NATLIC DATA A

    The license key information stored in the dataset will be in ASCII format.

  10. Stop your FTP session by entering:

    ftp>quit

Top of page

Installation Procedure for Natural under CMS

Step 1: Define the Natural Discontiguous Saved Segments to VM

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: Generate a TEXT file from the Software AG license key file

Step 8: Customize the Natural Parameter Module

Step 9: Customize the INCLUDE List for Linking of Natural

Step 10: Linking the Adabas Interface

Step 11: Generate a Natural Module

Step 12: Generate a Natural DCSS

Step 13: Delete Natural System Objects

Step 14: Load the Natural System File and Error Messages

Step 15: Make Natural Modules Available to the Users

Top of page

Installation Verification for Natural under CMS

To verify your installation, perform the following steps:

  1. Issue as CMS command the name of the Natural module created in a previous step.

  2. Check that the following results are available:

Top of page