Version 4.2.6 for Mainframes
 —  Database Management System Interfaces  —

Installing the Natural SQL Gateway Server under z/OS

This document describes how to install a server for the Natural SQL Gateway (product code NSB) under the operating system z/OS.

The installation of the Natural SQL Gateway server is performed by installation jobs. The sample jobs are contained in the dataset NSBvrs.JOBS and are prefixed with NSB, or generated by System Maintenance Aid (SMA).

The following topics are covered:


Prerequisites

For details, refer to Prerequisites in the section Installing Natural SQL Gateway.

Top of page

Content of the NSB Server Distribution Tape

The installation tape contains the datasets listed in the table below. The sequence of the datasets and the number of library blocks needed are shown in the Report of Tape Creation which accompanies the installation tape.

Dataset Name Contents
NSBvrs.OBJS Contains the object modules of the server.
NSBvrs.JOBS Example installation jobs.

The notation vrs in dataset names represents the version, release and system maintenance level of the product.

Top of page

Installation Procedure

Step 1: Allocate the Natural SQL Gateway server LOAD library

(Job I008, Step 9510)

Step 2: Create a Natural SQL Gateway server configuration file and sample Clist

(Job I009 / Step 9510, 9520, 9530)

Step 9510 creates the NSBCONFG sample member for the batch server.

Step 9520 creates a Clist sample member to ping and terminate a Natural SQL Gateway server.

Step 9530 creates a sample member with a batch job to ping and terminate a Natural SQL Gateway server.

The following parameters of the configuration file have to be defined. See Configuring the Natural SQL Gateway Server. For the other parameters, the default values may be used:

FRONTEND_NAME Specify the name of the Natural SQL Gateway server front-end module you will generate in one of the following steps.
PORT_NUMBER Specify the TCP/IP port number under which the server can be connected.

Step 3: Link the object modules into the NSB load library

(Job I054, Step 9510)

The NSB object modules must be linked with the necessary runtime extensions of your batch installations into executable load modules.

See sample job NSBI054 on dataset NSBvrs.JOBS.

Step 4: Create server startup JCL

(Job I200, Step 9515)

Described in the section Configuring the Natural SQL Gateway Server. See sample member NSBSTART on dataset NSBvrs.JOBS.

Step 9515 creates a startup procedure for the batch server.

Sample:

//         PROC SRV=SAGNSB
//NSB      EXEC PGM=NATRNSV, 
// REGION=4000K,TIME=1440,PARM='POSIX(ON),TRAP(ON,NOSPIE)/&SRV' 
//STEPLIB  DD   DISP=SHR,DSN=NSBvrs.LOAD
//         DD   DISP=SHR,DSN=SMA.LOAD 
//SYSUDUMP DD   SYSOUT=X 
//CEEDUMP  DD   SYSOUT=X 
//CMPRINT  DD   SYSOUT=X 
//STGCONFG DD   DISP=SHR, 
//              DSN=NSB.CONFIG(&SRV) 
//STGTRACE DD   SYSOUT=X 
//STGSTDO  DD   SYSOUT=X 
//STGSTDE  DD   SYSOUT=X 
//SYSOUT   DD   SYSOUT=X

Note:
The Natural SQL Gateway server account must be defined in the z/OS UNIX System Services (OE segment). If the server account is not defined, the server ends with U4093 and system message CEE5101C in the trace file.

Top of page