The Natural system files FNAT, FUSER,
FDIC, FSEC and FSPOOL can also be
located on VSAM files.
To support the locking of source objects a separate FLOCK
file and related paths are necessary.
This section covers the following topics:
See the Prerequisites under Installing Natural for VSAM in the Installation section.
For the installation of Natural ISPF on VSAM system files, refer to the
Natural ISPF Installation documentation. Be sure that you
use the relevant module (NVSISPV) provided on the Natural for VSAM
installation tape.
This section describes step by step how to install Natural under the operating system z/OS using VSAM system files. The information given is basically a combination of the installation descriptions for both base Natural and Natural for VSAM (product code NVS), plus some points specific to VSAM system files.
To install Natural with VSAM system files, you need the datasets for both base Natural and Natural for VSAM. The required datasets are listed in the table below:
| Dataset Name | Contents |
|---|---|
NATvrs.ERRN |
Natural error messages. |
NATvrs.LOAD |
Natural load modules. |
NATvrs.SRCE |
Natural source modules and macros. |
NATvrs.JOBS |
Example installation jobs. |
NATvrs.INPL |
Natural system programs. |
NATvrs.EXPL |
Natural example programs. |
NVSvrs.LOAD |
Natural for VSAM load modules. |
NVSvrs.SRCE |
Natural for VSAM source modules. |
NVSvrs.EMPL |
Natural for VSAM example file. |
NVSvrs.EXPL |
Natural for VSAM example programs. |
NVSvrs.LINI |
Natural for VSAM Locking Source Objects. |
NVSvrs.VINI |
Natural for VSAM FDIC initialization file.
|
The notation vrs in dataset
names represents the version number of the product. The sequence of the
datasets is shown in the Report of Tape Creation which
accompanies the installation tape.
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.
Under z/OS, the installation procedure for Natural with VSAM system files consists of the following steps:
Load the VSAM demo file EMPL and define the alternate
index path EMPLX for the file EMPL.
Define three VSAM clusters to be used as system files for Natural
(FNAT, FUSER and FDIC), an alternate
index and a path for the alternate index for FDIC.
It is strongly recommended that you keep these three system files on separate VSAM clusters.
This step must only be performed if you have Natural Advanced Facilities installed and want your spool file to be a VSAM file, too.
Define an additional VSAM cluster to be used as spool file
(FSPOOL) and five alternate indices.
Note:
Path processing is not supported
for FSPOOL.
This step must only be performed if you have Natural Security installed and want your security file to be a VSAM file, too.
Define an additional VSAM cluster to be used as security file
(FSEC) and three alternate indices.
Note:
Path processing is not supported
for FSEC.
Allocate VSAM SCRATCH PAD File - Job VSAMI008, Step 1450
Initialization VSAM SCRATCH PAD File - Job VSAMI008, Step 1451
This step must only be performed if you want to use a scratch-pad
file; that is, if you want to use read-only system files (ROSY=ON); see also
the parameter ROSY and the macro
NTLFILE
(described in the Natural Parameter Reference
documentation).
Define an additional VSAM cluster to be used as scratch-pad file.
For the optional scratch-pad file inclusion, the following
NATPARM parameters must be added or, if already present, updated
with:
NTLFILE 212,dbid,nt-file-number,dd-name-scratch-pad-file ROSY=ON
If you want your system file(s) to be opened for input, adapt your Natural parameter module as follows:
FNAT=(dbid,fnr,filename,,RO), FUSER=(dbid,fnr,filename,,RO), FSEC=(dbid,fnr,filename,,RO),
This step must only be performed if you want to use a locking of
source objects on VSAM system file (SLOCK=PRE); see also the
parameter SLOCK and the macro
NTLFILE
(described in the Natural Parameter Reference
documentation).
Define an additional VSAM cluster to be used as source locking file.
For the optional source locking file inclusion, the following
NATPARM parameters must be added or, if already present, updated
with:
NTLFILE 002,dbid,nt-file-number,dd-name-source-locking-file,,PATH SLOCK=PRE
The default dd-name is FLOCK, the related default pathes
are FLOCKA, FLOCKB and FLOCKC.
Allocate and Define VSAM Source Locking File - Job VSAMI008, Step 1460
Printing Data Records VSAM Source Locking File - Job VSAMI008, Step 1461
This step must only be performed if you want to use a VSAM Source
Locking File; that is, if you want to use VSAM Source Locking parameter
SLOCK -
Source Locking (described in the Natural Parameter
Reference documentation).
Assemble and link the Natural z/OS interface module NATOS
contained in dataset NATnnn.SRCE.
Edit, assemble and link the Natural for VSAM parameter module
NVSPARM. For a description of the parameters which can be
specified, see Assembling
the NVSPARM Parameter Module in the section
Natural for VSAM Parameters.
Assemble and link the Natural for VSAM I/O module NVSMISC
with the LSR options:
DEFER=YES COMMIT=NO READINT=NO
See a description of the parameters which can be specified in
NVSMISC (see
the section Natural for VSAM Parameters).
Create the Natural batch parameter module.
To install Natural with VSAM system files, in addition to the
VSIZE
and NTDB
specification, you must modify the parameters FNAT,
FUSER and
FDIC as
follows:
VSIZE=126, FNAT=(vsam-dbid,fnr-fnat,dd-name-fnat), FUSER=(vsam-dbid,fnr-fuser,dd-name-fuser), FDIC=(vsam-dbid,fnr-fdic,dd-name-fdic), NTDB VSAM,vsam-dbid
vsam-dbid must have the same value in all four entries.
It is recommended to use different files and different file numbers
for FNAT and FUSER. The
FDIC file must be a file different from FNAT
and FUSER. Therefore, the FDIC parameter must
not be omitted.
The DD names are the logical names of the system files; each DD name
can be up to seven characters long. The DD name for the FDIC path
is created by appending an X to the DD name of the
FDIC file.
If you have Natural Advanced Facilities installed and want your spool
file to be a VSAM file, modify the FSPOOL parameter
accordingly:
FSPOOL=(vsam-dbid,fnr-fspool,dd-name-fspool)
If you have Natural Security installed and want your security file to
be a VSAM file, modify the FSEC parameter
accordingly:
FSEC=(vsam-dbid,fnr-fsec,dd-name-fsec)
The FSEC file must be a file different from
FNAT.
For information on the components and structure of the Natural interface to VSAM, see also Components of Natural for VSAM and Structure of the Natural Interface to VSAM.
With the INCLUDE instruction for the parameter module,
specify the name of the Natural parameter module created in Step 8.
Add the following INCLUDE instructions to the link of the
Natural batch nucleus:
INCLUDE NVSLIB(NVSNUC) INCLUDE NVSLIB(NVSFNAT) INCLUDE NVSLIB(NVSFSPO) INCLUDE NVSLIB(NVSFSEC) INCLUDE SMALIB(NVSFLOCK) INCLUDE SMALIB(NVSPARM) INCLUDE SMALIB(NVSMISC)
The module NVSFSPO is only required if you have Natural
Advanced Facilities installed and want your spool file to be a VSAM file,
too.
The module NVSFSEC is only required if you have Natural
Security installed and want your security file to be a VSAM file, too.
The module NVSFLOCK is only required if you want locking
for source objects on VSAM system files FUSER/FNAT.
If your front-end is not linked to your Natural nucleus,
NVSPARM and NVSMISC must be linked to
NATPARM instead.
Add the corresponding DD statements to the link step for Natural and link-edit the executable module.
Link the executable batch Natural nucleus.
Use the Natural system command INPL (see the Natural System
Command Reference documentation) to load the Natural system programs
(dataset NATnnn.INPL) into the Natural
system files.
Ensure that the DD names specified in NATPARM are
specified in the INPL job, too. In addition, an alternate index DD
name (dd-name-fdicX) must be specified
for FDIC.
Note:
If you want to install any other Software AG products that require
INPL steps, ensure that these INPL steps are adapted
according to the VSAMI061 job.
Load the Natural error messages file (dataset
NATnnn.ERRN) using the program
ERRLODUS
as described in the Natural SYSERR Utility
documentation.
Ensure that the DD names specified in NATPARM are
specified in the ERRLODUS job, too.
Use the system command INPL to load the
Natural example programs (dataset
NATnnn.EXPL) and the Natural for VSAM
example programs (dataset NVSnnn.EXPL)
into the Natural system file.
Ensure that the DD names specified in NATPARM are
specified in the INPL job, too. In addition, a path DD name
(dd-name-fdicX) must be specified for
FDIC.
Reorganize the FNAT system file using the VSAM facility
AMS REPRO to unload and reload the file.
This step must only be performed if you wish to install Natural for VSAM under CICS.
If Natural for VSAM is to be installed under CICS, assemble and link
the module NVSCICS.
Proceed with the specific installation steps for Natural required under your TP monitor (see the relevant sections in the Natural Installation documentation), taking into account the following additions:
Modify your Natural online parameter modules according to Step 8.
Add the following INCLUDE instructions to all links of the online Natural nucleus:
INCLUDE NVSLIB(NVSNUC) INCLUDE NVSLIB(NVSFNAT) INCLUDE NVSLIB(NVSFSPO) INCLUDE NVSLIB(NVSFSEC) INCLUDE NVSLIB(NVSFLOCK)
The module NVSFSPO is only required if you have
Natural Advanced Facilities installed and want your spool file to be a VSAM
file, too. The online environment for Natural Advanced Facilities must be a
CICS environment, and the VSAM spool files must be defined in the CICS FCT. The
module NVSFSEC is only required if you have Natural Security
installed and want your security file to be a VSAM file, too. The VSAM security
files must be defined in the CICS FCT. The module NVSFLOCK is only
required if you want locking for source objects on VSAM system files
FUSER/FNAT. The VSAM locking files must be defined in
the CICS FCT.
Add the following INCLUDE instructions to the link of
the front-end in a CICS environment:
INCLUDE SMALIB(NVSPARM) INCLUDE SMALIB(NVSCICS)
Add the following INCLUDE instructions to the link of
the front-end in any other supported environment:
INCLUDE SMALIB(NVSPARM) INCLUDE SMALIB(NVSMISC)
Before starting Natural, ensure that the DD and DSN names of the VSAM system files are known in your respective batch and online environments.
| TP Monitor | Instruction | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Com-plete | Catalog the VSAM system files FNAT,
FUSER, FDIC and FDICX to Com-plete using
the CA function of the Com-plete utility UFILE.
If Natural Security is installed, catalog the VSAM security files
If locking of source objects for VSAM system files
If you have specified |
||||||||||||||||||||||||||||||||||||||||||
| CICS | Add the following entries to your FCT:
Refer to the job VSAMI005 for examples. You can add DD statements for these datasets to your CICS startup job, too. |
||||||||||||||||||||||||||||||||||||||||||
| TSO |
Add the following statements to your Natural CLIST:
|
This section describes step by step how to install Natural under the operating system z/VSE using VSAM system files. The information given is basically a combination of the installation descriptions for both base Natural and Natural for VSAM (product code: NVS), plus some points specific to VSAM system files.
To install Natural with VSAM system files, you need the datasets for both base Natural and Natural for VSAM. The required datasets are listed in the table below:
| Dataset Name | Contents |
|---|---|
NATnnn.LIBR |
Natural source modules, macros, relocatable modules and sample installation jobs. |
NATnnn.INPL |
Natural system programs. |
NATnnn.EXPL |
Natural example programs. |
NATnnn.ERRN |
Natural error messages. |
NVSnnn.LIBR |
Natural for VSAM source modules, macros and relocatable modules. |
NVSnnn.EMPL |
Natural for VSAM example file. |
NVSnnn.EXPL |
Natural for VSAM example programs. |
NVSnnn.LINI |
Natural for VSAM Locking Source Objects. |
NVSnnn.VINI |
Natural for VSAM FDIC initialization file.
|
The notation nnn in dataset
names represents the version number of the product. The sequence of the
datasets, their type and the space each dataset requires on disk are shown in
the Report of Tape Creation which accompanies the
installation tape.
The sample JCS supplied on tape for the installation of Natural assumes one library, which has installation sublibraries per Software AG product library. In addition to these sublibraries, you need a work sublibrary and a sublibrary for sample installation jobs for Natural. It is recommended that you create this library and the work sublibrary now.
Then copy the sublibrary containing the sample installation jobs from tape using the following JCS:
* $$ JOB JNM=NATJOBS,CLASS=0,DISP=D,LDEST=*,SYSID=1
* $$ LST CLASS=A,DISP=D
// JOB NATJOBS
// ASSGN SYS005,IGN
// ASSGN SYS006,cuu,VOL=NVSnnn
// MTC REW,SYS006
// MTC FSF,SYS006,nn
* Tape positioned at file ?, tape mark nn
* *** Now process NVSnnn.LIBR - JOBS ***
// EXEC LIBR,PARM='MSHP'
RESTORE SUBLIB=SAGLIB.NVSnnnJ:SAGLIB.NVSnnnJ -
TAPE=SYS006 -
LIST=YES -
REPLACE=NO
/*
// MTC REW,SYS006
/*
/&
* $$ EOJ
The notation cuu represents
the physical unit address of the tape drive.
The notation nn represents the
file sequence number given by "(3 *
file-no) - 2", as shown on the
Report of Tape Creation. Leave out the // MTC FSF
... instructions if your library is the first dataset on the tape.
The notation nnn represents
the version number of the product.
Now use jobs NATTAPE and NVSTAPE from this
job library to restore the Natural sublibrary from tape and make Natural known
to MSHP.
All further datasets will be directly used from tape by the installation jobs.
Under z/VSE, the installation procedure for Natural with VSAM system files consists of the following steps:
Load the VSAM demo file EMPL and define the alternate
index path EMPLX for the file EMPL.
Define three VSAM clusters to be used as system files for Natural
(FNAT, FUSER and FDIC) and a path for
FDIC.
It is strongly recommended that you keep these three system files on separate VSAM clusters.
This step must only be performed if you have Natural Advanced Facilities installed and want your spool file to be a VSAM file, too.
Define an additional VSAM cluster to be used as spool file
(FSPOOL) and five alternate indices.
Note:
Path processing is not supported for
FSPOOL.
This step must only be performed if you have Natural Security installed and want your security file to be a VSAM file, too.
Define an additional VSAM cluster to be used as security file
(FSEC) and three alternate indices.
Note:
Path processing is not supported for
FSEC.
Allocate VSAM SCRATCH PAD File - Job VSAMI008, Step 1450
Initialization VSAM SCRATCH PAD File - Job VSAMI008, Step 1451
This step must only be performed if you want to use a scratch-pad
file; that is, if you want to use read-only system files
(ROSY=ON); see also the parameter
ROSY and
the macro NTFILE in the
section Profile Parameters in the Natural
Parameter Reference documentation.
Define an additional VSAM cluster to be used as scratch-pad file.
For the optional scratch-pad file inclusion, the following
NATPARM parameters must be added or, if already present, updated
with:
NTFILE ID=212,DBID=dbid,FNR=nt-file-number,PASSWD=dd-name-scratch-pad-file ROSY=ON
If you want your system file(s) to be opened for input, adapt your Natural parameter module as follows:
FNAT=(dbid,fnr,filename,,RO), FUSER=(dbid,fnr, filename,,RO), FSEC=(dbid,fnr,filename,, RO),
This step must only be performed if you want to use a locking of
source objects on VSAM system file (SLOCK=PRE); see also the
parameter SLOCKand the macro
NTFILE
(described in the Natural Parameter Reference
documentation).
Define an additional VSAM cluster to be used as source locking file.
Allocate and Define VSAM Source Locking File - Job VSAMI008, Step 1460
Printing Data Records VSAM Source Locking File - Job VSAMI008, Step 1461
For the optional source locking file inclusion, the following
NATPARM parameters must be added or, if already present, updated
with:
NTLFILE 002,dbid,nt-file-number,dd-name-source-locking-file,,PATH SLOCK=PRE
The default dd-name is FLOCK, the related default pathes
are FLOCKA, FLOCKB and FLOCKC.
Set the parameters in the source of the module NATVSE to
suit your requirements. The NATVSE generation parameters are
described in the section Running Natural in Batch under
z/VSE (Natural in Batch Mode) in the
Natural Operations documentation.
Assemble and link the Natural z/VSE interface module
NATVSE contained in dataset
NATnnn.LIBR.
Edit, assemble and link the Natural for VSAM parameter module
NVSPARM. For a description of the parameters which can be
specified, see the section Assembling the NVSPARM Parameter
Module.
For a quick installation, use the Natural for VSAM LSR feature and
specify the following NVMLSR definitions in NVSPARM
(see also NVMLSR
Macro in the section Natural for VSAM
Parameters):
NVMLSR DDNAME=fnat-dd-name,SHRPOOL=1 NVMLSR DDNAME=fuser-dd-name,SHRPOOL=2 NVMLSR DDNAME=fdic-dd-name,SHRPOOL=3 NVMLSR DDNAME=fdicx-dd-name,SHRPOOL=3
If you want to use FSEC system files:
NVMLSR DDNAME=fsec-dd-name,SHRPOOL=4 NVMLSR DDNAME=fseca-dd-name,SHRPOOL=4 NVMLSR DDNAME=fsecb-dd-name,SHRPOOL=4 NVMLSR DDNAME=fsecc-dd-name,SHRPOOL=4
Assemble and link the Natural for VSAM I/O module NVSMISC
with the LSR options:
DEFER=YES COMMIT=NO READINT=NO
See the description of the parameters which can be specified in
NVSMISC (see
the section Natural for VSAM Parameters).
Create the Natural batch parameter module.
To be able to install Natural with VSAM system files, in addition to
the VSIZE
and NTDB specification,
modify the parameters FNAT,
FUSER and
FDIC as
follows:
VSIZE=126, FNAT=(vsam-dbid,fnr-fnat,dlbl-name-fnat), FUSER=(vsam-dbid,fnr-fuser,dlbl-name-fuser), FDIC=(vsam-dbid,fnr-fdic,dlbl-name-fdic), NTDB VSAM,vsam-dbid
vsam-dbid must have the same
value in all four entries.
It is recommended to use different files and different file numbers
for FNAT
and FUSER.
The FDIC file must be a file different from
FNAT and FUSER. Therefore, the
FDIC
parameter must not be omitted.
The DD names are the logical names of the system files; each DD name
can be up to seven characters long. The DLBL name for FDIC is
created by appending an X to the DLBL name for the
FDIC file.
If you have Natural Advanced Facilities installed and want your spool
file to be a VSAM file, modify the FSPOOL parameter
accordingly:
FSPOOL=(vsam-dbid,fnr-fspool,dd-name-fspool)
Assemble and link the parameter module.
If you have Natural Security installed and want your security file to
be a VSAM file, modify the FSEC parameter accordingly:
FSEC=(vsam-dbid,fnr-fsec,dd-name-fsec)
The FSEC file must be a file different from FNAT.
For information on the components and structure of the Natural interface to VSAM, see also Components of Natural for VSAM and Structure of the Natural Interface to VSAM.
With the INCLUDE instruction for the parameter module,
specify the name of the Natural parameter module created in Step 8.
Add the following INCLUDE instructions to the link of the
Natural batch nucleus:
INCLUDE NVSNUC INCLUDE NVSFNAT INCLUDE NVSFSPO INCLUDE NVSFSEC INCLUDE NVSFLOCK INCLUDE NVSPARM INCLUDE NVSMISCD
The module NVSFSPO is only required if you have Natural
Advanced Facilities installed and want your spool file to be a VSAM file,
too.
The module NVSFSEC is only required if you have Natural
Security installed and want your security file to be a VSAM file, too.
The module NVSFLOCK is only required if you want locking
for source objects on VSAM system files FUSER/FNAT.
If your front-end is not linked to your Natural nucleus,
NVSPARM and NVSMISCD must be linked to
NATPARM instead.
Add the corresponding sublibrary for Natural for VSAM to the search chain for the linkage editor and link-edit the executable module.
Link the executable batch Natural nucleus.
Use the Natural system command INPL to load the Natural system programs
(dataset NATnnn.INPL) into the Natural
system files.
Ensure that the DLBL names specified in NATPARM (Step 8)
are specified in the INPL job, too. In addition, a path DLBL name
(dlbl-name-fdicX) must be specified for
FDIC.
Note:
If you want to install any other Software AG products that require
INPL steps, ensure that these INPL steps are adapted
according to the VSAMI061 job.
Load the Natural error messages file (dataset
NATnnn.ERRN) using the
ERRLODUS
utility (which is described in the Natural SYSERR Utility
documentation).
Ensure that the DLBL names specified in NATPARM (Step 8)
are specified in the ERRLODUS job, too.
Use the system command INPL to load the
Natural example programs (dataset
NATnnn.EXPL) and the Natural for VSAM
example programs (dataset NVSnnn.EXPL)
into the Natural system file.
Ensure that the DLBL names specified in NATPARM (Step 8)
are specified in the INPL job, too. In addition, a path DLBL name
(dlbl-name-fdicX) must be specified for
FDIC.
Reorganize the FNAT system file using the VSAM facility AMS REPRO to unload and reload the file.
This step must only be performed if you wish to install Natural for VSAM under CICS.
If Natural for VSAM is to be installed under CICS, assemble and link
the module NVSCICS.
Proceed with the specific installation steps for Natural required under your TP monitor (see the relevant sections in the Natural Installation documentation), taking into account the following additions:
Modify your Natural online parameter modules according to Step 8.
Add the following INCLUDE instructions to all links of
the online Natural nucleus:
INCLUDE NVSNUC INCLUDE NVSFNAT INCLUDE NVSFSPO INCLUDE NVSFSEC INCLUDE NVSFLOCK
The module NVSFSPO is only required if you have
Natural Advanced Facilities installed and want your spool file to be a VSAM
file, too. The online environment for Natural Advanced Facilities must be a
CICS environment, and the VSAM spool files must be defined in the CICS FCT. The
module NVSFSEC is only required if you have Natural Security
installed and want your security file to be a VSAM file, too. The VSAM security
files must be defined in the CICS FCT. The module NVSFLOCK is only
required if you want locking for source objects on VSAM system files
FUSER/FNAT. The VSAM locking files must be defined in
the CICS FCT.
Add the following INCLUDE instructions to the link of
the front-end in a CICS environment:
INCLUDE NVSPARM INCLUDE NVSCICS
Add the following INCLUDE instructions to the link of
the front-end in a Com-plete environment:
INCLUDE NVSPARM INCLUDE NVSMISCD
Add the corresponding sublibrary for Natural for VSAM to the search chain for the linkage editor and link-edit the executable module. Before starting Natural, ensure that the DLBL names of the VSAM system files are known in your batch and online environments.
| TP Monitor | Instruction |
|---|---|
| Com-plete |
Add the following DLBL statements to your Com-plete startup job: // DLBL FNAT, 'DSN=SAGLIB.VSAM.FNAT',,VSAM,CAT=xxxx // DLBL FUSER, 'DSN=SAGLIB.VSAM.FUSER',,VSAM,CAT=xxxx // DLBL FDIC, 'DSN=SAGLIB.VSAM.FDIC',,VSAM,CAT=xxxx // DLBL FDICX, 'DSN=SAGLIB.VSAM.FDIC.PATH',,VSAM,CAT=xxxx // DLBL EMPLVS, 'DSN=SAGLIB.VSAM.EMPLVS',,VSAM,CAT=xxxx // DLBL EMPLVX, 'DSN=SAGLIB.VSAM.EMPLVX.PATH',,VSAM,CAT=xxxx If Natural Security is installed, add the following DLBL statements to your Com-plete startup job: // DLBL FSEC, 'DSN=SAGLIB.VSAM.FSEC',,VSAM,CAT=xxxx // DLBL FSECA, 'DSN=SAGLIB.VSAM.FSEC.AIXA',,VSAM,CAT=xxxx // DLBL FSECB, 'DSN=SAGLIB.VSAM.FSEC.AIXB',,VSAM,CAT=xxxx // DLBL FSECC, 'DSN=SAGLIB.VSAM.FSEC.AIXC',,VSAM,CAT=xxxx If you want locking of source objects for VSAM system files
// DLBL FLOCK, 'DSN=SAGLIB.VSAM.FLOCK',,VSAM,CAT=xxxx // DLBL FLOCKA, 'DSN=SAGLIB.VSAM.FLOCK.PATHA',,VSAM,CAT=xxxx // DLBL FLOCKB, 'DSN=SAGLIB.VSAM.FLOCK.PATHB',,VSAM,CAT=xxxx // DLBL FLOCKC, 'DSN=SAGLIB.VSAM.FLOCK.PATHC',,VSAM,CAT=xxxx If you have specified |
| CICS | Add the following entries to your FCT:
Refer to the job VSAMI005 for examples. You can add DLBL statements for these datasets to your CICS startup job, too. |
To verify whether the installation has been successfully performed, log
on to the library SYSEXNVS and run the following programs:
NVSINST1
NVSINST2
NVSINST3
NVSINST4
NVSINST5
NVSINST6
If all these programs can be executed successfully, the installation of Natural on VSAM system files is completed and verified.
Note for z/OS batch mode:
For verification in batch mode under z/OS, you can run the job
VSAMI200 which executes the above programs.
The Natural VSAM system files FSEC and FSPOOL
cannot be used for record-level sharing (RLS), as the related AIX files cannot
be accessed using a path definition. The reason is that null values are not
suppressed during VSAM upgrade handling for AIX keys. The record length of AIX
files related to FSEC and FSPOOL would be exceeded
for AIX keys filled with blanks or binary zeros. This would cause problems
under CICS, as the record length supported is limited to 32 KB only. Natural
for VSAM supports null-value suppression for AIX keys and the upgrade handling
for AIX files.