This section describes step by step how to install Natural for DL/I, also referred to as NDL.
Notation vrs or vr: If used in the following document, the notation vrs or vr stands for the relevant version, release, system maintenance level numbers. For further information on product versions, see Version in the Glossary.
Products and versions are specified under Natural and Other Software AG Products in and Operating/Teleprocessing Systems Required in the current Natural Release Notes.
The installation tape contains the datasets listed in the table below. The sequence of the datasets is shown in the Report of Tape Creation which accompanies the installation tape.
| Dataset Name | Contents |
|---|---|
NDLnnn.LOAD |
Natural executable modules necessary for the linkage editor. |
NDLnnn.SRCE |
Macros and sources for the parameter module NDLPARM
and for the batch procedures NATDBD/NATPSB.
|
NDLnnn.JOBS |
Example installation jobs. |
The notation vrs in dataset
names represents the version number of the product.
If you are using SMA, refer to the System Maintenance Aid documentation (included in the current edition of the Natural documentation CD).
If you are not using SMA, follow the instructions below.
This section explains how to:
Copy dataset COPY.JOB from tape to disk.
Modify this dataset to conform to your local naming conventions.
The JCL in this dataset is then used to copy all datasets from tape to disk.
If the datasets for more than one product are delivered on the tape, the
dataset COPY.JOB contains the JCL to unload the datasets for all
delivered products from the tape to your disk.
After that, you will have to perform the individual install procedure for each component.
The dataset COPY.JOB (Label 2) contains the JCL to unload all
other existing datasets from tape to disk. To unload COPY.JOB, use
the following sample JCL:
//SAGTAPE JOB SAG,CLASS=1,MSGCLASS=X //* --------------------------------- //COPY EXEC PGM=IEBGENER //SYSUT1 DD DSN=COPY.JOB, // DISP=(OLD,PASS), // UNIT=(CASS,,DEFER), // VOL=(,RETAIN,SER=tape-volume), // LABEL=(2,SL) //SYSUT2 DD DSN=hilev.COPY.JOB, // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=volume, // SPACE=(TRK,(1,1),RLSE), // DCB=*.SYSUT1 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //
where:
hilev is a valid high level
qualifier
tape-volume is the tape
volume name, for example: T12345
volume is the disk volume
name
Modify the COPY.JOB on your disk to conform to your local
naming conventions and set the disk space parameters before submitting this
job:
Set HILEV to a valid high level qualifier.
Set LOCATION to a storage location.
Set EXPDT to a valid expiration date.
Submit COPY.JOB to unload all other datasets from the tape to
your disk.
The installation tape contains the datasets listed in the table below. The sequence of the datasets is shown in the Report of Tape Creation which accompanies the installation tape.
| Dataset Name | Contents |
|---|---|
NDLnnn.LIBR |
LIBR backup file
|
The notation nnn in dataset
names represents the version number of the product.
If you are using SMA, refer to the System Maintenance Aid documentation (included in the current edition of the Natural documentation CD).
If you are not using SMA, follow the instructions below.
This section explains how to:
Copy dataset COPYTAPE.JOB from tape to disk.
Modify this dataset to confom with your local naming conventions.
The JCL in this member is then used to copy all datasets from tape to disk.
If the datasets for more than one product are delivered on the tape, the
member COPYTAPE.JOB contains the JCL to unload the datasets for
all delivered products from the tape to your disk, except the datasets that you
can directly install from tape, for example, Natural INPL
objects.
After that, you will have to perform the individual install procedure for each component.
The dataset COPYTAPE.JOB contains the JCL to unload all other
existing datasets from tape to disk. To unload COPYTAPE.JOB, use
the following sample JCL:
* $$ JOB JNM=LIBRCAT,CLASS=0, + * $$ DISP=D,LDEST=(*,UID),SYSID=1 * $$ LST CLASS=A,DISP=D // JOB LIBRCAT * ***************************************** * CATALOG COPYTAPE.JOB TO LIBRARY * ***************************************** // ASSGN SYS004,nnn <------ tape address // MTC REW,SYS004 // MTC FSF,SYS004,4 ASSGN SYSIPT,SYS004 // TLBL IJSYSIN,'COPYTAPE.JOB' // EXEC LIBR,PARM='MSHP; ACC S=lib.sublib' <------- for catalog /* // MTC REW,SYS004 ASSGN SYSIPT,FEC /* /& * $$ EOJ
where:
nnn is the tape
address
lib.sublib is the library and
sublibrary of the catalog
Modify COPYTAPE.JOB to conform to your local naming
conventions and set the disk space parameters before submitting this job.
Submit COPYTAPE.JOB to unload all other datasets from the
tape to your disk.
The NDL installation procedure consists of the following steps:
Modify the NDL parameter module NDLPARM as described in
the section Natural Parameter
Modifications for DL/I.
Assemble and link/catalog NDLPARM.
Modify the appropriate I060 and I080 jobs according to the TP monitor or batch modules you are relinking; for example, NATI060 for batch and NCII080 for CICS. This applies also to Step 3 below.
Add the parameter DLISIZE and specify
DLISIZE=27. This value applies if the default values of the
NDLPARM parameters are used.
Add an NTDB macro specifying the database
identification list (DBID list) that relates to DL/I segment types. The numbers
specified in this DBID list must be in the range from 1 to 254. They indicate
which DBIDs are reserved for DL/I segment types. Up to 254 entries can be
specified. All Natural DDMs that refer to a DL/I segment type are cataloged
with a DBID from this list. The number with the lowest value in this list is
the default DBID for DL/I segment types.
NTDB DLI,(250,253,252) NTDB DLI,250
Note:
Values for DL/I database IDs above 255 are not possible.
Under z/OS: Add the following
INCLUDE instructions and the corresponding DD statements to the
link step for Natural and link-edit the executable module:
| CICS | IMS TM | Batch Mode |
|---|---|---|
INCLUDE NDLLIB(NDLNUC) |
INCLUDE NDLLIB(NDLNUC) |
INCLUDE NDLLIB(NDLNUC) |
INCLUDE NDLLIB(NDLSIOCX) |
INCLUDE NDLLIB(NDLSIOBA) |
INCLUDE NDLLIB(NDLSIOBA) |
INCLUDE SMALIB(NDLPARM) |
INCLUDE SMALIB(NDLPARM) |
INCLUDE SMALIB(NDLPARM) |
INCLUDE TPSLIB(ASMTDLI) |
INCLUDE DLILIB(ASMTDLI) |
INCLUDE DLILIB(ASMTDLI) |
Under z/VSE: Add the following
INCLUDE instructions and the corresponding sublibraries for NDL to
the search chain for the linkage editor and link-edit the executable
module:
| CICS | Batch Mode |
|---|---|
INCLUDE NDLNUC |
INCLUDE NDLNUC |
INCLUDE NDLSIOCX |
INCLUDE NDLSIOBA |
INCLUDE NDLPARM |
INCLUDE NDLPARM |
INCLUDE ASMTDLI |
INCLUDE ASMTDLI |
Under CICS, the link-edit of the load module that contains NDL can be done in any of the following ways:
Include all NDL modules (that is, NDLNUC,
NDLPARM and NDLSIOCX) and the DL/I module
ASMTDLI in the link-edit of Natural.
Include all NDL modules (that is, NDLNUC,
NDLPARM and NDLSIOCX) and the DL/I module
ASMTDLI in the link-edit of the Natural TP driver. This way of
link-editing only applies if the Natural TP driver runs separately from the
Natural nucleus.
Link-edit all NDL modules (that is, NDLNUC,
NDLPARM and NDLSIOCX), the DL/I module
ASMTDLI and an alternate Natural parameter module as a separate
module with the mandatory entry name
CMPRMTB. The name of the
resulting module is optional. This way of link-editing only applies if an
alternate parameter module (PARM=) is used. If so, under CICS, an
additional CICS PPT entry with
PROGRAM=name is required.
Link-edit all NDL modules (that is, NDLNUC,
NDLPARM and NDLSIOCX) and the DL/I module
ASMTDLI as a separate module with the mandatory
entry name NATGWDLI. The
name of the resulting module is
optional. If it is different from NATGWDLI, however, it must be
specified as an alias name in an NTALIAS macro entry of
the Natural parameter module. This way of link-editing only applies if the
Natural Resolve CSTATIC Addresses feature (RCA) is used. If so, under CICS, an
additional CICS PPT entry with
PROGRAM=name is required.
Include all environment-independent NDL Modules (that is,
NDLNUC and NDLPARM) in the link-edit of Natural
Include the environment-dependent NDL I/O module (NDLSIOCX) in the
link-edit of the Natural TP driver. This way of link-editing only applies if a
shared nucleus is created.
To verify the installation of NDL with a sample database rather than with existing databases, you perform the following steps:
Allocate VSAM spaces for the sample database (Job I008, Steps 1500 to 1502).
Create the DBDs, PSBs and ACB, and perform the initial load (Job I053, Steps 1500 to 1560). Creation of an ACB only applies to z/VSE.
Execute procedures NATPSB and NATDBD for
the sample database (Job I075, Steps 1500 and 1510).
To enable Natural to access DL/I databases, additional data must be
added to the FDIC system file. To do so, the procedures
NATPSB
and NATDBD must be
executed for each PSB/DBD to be used.
If you are not using System Maintenance Aid (SMA) the following
applies: When executing modules NDPBNDB0 or NDPBNSB0
in an LE370 enabled batch Natural to store an NDB or NSB into the
FDIC system file, the following Natural error message may be
issued:
SYSDLI 3970 Error when loading NDB/NSB
The step ends with Condition Code 8 in this case.
To prevent this error, the NDB or NSB load module must be
link-edited with AMODE(31). The binder step will then end with
Return Code 4 due to the following warning message:
IEW2651W 511C ESD AMODE 24 CONFLICTS WITH USER-SPECIFIED AMODE 31
This return code must be ignored in the following step by means of a
COND=(8,LE) keyword.
To verify the installation of Natural for DL/I
Invoke online Natural.
Invoke the Natural utility SYSDDM by entering the
following system command: SYSDDM
On the SYSDDM menu, enter function code D
to invoke the DL/I Services function.
On the resulting screen, enter function code D to invoke
the NDB Maintenance function.
On the resulting screen, enter function code S to select
the NDB which was created in substep 3 of Step 4.
On the resulting screen, enter function code L to list
the NDB segments.
On the resulting screen, enter function code A to assign
DBID and FNR to the segments.
On the same screen, enter function code G to generate a
DDM from the segment description.
Catalog the generated DDM.
Only if running under CICS: Enter NATPSB ON
psbname in the Command line.
Edit and run the following program:
DEFINE DATA LOCAL
01 COURSE VIEW OF DPQA03-COURSE
02 COURSEN
02 TITLE
02 DESCRIPN
/* End of DPQA03-COURSE View
END-DEFINE
READ (100) COURSE BY COURSEN
DISPLAY COURSEN TITLE DESCRIPN
END