EntireX	Version 9.7	SEARCH   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

This document covers the following topics:

• The RPC Communication Area (Reference)

• Generic RPC Services Modules

The RPC Communication Area (Reference)

The RPC communication area is used to specify parameters that are needed to communicate with the broker and are not specific to client interface objects. These are, for example, the Broker ID, client parameters such as user ID, password and the server address such as class/servername/service etc. See the table below for a complete listing.

Notes:

1. See below the table for an explanation of column headings.
2. The RPC communication area is provided with the generated copybook ERXCOMM in the folder include for RPC client generation. See Generating COBOL Source Files from Software AG IDL Files.
3. See section Using the RPC Communication Area for the usage of the RPC communication area.

RPC Communication Area field

Name of the filed in the RPC communication area.

Explanation

Explanation of the purpose of the field.

Req/Opt/Auto

Indicates for input fields whether they have to be given by the RPC application (required) or may be given by the user (optional). Fields marked with "Auto" are managed internally by the Generic RPC Services Modules themselves.

In/Out

Indicates whether the field is an input field (to be given by the RPC application) or an output field (returned to your RPC application).

Notes:

1. See Using Broker Logon and Logoff.
2. Optional if broker does not require security, required if broker is secured.
3. RPC conversations are supported when communicating with an RPC server. For more information, see Using Conversational RPC.
4. Natural Security is only relevant if communicating with a Natural RPC server. See Using the COBOL Wrapper with Natural Security and Impersonation.
5. See Reliable RPC for COBOL Wrapper.
6. Field is managed internally by the Generic RPC Services Modules themselves. For these to work properly you need to initialize the RPC Communication Area before using it in your RPC client application. See Step 1: Declare and Initialize the RPC Communication Area. Do not change this field in your RPC client application.

Generic RPC Services Modules

This section covers the following topics:

• Introduction

• Generic RPC Services Modules Usage

• Delivered Modules for z/OS

• Delivered Modules for z/VSE

• Delivered Modules for BS2000/OSD

• Delivered Modules for IBM i

• Adapting the Used Broker Stub

Introduction

The generic RPC services module COBSRVI is required for RPC clients.

• It can be optionally generated during RPC client generation in the folder client in the container folder. Section Generate Generic RPC Service for Module COBSRVI under Generating COBOL Source Files from Software AG IDL Files explains how to generate the RPC service module COBSRVI.

• It contains functions needed for RPC communication where a client interface object(s) is not needed. Refer to the functions documented with the RPC communication area field COMM-FUNCTION under The RPC Communication Area (Reference) for a list of provided functions.

• It manages internal states held inside the RPC communication area for conversational RPC, reliable RPC etc. See The RPC Communication Area (Reference).

• From a COBOL programmer's point of view, it is always called with the COBOL program name COBSRVI, even for the delivered mainframe sources COBSRVIB, COBSRVIC and COBSRVID.

• It contains the call to the broker stub.

Generic RPC Services Modules Usage

The delivered modules on mainframe platforms are mainly for a quick demonstration of the delivered examples. The best approach is to use the modules generated by the EntireX Workbench, for the following reasons:

• The modules delivered on mainframe platforms may be out-of-date.

• You can set generation options, for example String Literal (see Characters Used for String Literals), individually as required.

Delivered Modules for z/OS

Module

Name of the delivered module.

vrs

Version, release and service pack.

EXP970.INCL

Generic RPC include data set. The generic RPC include data set may be delivered as a patch with a different name EXP970.INnn, where nn is the patch level number. Make sure you install the highest patch level available. The data set is required to SYSLIB input for the COBOL compiler.

EXP970.SRCE

Generic RPC source data set. The generic RPC source data set may be delivered as a patch with a different name EXP970.S0nn, where nn is the patch level number. Make sure you install the highest patch level available. The data set is required to SYSLIB input for the COBOL compiler.

Notes:

1. See The RPC Communication Area (Reference).
2. See Generic RPC Services Modules Usage.
3. See Aborting RPC Server Customer Code and Returning Error to RPC Client (z/OS | z/VSE) in the CICS RPC Server documentation.

Delivered Modules for z/VSE

File

Name of the delivered file.

Sublibrary

Name of the delivered sublibrary.

Description

Purpose of the file.

Notes:

1. See The RPC Communication Area (Reference).
2. See Generic RPC Services Modules Usage.
3. We recommend you use module COBSRVI generated by the EntireX Workbench instead of the modules COBSRVIB, COBSRVIC and COBSRVID delivered with your z/VSE installation. The reason for this is that the EntireX Workbench is updated much more frequently. Section Generate Generic RPC Service for Module COBSRVI under Generating COBOL Source Files from Software AG IDL Files explains how to generate the RPC service module.

Delivered Modules for BS2000/OSD

Notes:

1. See The RPC Communication Area (Reference).
2. See Generic RPC Services Modules Usage
3. We recommend you use module COBSRVI generated by the EntireX Workbench instead of the delivered module. The reason for this is that the EntireX Workbench is updated much more frequently. Section Generate Generic RPC Service for Module COBSRVI under Generating COBOL Source Files from Software AG IDL Files explains how to generate the RPC service module.

Delivered Modules for IBM i

Notes:

1. See The RPC Communication Area (Reference).
2. See Generic RPC Services Modules Usage
3. Do not use module RPCSRVI delivered with your IBM i installation. It does not support all the features described here, for example reliable RPC. Use module COBSRVI generated by the EntireX Workbench instead. Section Generate Generic RPC Service for Module COBSRVI under Generating COBOL Source Files from Software AG IDL Files explains how to generate the RPC service module.

Adapting the Used Broker Stub

Because multiple broker stubs may be offered per operating system and environments, it may be necessary to adapt the COBSRVI module to the correct broker stub that supports the required transport (TCP, SSL, NET). To do this, modify the COBOL subprogram DOBROKER inside the COBSRVI source file with a broker stub that meets your requirements.

For availability and information on broker stubs, see Administration of Broker Stubs under z/OS | UNIX | Windows | BS2000/OSD | IBM i.

Caution:
Do not make any modifications other than changing the broker stub name, and do not modify the COBOL subprogram COBSRVI inside the same COBSRVI program source. Unexpected behavior will occur.

www.softwareag.com

Copyright © 1997-2014 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT