This document describes how to install a Natural Development Server (product code NDV) in the runtime environment SMARTS on BS2000.
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 load modules and the procedures of the SMARTS server.|
||Patch-level of SMARTS (product code APS). The content
of this library must be copied into the library
||Contains the load modules of the Natural Development Server.|
||Contains the Installation Job Control for those customers who want to install without using System Maintenance Aid (SMA).|
||Contains the field definition table (FDT) of the
Development Server File (the layout is identical with
||Contains the load modules of the Natural Com-plete Interface (required for SMARTS).|
||Contains the macros of the Natural Com-plete Interface (required for SMARTS).|
vrs in a dataset name represents the version, release and system maintenance level of the product.
pp in a dataset name represents the patch level of the product.
For the currently applicable versions, refer to Empower at https://empower.softwareag.com/.
In the following text, the library name
the example job library
NDVvrs.JOBS), if you are not using
the SMA job library (see SMA parameter
JOBLIB in SMA Parameter Group
you are using SMA.
Software AG uses the following naming conventions for source
elements in the library
= Assembler sources
function> = Instruction for
||SMARTS parameters for NDV. See also SMARTS SYSPARM Parameters.|
||NDV configuration parameters. See also NDV Configuration Parameters.|
||Assembler source - Natural parameter module for NDV.|
||Link instructions to link the Natural nucleus.|
||Link instructions to link the NDV front-end module.|
||Procedure to start the NDV server.|
||Procedure to stop the NDV server.|
||Procedure to show the
To install the Natural Development Server in a SMARTS environment on BS2000, perform the following steps:
(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 by using the dataset
The layout of the Development Server
File corresponds to the layout of the Predict 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 I055, Step 8420)
Assemble the source
ANDVPARM which is contained in
(Job I060, Step 3802)
This step is optional.
The Natural nucleus module must be relinked with the modules
NAT3279 if they have not been included
yet. This is accomplished by using the source
LNATSHAR which is
contained in the library
If you are using SMA, please refer to the SMA read-me file of
(Job I060, Steps 8410)
Link the NDV front-end module by using the source
LNDVFRNT which is contained in the library
(Job I085, Step 8400)
CREATE-PFS is called to allocate and
format a PFS file.
This procedure has to be supplied with the following parameters:
||The name of the container file.|
||The size of the container file. To be specified either in K for kilobytes or M for megabytes.|
||The SMARTS library where the format utility
See also PFS Description and Allocating and Configuring a SMARTS Portable File System at the end of this document.
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 Mainframes 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
If Natural Security (NSC) is installed:
The NDV initial user ID (default ID is
must be defined in Natural Security (NSC) with a valid default library. Refer
also to NDV configuration parameter
the section Development Server
Configuration. Alternatively, you can define the Natural
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 a remote development client is not defined, the Map Environment dialog will return a Natural Security (NSC) error.
Make sure that a user who is defined in Natural Security has a default library or a private library defined. Otherwise, If he/she logs on to the server from an NDV client, an error message NAT0815 will occur.
/LOGON /SYSFILE SYSOUT=ATDEBUG.OUT /SYSFILE SYSLST=ATDEBUG.LST /FILE ADAPARM,DDLNKPAR /FILE NATvrs.MOD,LINK=BLSLIB01 /FILE NDVvrs.MOD,LINK=BLSLIB02 /FILE CMPRMIN.RMDBG,CMPRMIN /FILE ADAvrs.MOD,DDLIB /FILE DBGTRACE.NATBATCH,LINK=DBGTRACE,FCBTYPE=ISAM,SHARUPD=YES 1 /START-EXE-PROG F-F=*LI-E(L=NATvrs.MOD,EL=NATvrsBA,TYPE=L) /LOGOFF
/SET-LOGON-PARAMETERS USER-IDENTIFICATION=*NO,ACCOUNT=*NONE /ASSIGN-SYSOUT TO=ATDEBUG.OUT /ASSIGN-SYSLST TO=ATDEBUG.LST /CREATE-FILE FILE-NAME=ADAPARM,SUPPRESS-ERRORS=*FILE-EXISTING /ADD-FILE-LINK LINK-NAME=DDLNKPAR,FILE-NAME=ADAPARM,SUPPORT=*DISK /CREATE-FILE FILE-NAME=NATvrs.MOD,SUPPRESS-ERRORS=*FILE-EXISTING /ADD-FILE-LINK LINK-NAME=BLSLIB01,FILE-NAME=NATvrs.MOD,SUPPORT=*DISK /CREATE-FILE FILE-NAME=NDVvrs.MOD,SUPPRESS-ERRORS=*FILE-EXISTING /ADD-FILE-LINK LINK-NAME=BLSLIB02,FILE-NAME=NDVvrs.MOD,SUPPORT=*DISK /CREATE-FILE FILE-NAME=CMPRMIN.RMDBG,SUPPRESS-ERRORS=*FILE-EXISTING /ADD-FILE-LINK LINK-NAME=CMPRMIN,FILE-NAME=CMPRMIN.RMDBG,SUPPORT=*DISK /CREATE-FILE FILE-NAME=ADAvrs.MOD,SUPPRESS-ERRORS=*FILE-EXISTING /ADD-FILE-LINK LINK-NAME=DDLIB,FILE-NAME=ADAvrs.MOD,SUPPORT=*DISK /CREATE-FILE FILE-NAME=DBGTRACE.NATBATCH,SUPPRESS-ERRORS=*FILE-EXISTING /ADD-FILE-LINK LINK-NAME=DBGTRACE,FILE-NAME=DBGTRACE.NATBATCH,SUPPORT=- / *DISK(SHARED-UPDATE=*YES) 1 /START-EXE-PROG F-F=*LI-E(L=NATvrs.MOD,EL=NATvrsBA,TYPE=L) /EXIT-JOB MODE=NORMAL
1: Specifies the trace file. The
SHARED-UPDATE option enables the user to lookup the trace file
while the debug task is still running.
The Natural parameter file
CMPRMIN.RMDBG for example
has the following content:
If the Natural environment dependent nucleus is shared by various Natural applications that are running under TIAM, UTM or batch, NATADvrs has to be linked to each of the Natural environment dependent nuclei. For the assemblies of the Natural drivers this means, that the parameter
LINK=(NATADBG) has to be specified to
enable the BS2000 loader to find the load points of
NATADvrs in the particular environment dependent
The following topics are covered below:
For information on how to map an environment, refer to the Natural Single Point of Development documentation, section First Steps with Natural SPoD, Local and Remote Environment, Connecting to a Development Server for the First Time.
APSSVR0026-* Server NCFNAT41 started APSOPC0000-* SMARTServer is initialized
The following messages are displayed when parameter
Template session initialized Template runtime connected Template runtime terminated Template ready for clone Main listener activated Setup PAL environment successful Listener thread launched 01625028 ************************************************ ************ Server is up ************** ************************************************ Waiting for terminate event...
The following topics are covered below:
SMARTS PFS (Portable or POSIX File System) implements a file system, known from UNIX systems, in a mainframe environment. Basically, it consists of a container file, which comprises all (UNIX) files and a corresponding (logical) access method, which processes all requested I/O operations.
The container file has to be allocated and preformatted using the
CREATE-PFS (described below).
The PFS maps all file names to a node of a directory tree within
the physical container file. In the case of BS2000, this container file is a
PAM file with a block size of 4 KB (
Within Natural, the actual path is specified by a corresponding
DEFINE WORK FILE statement in the program which executes work file
or print file access.
Each node (subdirectory) is separated by a slash (/) from its parent. The highest level qualifies the file name.
DEFINE WORK FILE 1 '/MISC/USER1/TESTFILE/'
ROOT' => MISC => 'USER1 =>
DEFINE WORK FILE 1 'TESTFILE2.W01'
ROOT' => TESTFILE2.W01
The Natural server uses the SMARTS portable file system (PFS) as a data container for Natural work files, print files, temporary sort files and the editor work file. The SMARTS PFS is the only storage medium available for these files under SMARTS.
In order to be able to use the PFS for Natural files you have to configure Natural accordingly:
For work files or print files, specify the access method
AM=SMARTS, using the Natural profile parameters
WORK (Work-File Assignments) and/or
For temporary sort files, specify the type of storage medium
STORAGE=SMARTS, using the Natural profile parameter
SORT (Control of Sort Program).
And to allocate the editor work file in the PFS, specify the
work file mode
FMODE=SM, using the Natural profile parameter
EDBP (Software AG Editor Buffer Pool Definitions).
If you use one of these options, you have to configure your SMARTS to use a PFS.
The file PFS.TST should not exist before the allocation procedure is executed, otherwise DMS error DMS0683 will occur.
The initialization can be done by using the following procedure:
/CLP FROM-FILE=*LIBRARY-ELEMENT(LIBRARY=APSvrs.LIB,ELEMENT=CREATE-PFS, - / TYPE=SYSJ),PROCEDURE-PARAMETERS=(FILE-NAME=PFS.TEST,SIZE=4096K, - / APS-LIB=APSvrs.LIB)
In the SMARTS
SYSPARM configuration file, add the
CDI_DRIVER=('CIO,PAAQBIO,PFSTSK=PFSTASK,TRACE=N') CDI_DRIVER=('TESTPFS,PAANPFS,LRECL=4096,CONTAINER=CIO:PFS/TEST/') MOUNT_FS=('TESTPFS://','/')