Version 9.6
 —  Installing EntireX under BS2000/OSD  —

Installing the BS2000/OSD Batch RPC Server

This document covers the following topics:


Step 1: Define an RPC SVM File

The SVM file is used at runtime to marshal and unmarshal the RPC data stream. This enables the RPC server to support special COBOL syntax. This server-related information is held in an ISAM file, which needs to be defined and initialized. Each RPC server requires its own SVM file.

Customize S-procedure CREATE-SVM-FILE in EXP960.JOBS.

Procedure Parameter Description Default
EXP-LIB BS2000/OSD Batch RPC Server load library EXP960.LIB
SVM-FILE SVM file name SVMFILE
SYSOUT-FILE SYSOUT file name RPC.SYSOUT.CREASVM

The SVM file name must correspond to the SVM file specified in the BS2000/OSD Batch RPC Server startup job control. See Step 4: Customize the BS2000/OSD Batch RPC Server Startup JCL.

See also Handling SVM Files in the BS2000/OSD administration documentation.

Top of page

Step 2: Customize the BS2000/OSD Batch RPC Server Configuration File RPC-CONFIG

RPC-CONFIG in EXP960.JOBS contains the RPC server parameters. If the default settings are used, only the BROKERID parameter needs to be set up according to your environment. The BS2000/OSD Batch RPC Server will then run in a default configuration.

Depending on the communication method, the Broker ID has two formats:

If the provided parameter file is used, the RPC server will run as a COBOL server. Besides the RPC service (RPC/SRV1/CALLNAT), it will register the DEPLOYMENT and the EXTRACTOR service. This corresponds to the delivered settings in the broker attribute file on BS2000/OSD and other platforms. The server is configured to run with a fixed number of 3 worker task replicates. System Management Hub support and security are turned off.

See also Configuring the RPC Server.

The default configuration file RPC-CONFIG:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*                                                                     *
*            EntireX RPC Server v8.1 Configuration File               *
*                                                                     *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
* * * * * * * * * * EntireX Broker Parameters * * * * * * * * * * * * *
*
BROKERID=<ipaddr>:<port>:TCP                Broker Id if TCPIP is used
* BROKERID=ETB<nnnnn>::NET                  Broker Id if NET is used
*
SERVERNAME=SRV1
SERVICE=CALLNAT
CLASS=RPC
*
TIMEOUT=300                                 Seconds
LOGON=YES                                   EntireX Broker Logon
*
* CODEPAGE=EDF041
*
* KERNELSECURITY=YES                        EntireX Broker Security
* USERID=<userid>
* PASSWORD=<password>
*
*
* * * * * * * * * * EntireX RPC Server Parameter  * * * * * * * * * * *
*
RESTARTCYCLES=3                             default is 15
* TRACELEVEL=NONE                           NONE, STANDARD or ADVANCED
* SMHPOPT=<smhport>
*
* EntireX RPC Cobol Server Configuration
* ---------------------------------------------------------------------
SVM=PREFERRED
DEPLOYMENT=YES
EXTRACTOR=YES
MARSHALLING=(LANGUAGE=COBOL)
*
* EntireX RPC C Server Configuration
* ---------------------------------------------------------------------
* EXTRACTOR=YES
* MARSHALLING=(LANGUAGE=C)
*
* Start up a fixed number of workers
* ---------------------------------------------------------------------
WORKERMODEL=(FIX,3)
*
* Balance the load of available workers
* ---------------------------------------------------------------------
* WORKERMODEL=(SCALE,2,5)
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Top of page

Step 3: Customize ADALNK Parameter File RPC-ADAPARM

The BS2000/OSD Batch RPC Server requires ADALNK parameters when a local communication with an EntireX Broker on same machine is desired (XCOM communication). Set up the IDTNAME in RPC-ADAPARM in EXP960.JOBS under which the broker has registered at the Adabas ID table.

Parameter Description
ADALNK IDTNAME=ADA<xxxxx> Specifies the ID table name under which EntireX Broker is accessible.

