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:
For details, refer to the section Prerequisites.
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.
||Contains the object modules of the development server. See Natural Development Server on Mainframes.|
||Contains 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.|
||Contains the transaction processor.|
||Contains the error messages of the transaction processor.|
||Contains the FDT of the Development Server File (the layout is
||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/.
(Job I008, Step 8410)
(Job I009, Step 8410, 8420, 8430)
Step 8410 creates a sample
NDVCONFG for the batch
Step 8420 creates a sample
TERMINATE a Natural Development Server.
Step 8430 creates a sample batch job to
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:
||Specify the name of the Natural Development Server front-end module you generate in Step 6.|
||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.
(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
The layout of the Development Server
FDIC) corresponds to the layout of the Predict
Version 4.3 or above dictionary file.
If you have a Predict version installed as specified under Natural and Other Software AG Products in the current Natural Release Notes for Mainframes, you can ignore this step.
(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
(Job I060, Steps 8410, 8420, 8430)
Job I060, Step 8410, start the batch program
Job I060, Step 8420, assemble and link the parameter module
Job I060, Step 8430, link the NDV server front-end module.
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
SYS1.CSSLIB in order to enable the use of
(Job I061, Steps 8450,8451,8452)
During the loading of the NDV related modules with the Natural utility
INPL, the assigned
FSEC file is
initialized with NDV-specific information.
Load objects from dataset
NDVvrs.INPL onto your Natural system
FNAT), using the Natural utility
FDIC must have been set to point to your
development server file.
Load the error messages from dataset
To use the tutorial (see First Steps with Natural Single
Point of Development), load the sample programs from dataset
NDVvrs.EXPL to your Natural system file
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
FDIC as Development Server File (
you have to copy the existing DDMs and processing rules to the Development
Server File (
FDIC), using the copy function of the Natural utility
(Job I200, Step 8415)
Described in the section Configuring the Natural Development
Server. See sample member
NDVSTART on dataset
// 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
The NDV server account must be defined in the z/OS UNIX System Services (OE segment). If the server account is not defined, the server ends with
U4093 and system message
CEE5101C in the trace
(Job I200, Step 8418)
//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),INTENS=1 //* //DDCARD DD * ADARUN DB=001,DE=3390,SVC=249 //* //SYSPRINT DD SYSOUT=* //CMPRINT DD SYSOUT=* //CMSYNIN DD * MYLIB,DBA,DBA MYPROG FIN /*
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
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.
If you configure the NDV server to use an external security system (see
NDV configuration parameter
NDV clients must be defined to the external security system.