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.
| Dataset Name | Contents |
|---|---|
APSvrs.LIB |
Contains the load modules and the procedures of the SMARTS server. |
APSvrs.L0pp |
Patch-level of SMARTS (product code APS). The content of this
library must be copied into the library
APSvrs.LIB.
|
NDVvrs.MOD |
Contains the load modules of the Natural Development Server. |
NDVvrs.JOBS |
Contains the Installation Job Control for those customers who want to install without using System Maintenance Aid (SMA). |
NDVvrs.EXPL |
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. |
NDVvrs.INPL |
Contains the transaction processors. |
NDVvrs.ERRN |
Contains the error messages of the transaction processor. |
NDVvrs.SYSF |
Contains the field definition table (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 corresponding Natural Release Notes for
Mainframes).
|
NCFvrs.MOD |
Contains the load modules of the Natural Com-plete Interface (required for SMARTS). |
NCFvrs.MAC |
Contains the macros of the Natural Com-plete Interface (required for SMARTS). |
- where
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 JOBLIB stands
for
the example job library
(NDVvrs.JOBS), if you are not using
SMA, or
the SMA job library (see SMA parameter JOBLIB
in SMA Parameter Group BASIC), if you are using SMA.
Software AG uses the following naming conventions for source elements
in the library JOBLIB:
A<product-code><function>
= Assembler sources
L<product-code><
function> = Instruction for
TSOSLNK/BINDER
| Element | Description |
|---|---|
NDV-SYSPARM |
SMARTS parameters for NDV. See also SMARTS SYSPARM Parameters. |
NDV-CONFG |
NDV configuration parameters. See also NDV Configuration Parameters. |
NDV-ADAPARM |
ADALNK parameter for NDV.
|
ANDVPARM |
Assembler source - Natural parameter module for NDV. |
LNATSHAR |
Link instructions to link the Natural nucleus. |
LNDVFRNT |
Link instructions to link the NDV front-end module. |
START-NDV |
Procedure to start the NDV server. |
STOP-NDV |
Procedure to stop the NDV server. |
SHOW-SYSOUT |
Procedure to show the SYSOUT file of the FSIO
task of NDV.
|
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
NDVvrs.SYSF.
The layout of the Development Server
File corresponds to the layout of the Predict dictionary file
FDIC.
Note:
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 the
library JOBLIB.
(Job I060, Step 3802)
This step is optional.
The Natural nucleus module must be relinked with the modules
NAT3270 and NAT3279 if they have not been included
yet. This is accomplished by using the source LNATSHAR which is
contained in the library JOBLIB.
If you are using SMA, please refer to the SMA read-me file of
NDVvrn (skeleton
##NDVvrn-README).
(Job I060, Steps 8410)
Link the NDV front-end module by using the source LNDVFRNT
which is contained in the library JOBLIB.
(Job I061, Steps 8450,8451,8452)
During the loading of the NDV related objects with the Natural utility
INPL, the assigned system file(s) FDIC and/or
FSEC is/are initialized with NDV-specific information.
Using the INPL utility, load the objects
from dataset NDVvrs.INPL onto your
Natural system file (FNAT). The Natural profile parameter
FDIC must have been set to point to your development
server file.
Using ERRLODUS, load the error messages
from dataset NDVvrs.ERRN.
To use the tutorial (see First Steps with Natural Single
Point of Development in the Natural Single Point of Development
documentation, load the sample programs from dataset
NDVvrs.EXPL to your Natural system file
FNAT.
(Job I085, Step 8400)
The procedure CREATE-PFS is called to allocate and format
a PFS file.
This procedure has to be supplied with the following parameters:
FILE-NAME |
The name of the container file. |
FILE-SIZE |
The size of the container file. To be specified either in K for kilobytes or M for megabytes. |
APS-LIB |
The SMARTS library where the format utility
PFSUTIL resides.
|
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
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.
If Natural Security (NSC) is installed:
The NDV initial user ID (default ID is STARGATE) must be
defined in Natural Security (NSC) with a valid default library. Refer also to
NDV configuration parameter INITIAL_USERID in
the section Development Server
Configuration. 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 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.
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
TRACE_LEVEL=31 was
set:
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
BS2000 procedure 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 (STD,2).
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/'
Specifies: ROOT' => MISC => 'USER1 =>
'TESTFILE
://MISC/USER1/TESTFILE
DEFINE WORK FILE 1 'TESTFILE2.W01'
Specifies: 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
PRINT (Print File Assignments).
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
following lines:
CDI_DRIVER=('CIO,PAAQBIO,PFSTSK=PFSTASK,TRACE=N')
CDI_DRIVER=('TESTPFS,PAANPFS,LRECL=4096,CONTAINER=CIO:PFS/TEST/')
MOUNT_FS=('TESTPFS://','/')