Top of page

Step 4: Customize the BS2000/OSD Batch RPC Server Startup JCL

The job control delivered with BS2000/OSD Batch RPC Server makes use of BS2000/OSD S-procedures. We strongly recommend you do not modify START-RPC-SERVER. This procedure is recursively called to establish the RPC server environment. Modifications should only be done to the PARAMETER-DECLARATION section as described below. If all RPC server components are installed under the same BS2000/OSD user ID and all previous installation steps have been done using the default settings, no modifications to START-RPC-SERVER are necessary to run a COBOL server and execute the delivered examples.

Procedure Parameter Description Default
EXP-JOBS Batch RPC Server jobs library. EXP960.JOBS
EXP-LIB Batch RPC Server load library. EXP960.LIB
EXX-LIB EntireX Broker load library. EXX960.LIB
WAL-MOD WAL library. WAL826.MOD
PROGRAM-LIB Server module library. Additional server module libraries can be included in the BLSLIB chain. (See the SET UP FILE LINKS section in the START-RPC-SERVER job control.) There are two sample server libraries delivered:
EXP960.COBS COBOL sample server module library. See Client and Server Examples for BS2000/OSD in the COBOL Wrapper documentation.
EXP960.CSRV C sample server module library. See Server Examples for BS2000/OSD in the C Wrapper documentation.
EXP960.COBS
ADABAS-PARAMETERS Adabas parameters used for XCOM communication method. RPC-ADAPARM
RPC-CONFIG-FILE RPC configuration parameter file. RPC-CONFIG
SVM-FILE Sever mapping ISAM file name. SVMFILE
PROC-NAME The name of the START-RPC-SERVER procedure. START-RPC-SERVER
WORKER-JOB-NAME Job name of the worker tasks. RPCWORK
LOG-FILE-PREFIX
File name prefix used for the SYSOUT files of the main and worker tasks. The following SYSOUT files are generated:
for the main task: log-file-prefix.tsn.RPCMAIN
for each worker task and the SMH task: log-file-prefix.tsn.RPCWORK
RPC.
WORKER-JOB-CLASS Job class of the worker tasks *STD
WORKER-CPU-LIMIT CPU limit of the worker tasks. If this parameter is set to *NO, the user ID requires the permission to run jobs with TIME='NTL' in the job class assigned *STD
CRTE-LIB BS2000/OSD Common Runtime Environment (CRTE) library $.SYSLNK.CRTE
STUB-TRACE-LEVEL Trace level of the EntireX Broker stub. For diagnostic purposes it can be set to 1, 2 or 3 0
LOGGING The logging parameter is passed to the worker task job control and the SYSJ elements executed *NO
WORKER-PARMS Is filled during runtime with the worker task parameters. Note: Do not modify it ! *RPC
MAIN-TASK-TSN Is filled during runtime with the main task TSN. Note: Do not modify it! *RPC

Top of page

Starting the RPC Server

Start of instruction setTo start the BS2000/OSD Batch RPC Server

Top of page

Stopping the RPC Server

Start of instruction setTo stop the BS2000/OSD Batch RPC Server using System Management Hub

Start of instruction setTo stop the BS2000/OSD Batch RPC Server from a privileged user ID

Start of instruction setTo stop the BS2000/OSD Batch RPC Server from an operator console

Start of instruction setTo stop the BS2000/OSD Batch RPC Server from a non-privileged user ID

Top of page

Verifying the Installation of the BS2000/OSD Batch RPC Server

The BS2000/OSD Batch RPC Server is delivered with libraries that contain COBOL client sample programs, and COBOL and C server sample programs. The sample client and server programs can be used for installation verification. They also correspond to the basic and reliable RPC examples delivered with the EntireX Developer's Kit on other platforms, for example UNIX and Windows.

See Client and Server Examples for BS2000/OSD in the COBOL Wrapper documentation and Server Examples for BS2000/OSD in the C Wrapper documentation.

Top of page