This document describes how to install a Natural Development Server (product code NDV) on the operating system z/OS (Batch).

The following topics are covered:

• Prerequisites

• Content of the Development Server Distribution Medium

• Installation Procedure

---

Prerequisites

For details, refer to the section Prerequisites.

Content of the Development Server Distribution Medium

The installation medium contains the datasets listed in the table below. The sequence of the datasets and the number of library blocks needed are shown in the Software AG Product Delivery Report, which accompanies the installation medium.

Dataset Name	Contents
NDVvrs.OBJS	Contains the object modules of the development server. See Natural Development Server on Mainframes.
NDVvrs.INPL	Contains the transaction processor, the error messages of the transaction processor, and the sample programs required for using the tutorial. See First Steps with Natural Single Point of Development in the Natural Single Point of Development documentation.
NDVvrs.SYSF	Contains the FDT of the Development Server File (the layout is identical with PRDvrs.SYSF provided with a Predict version as specified under Natural and Other Software AG Products in the current Natural Release Notes).
NDVvrs.JOBS	Example installation jobs.

The notation vrs in dataset names represents the version, release and system maintenance level of the product.

For the currently applicable versions refer to Empower at https://empower.softwareag.com/.

Installation Procedure

Step 1: Allocate the development server LOAD library

(Job I008, Step 8410)

Step 2: Create a development server configuration file and sample Clist

(Job I009, Step 8410, 8420, 8430)

Step 8410 creates a sample NDVCONFG for the batch server.

Step 8420 creates a sample CLIST to PING and TERMINATE a Natural Development Server.

Step 8430 creates a sample batch job to PING and TERMINATE a Natural Development Server.

The following parameters of the configuration file have to be defined. For the other parameters, the default values may be used:

FRONTEND_NAME	Specify the name of the Natural Development Server front-end module you generate in Step 6.
PORT_NUMBER	Specify the TCP/IP port number under which the server can be connected.

For a description of the parameters, refer to Configuring the Natural Development Server.

Step 3: Load FDIC system file (optional)

(Job I050, Step 8403)

If you do not use Predict at all or if you have not yet migrated to a Predict version as specified under Natural and Other Software AG Products in the current Natural Release Notes for Mainframes, create the development server file, using the dataset NDVvrs.SYSF.

The layout of the Development Server File (FDIC) corresponds to the layout of the Predict Version 4.3 or above dictionary file.

Step 4: Link the object modules into the NDV load library

(Job I054, Step 8410)

The NDV object modules must be linked with the necessary runtime extensions of your batch installations into executable load modules.

See sample job NDVI054 on dataset NDVvrs.JOBS.

Step 5: Create the NDV server front-end module

(Job I060, Steps 8410, 8420, 8430)

• Job I060, Step 8410, start the batch program IEBUPDATE and store NDVPARM.

• Job I060, Step 8420, assemble and link the parameter module NDVPARM.

• Job I060, Step 8430, link the NDV server front-end module.

  Note:
  If you have Natural subproducts for IBM database access installed, for example, Natural for DB2, Natural for DL/I, Natural for VSAM, you need to adjust the link job to include ATRRCSS from SYS1.CSSLIB in order to enable the use of SYNCPOINT/ROLLBACK functionalities.

Step 6: Load Natural objects, error messages and samples for NDV

(Job I061, Steps 8450)

During the loading of the NDV related modules with the Natural utility INPL, the assigned FDIC/FSEC file is initialized with NDV-specific information.

• Load objects from dataset NDVvrs.INPL onto your Natural system file (FNAT), using the Natural utility INPL. The parameter FDIC must have been set to point to your development server file.

• The error messages are loaded.

• The sample programs to use the tutorial (see First Steps with Natural Single Point of Development), are loaded to your Natural system file (FNAT).

Step 7: Copy DDMs and processing rules to FDIC (optional)

If you use a Predict system file FDIC as Development Server File (FDIC), ignore this step.

If a Predict version as specified under Natural and Other Software AG Products in the current Natural Release Notes for Mainframe has not been installed or if you do not use a Predict system file FDIC as Development Server File (FDIC), you have to copy the existing DDMs and processing rules to the Development Server File (FDIC), using the copy function of the Natural utility SYSMAIN.

Step 8: Create server startup JCL

(Job I200, Step 8415)

Described in the section Configuring the Natural Development Server. See sample member NDVSTART on dataset NDVvrs.JOBS.

Sample:

//         PROC SRV=SAGNDV
//NDV      EXEC PGM=NATRDEVS, 
// REGION=4000K,TIME=1440,PARM='POSIX(ON),TRAP(ON,NOSPIE)/&SRV' 
//STEPLIB  DD   DISP=SHR,DSN=NDVvrs.LOAD
//         DD   DISP=SHR,DSN=SAGLIB.SMALOAD 
//SYSUDUMP DD   SYSOUT=X 
//CEEDUMP  DD   SYSOUT=X 
//CMPRINT  DD   SYSOUT=X 
//STGCONFG DD   DISP=SHR, 
//              DSN=NDV.CONFIG(&SRV) 
//STGTRACE DD   SYSOUT=X 
//STGSTDO  DD   SYSOUT=X 
//STGSTDE  DD   SYSOUT=X 
//SYSOUT   DD   SYSOUT=X

Step 9: Debug a Natural batch job with Debug Attach for NaturalONE

(Job I200, Step 8418)

Sample JCL:

//NATEX    EXEC PGM=NATvrsBA,REGION=8M
//STEPLIB  DD DSN=SAGLIB.NDVvrs.LOAD,DISP=SHR
//         DD DSN=SAGLIB.SMALOAD,DISP=SHR
//         DD DSN=SAGLIB.ADAvrs.LOAD,DISP=SHR
//         DD DSN=CEE.SCEERUN,DISP=SHR
//*
//CMPRMIN  DD *
DBGAT=(ACTIVE=ON,CLID=CLIENT,HOST=DASSERV,PORT=2500)
RCA=(NATATDBG) RCALIAS=(NATATDBG,NATADvrs)
//*
//DDCARD   DD *
 ADARUN DB=001,DE=3390,SVC=249
//*
//SYSPRINT DD SYSOUT=*
//CMPRINT  DD SYSOUT=*
//CMSYNIN  DD *
MYLIB,DBA,DBA
MYPROG
FIN
/*

Step 10: NDV Clients must be defined to Natural Security

If Natural Security (NSC) is installed:

• The NDV initial user ID (default ID is STARGATE) must be defined in Natural Security with a valid default library. Refer also to NDV configuration parameter INITIAL_USERID. Alternatively, you can define the Natural profile parameter AUTO=OFF (automatic logon) for NDV.

• Each client user ID must be defined in Natural Security.

If the NDV initial user ID is not defined, the NDV server initialization aborts with a NAT0856 error message.

If an NDV client is not defined, the map environment returns an NSC error.

If you logon to the server from an NDV client, make sure that the user who is defined in Natural Security has a default library or a private library defined. Otherwise, error message NAT0815 will occur.

Step 11: NDV Clients must be defined to the server host

If you configure the NDV server to use an external security system (see NDV configuration parameter SECURITY_MODE), the NDV clients must be defined to the external security system.