Installing Natural Com-plete/SMARTS Interface on z/OS

This document describes the steps for installing Natural Com-plete/SMARTS Interface which corresponds to the Natural Com-plete Interface (product code NCF) on z/OS.

Related Topics:

For information on how to operate Natural in a Com-plete/SMARTS environment, see the following topics:

For information on installing and using Com-plete, see the Com-plete 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

A supported version of the following product must be installed before you can install the Natural Com-plete/SMARTS Interface:

  • Com-plete

    See the Com-plete Installation documentation.

See also General Prerequisites and System Support in the section Overview of the Installation Process.

Installation Medium

The installation medium contains the following data sets required for product installation:

Data Set Name Contents
NCFvrs.LOAD Load modules
NCFvrs.SRCE Source modules and macros
NCFvrs.LICS Product license file for Natural for Com-plete for zIIP

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

Copy the data sets into your environment as described in Copying Data Sets to a z/OS Disk in the section Installing Natural.

Sample Jobs

Sample installation jobs are contained in the NATvrs.JOBS data set and are prefixed with the product code. The data set is provided on the installation medium supplied for base Natural.

Installation Procedure

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

Step 1: Prepare, Convert, Assemble and Link the License File for Natural for Com-plete for zIIP

(Job I007, Steps 2301, 2302, 2304)

This step is optional and only required if you want to install Natural for Com-plete for zIIP.

You must install a valid Natural license file. An additional license file is required if you want to install Natural for Com-plete for zIIP to enable support of the IBM z/IIP (IBM System z Integrated Information Processor).

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 z/OS Host Using FTP in Software AG Mainframe Product Licensing.

  2. Check, convert, assemble and link the license file supplied for Natural for Com-plete for zIIP:

    Step 2301 Check license file NCFvrs.LICS. This job runs the CHECK function of the LICUTIL license utility (see below).
    Step 2302 Convert license file into an assembler source. This job runs the MAKE function of the LICUTIL license utility (see below).
    Step 2304 Assemble and link the assembler source to generate load module NCFLIC. This module is then linked to the nucleus in Job I080.

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

Step 2: Create the Startup Program

(Job I070, Steps 2320, 2321)

This step is optional.

You can use a Natural Com-plete/SMARTS Interface startup program to pass dynamic parameters to Natural.

  1. Adapt the example program NCO001 contained in the source library to your requirements.

  2. Assemble and link the startup program into your Com-plete user program library.

Step 3: Build the Natural Parameter Module

(Job I080, Steps 2300, 2310)

The Natural profile parameters and parameter macros mentioned in this section are described in the Parameter Reference documentation unless otherwise noted.

  1. Modify the Natural parameter module for Com-plete/SMARTS:

    • Configure the Com-plete/SMARTS batch interface: Modify the settings of the parameters supplied with the macro NTCOMP to meet your requirements. For descriptions of these parameters, see the corresponding profile parameter COMP.

    • Modify the following parameters:

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

      where database-id and file-number are the values you specified when loading the system files during the Installation Procedure for base Natural.

  2. Define a Natural local buffer pool under Com-plete by modifying the values of the keyword parameters supplied with the parameter macro NTBPI (see the Natural profile parameter BPI) as required.

    A local buffer pool is allocated during initialization of the first Natural session after Com-plete startup.

    The status of the local buffer pools can be displayed on the operator console by issuing the following Com-plete operator command: 

    SERV,server-name,BPSTAT

    where server-name is the name of the server as specified with the Com-plete SERVER startup option.

  3. If you want to use a Natural global buffer pool under Com-plete, specify the same values as in the Natural installation procedure for the profile parameter SUBSID in the parameter macro NTPRM (see the Operations documentation) for the keyword subparameter NAME in the parameter macro NTBPI (see the Parameter Reference documentation).

  4. Assemble and link the Natural parameter module.

Step 4: Link the Nucleus

(Job I080, Step 2320)

Link the environment-dependent nucleus for the Natural Com-plete/SMARTS Interface.

  • Link the environment-dependent nucleus into your Com-plete user program library.

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

    If you want Natural to run in the IBM Language Environment (LE), set the System Maintenance Aid (SMA) NAT-LE to Y (Yes). The default setting is N (No).

  • Specify the environment-dependent nucleus as a Com-plete startup option by setting the following Com-plete keyword parameter: 

    RESIDENTPAGE=name

    where name is the name of the environment-dependent nucleus for the Natural Com-plete/SMARTS Interface.

Step 5: Link the Natural Com-plete/SMARTS Interface Server

(Job I080, Step 2350)

  • Link the Natural Com-plete/SMARTS Interface server.

The Natural Com-plete/SMARTS Interface server is used to maintain common storage and tables across Natural sessions, for example, the local buffer pool.

Step 6: Define the Natural Com-plete/SMARTS Interface Server

  • Specify the Natural Com-plete/SMARTS Interface server as a Com-plete startup option by setting the following Com-plete keyword parameter: 

    SERVER=(server-name,module-name)

    where:

    server-name is the name of the server as specified with the keyword subparameter SERVER in the parameter macro NTCOMP (see the Parameter Reference documentation).

    module-name is the name of the load module linked in Step 4: Link the Natural Com-plete/SMARTS Interface Server.

The Natural Com-plete/SMARTS Interface server module is loaded during Com-plete initialization. The module must therefore be placed in a load library contained in the COMPINIT load library concatenation (see also the Com-plete Installation documentation).

Step 7: Catalog the Natural Com-plete/SMARTS Interface

This step is required if either of the following is true:

  You run Natural under Com-plete/SMARTS and use threads below the line (THABOVE=NO setting in the NTCOMP macro).
  Or:
  You want to use Natural work pools below the 16-MB line.

  • Catalog the Natural Com-plete/SMARTS Interface by using the Com-plete ULIB utility.

    • For threads below the line:

      The region size to be specified with the ULIB utility parameter RG depends on the setting of the keyword subparameter NTHSIZE in the parameter macro NTCOMP described in the Parameter Reference documentation.

    • For work pools below the 16-MB line:

      The region size to be specified with the ULIB utility parameter RG depends on the setting of the Natural profile parameter WPSIZE (see the Parameter Reference documentation) for the parameter macro NTPRM (see the Operations documentation).

    See also Storage Usage in the section Natural under Com-plete/SMARTS in the TP Monitor Interfaces documentation.

    After installation, you can use the Natural SYSTP utility (see the Utilities documentation) to determine the region size actually used.

Step 8: Natural zIIP Shutdown Statistics

This step is required if you want to print Natural zIIP statistics when the Com-plete environment is shut down. For more information, see zIIP Processing Reports Available in the Natural for zIIP documentation.

NCFTRMEX writes zIIP statistics to the APSLOG which are being collected since the startup of Com-plete. The shutdown exit NCFTRMEX uses program NATZPST to access the zIIP statistics.

To activate zIIP Shutdown statistics, the modules NCFTRMEX and NATZPST must be placed in a load library contained in the Com-plete COMPLIB load library concatenation. For more information, see the Com-plete Installation documentation.

Installation Verification

You can verify the successful installation of the Natural Com-plete/SMARTS Interface by performing the following steps:

  1. Stop and restart Com-plete.

  2. Enter the Com-plete user menu and type in the name of the environment-dependent nucleus for the Natural Com-plete/SMARTS Interface.

    The Natural initial screen should appear.

  3. Proceed with the steps described in the section Test Online Natural.