Version 4.2.6 for Mainframes
 —  Installation  —

Installing the Natural CICS Interface

This document describes how to install the Natural CICS Interface (product code NCI).

The following topics are covered:

Warning:
Before starting the installation procedure of Natural under CICS, you should have read the section concerning the system control mechanism, see System Control under CICS in the Natural TP Monitor Interfaces documentation.

See also Natural under CICS in the Natural TP Monitor Interfaces documentation for information on the following topics:

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.


Prerequisites

The following software must be installed and running before you install the Natural CICS Interface:

Top of page

Installation Tape for the Natural CICS Interface

Installation Tape - z/OS Systems

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
NCIvrs.LOAD CICS-dependent load modules
NCIvrs.OBJS CICS-dependent object modules.
NCIvrs.SRCE CICS-dependent source programs and macros

Copying the Tape Contents to a z/OS Disk

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:

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.

Step 1 - Copy Dataset COPY.JOB from Tape to Disk

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

Step 2 - Modify COPY.JOB on Your Disk

Modify the COPY.JOB on your disk to conform to your local naming conventions and set the disk space parameters before submitting this job:

Step 3 - Submit COPY.JOB

Submit COPY.JOB to unload all other datasets from the tape to your disk.

Installation Tape - z/VSE Systems

The installation tape contains the dataset listed below. The sequence of the datasets on tape is shown in the Report of Tape Creation which accompanies the installation tape.

Dataset Name Contents
NCIvrs.LIBR Natural CICS interface installation libraries

Copying the Tape Contents to a z/VSE Disk

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:

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.

Step 1 - Copy Dataset COPYTAPE.JOB from Tape to Disk

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

Step 2 - Modify COPYTAPE.JOB

Modify COPYTAPE.JOB to conform to your local naming conventions and set the disk space parameters before submitting this job.

Step 3 - Submit COPYTAPE.JOB

Submit COPYTAPE.JOB to unload all other datasets from the tape to your disk.

Top of page

Naming Conventions for the Natural CICS Interface

The following naming conventions apply for Natural under CICS:

ncip A common system prefix of 1 to 5 characters; for example, NCI42. This prefix is determined by the value of the parameter PREFIX in the Natural CICS interface parameter module; see also the corresponding step of the Installation Procedure described below. It is followed by specific characters to make up the names of the following objects:
ncipCB Natural CICS interface system directory; for example, NCI42CB.
ncipR1 to ncipR9 Natural CICS interface VSAM RRDS roll files (optional).
ncipXFA Natural CICS interface 3270 Bridge XFAINTU exit.

Top of page

Installation Procedure for the Natural CICS Interface

This section describes the actual installation steps.

When link-editing the Natural nucleus or its subcomponents, you may receive IEW2646I or IEW2660W messages, which can be ignored.

Step 1: Allocate the VSAM RRDS Roll Files for Natural (optional)

Step 2: Assemble the Roll-File Initialization Module (optional)

Step 3: Create the Natural CICS Interface Parameter Module

Step 4: Assemble the Natural CICS Interface Starter Module NCISTART

Step 5: Assemble the Natural CICS Interface Root Module NCIROOT

Step 6: Create the System Directory

Step 7: Assemble the Natural CICS Interface External CALLNAT Interface Module (optional)

Step 8: Assemble the Natural CICS Interface NEP Interface Module (optional)

Step 9: Assemble the Natural CICS Interface XFAINTU Exit (optional)

Step 10: Assemble the Natural CICS Front-End Driver NCISFED (optional)

Step 11: Create the Natural Parameter Module

Step 12: Link the Natural CICS Interface Nucleus

Step 13: Link the Natural System Directory

Step 14: Link the VSAM Roll-File Initialization Module (optional)

Step 15: Link the Natural CICS Interface External CALLNAT Interface Module (optional)

Step 16: Link the Natural CICS Interface NEP Interface Module (optional)

Step 17: Link the Natural CICS Interface XFAINTU Exit (optional)

Step 18: Link the Natural CICS RPC Server Front-End (optional)

Step 19: Initialize the VSAM Roll Files (optional)

Step 20: Customize CICS

Top of page

Installation Verification

  1. Enter CICS from a user's terminal and type in the Natural transaction code.

  2. Proceed with the steps described in the section Installation Verification for the TP Monitor Interface.

Top of page