Version 9.6
 —  EntireX z/VSE Batch RPC Server  —

Introduction to the Batch RPC Server

The EntireX z/VSE Batch RPC Server allows standard RPC clients to communicate with RPC servers on the operating system z/VSE under Batch. It supports the programming language COBOL and works together with the COBOL Wrapper and IDL Extractor for COBOL. This document covers the following topics:


Worker Models

graphics/intro_workerModels-bavs.png

RPC requests are worked off inside the RPC server in worker threads, which are controlled by a main thread. Every RPC request occupies during its processing a worker thread. If you are using RPC conversations, each RPC conversation requires its own thread during the lifetime of the conversation. The Batch RPC Server provides two worker models:

See parameter workermodel under Configuring the RPC Server.

Top of page

Inbuilt Services

The Batch RPC Server provides the following services for ease-of-use:

Deployment Service

The Deployment Service allows you to deploy server mapping files (SVM files) interactively using the Deployment Wizard (see Server Mapping Deployment). On the RPC server side, the SVM files are stored in a VSAM file as the container. See Deployment Service for configuration information.

graphics/intro_inbuilt_deployment-bavs.png

SMH Listener Service

With the SMH Listener Service you use the System Management Hub to monitor the RPC server. See Administering the EntireX RPC Servers using System Management Hub under UNIX | Windows.

The SMH Service is switched on if the parameter smhport is set. See parameter smhport under Configuring the RPC Server.

graphics/intro_inbuilt_smh-bavs.png

Top of page

Usage of SVM Files

There are many situations where the Batch RPC Server requires a server mapping file to correctly support special COBOL syntax such as JUSTIFIED, SYNCHRONIZE and OCCURS DEPENDING ON clauses, LEVEL-88 fields, etc. the .

SVM files contain COBOL-specific mapping information that is not included in the IDL file and therefore not sent by an EntireX RPC client to the RPC server. See also When is an SVM File Required? under SVM Files.

graphics/intro_useSvm.png

The RPC server marshalls the data in a two-step process: the RPC request coming from the RPC client (Step 1) is completed with COBOL-specific mapping information taken from the SVM file (Step 2). In this way the COBOL server can be called as expected.

The SVM files are retrieved as a result of the IDL Extractor for COBOL extraction process and the COBOL Wrapper if a COBOL server is generated.

You can customize the usage of the SVM file using parameter svm. See Configuring the RPC Server.

Note:
SVM files are used for COBOL only.

Top of page