This document covers the following topics:

• Broker Stubs under z/OS with Natural

• Broker Stubs under z/VSE with Natural

• Broker Stubs under BS2000 with Natural

• Verifying the Installation of the Broker Stub under Natural

---

Broker Stubs under z/OS with Natural

For using the Broker stubs with Natural in a batch or CICS environment, the stub module BKIMBTSO or CICSETB respectively is loaded dynamically. The Broker stubs require the IBM Language Environment runtime library to be installed.

BKIMBTSO for Natural in z/OS Batch and TSO

1. Add the EntireX load library (EXXvrs.LOAD) to your STEPLIB concatenation when running the Natural RPC server.

2. Start the Natural RPC server with the following profile parameters:

   RCA=(BROKER),RCALIAS=(BROKER,BKIMBTSO)

   For example:

   //STEP EXEC PGM=NATBATvs,PARM=('RCA=(BROKER),RCALIAS=(BROKER,BKIMBTSO)')

   This will dynamically load BKIMBTSO and each Broker call will use this stub. Loading the broker stub BKIMBTSO dynamically will work even if NATETB23 has already been statically linked to Natural. You do not need to link the Broker stub BKIMBTSO statically to Natural.

CICSETB for Natural in CICS

1. Add the following definition to the CICS CSD cluster:

   * ------------------------------------------------------------------ *
   * CSD Definition for Broker Stubs 
   * ------------------------------------------------------------------ *
     DEFINE PROGRAM(CICSETB) GROUP(EXX) 
       DESCRIPTION(CICS NETWORK BROKER STUB) 
       LANGUAGE(ASSEMBLER)
                                                                         
     DEFINE PROGRAM(CICSETB2) GROUP(EXX) 
       DESCRIPTION(CICS TCP BROKER STUB) 
       LANGUAGE(LE370)
                                                                         
     DEFINE PROGRAM(EXAGLUE) GROUP(EXX) 
       DESCRIPTION(CICS GLUE PGM FOR TCP STUB) 
       LANGUAGE(LE370) 
   
   DEFINE PROGRAM(EXAMEM) GROUP(EXX) 
     DESCRIPTION(CICS STUB SESSION HANDLER) 
     LANGUAGE(ASSEMBLER)

2. Add the EntireX load library (EXXvrs.LOAD) to both the DFHRPL chain and the STEPLIB chain of the CICS started tasks JCL.

3. Start the Natural RPC server task with the following profile parameters:

   RCA=(BROKER),RCALIAS=(BROKER,CICSETB)

   For example:

   N426 RCA=(BROKER),RCALIAS=(BROKER,CICSETB)

   This will dynamically load CICSETB and each Broker call will use this stub.

Broker Stubs under z/VSE with Natural

For using the Broker stubs with Natural in a batch or CICS environment, the stub module BKIMB or BKIMC respectively is loaded dynamically. The Broker stubs require the IBM Language Environment to be installed.

BKIMB for Natural in z/VSE Batch

1. Include the EntireX sublibrary (EXXvrs) into the LIBDEF search chain when running the Natural RPC server.

2. Start the Natural RPC server with the following profile parameters:

   RCA=(BROKER),RCALIAS=(BROKER,BKIMB)

BKIMC for Natural in z/VSE CICS

1. To enable CICS to find the various programs, include the EntireX sublibrary (EXXvrs) into the CICS LIBDEF search chain and add following definitions to your CICS CSD file:

   DEFINE PROGRAM(BKIMC) GROUP(EXX) DESCRIPTION(ENTIREX BROKER STUB INTERFACE) LANGUAGE(ASSEMBLER)
   DEFINE PROGRAM(BROKERC) GROUP(EXX) DESCRIPTION(ENTIREX BROKER STUB) LANGUAGE(C)

2. Start the Natural RPC server with the following profile parameters:

   RCA=(BROKER),RCALIAS=(BROKER,BKIMC)

   For example:

   N426 RCA=(BROKER),RCALIAS=(BROKER,BKIMC)

   This will dynamically load BKIMC and each Broker call will use this stub.

Broker Stubs under BS2000 with Natural

For using the Broker stubs with Natural in a batch or TIAM environment, the stub module BROKER is loaded dynamically.

1. Add the following assignments to the Natural startup procedure:

   /ADD-FILE-LINK LINK-NAME=BLSLIB00,FILE-NAME=<EXXvrs.LIB>
   /ADD-FILE-LINK LINK-NAME=ETBLIB,FILE-NAME=<EXXvrs.LIB>

2. Start the Natural RPC server with the following profile parameters:

   RCA=(BROKER),RCALIAS=(BROKER,BROKER)

Verifying the Installation of the Broker Stub under Natural

1. Log on to the Natural library SYSRPC and enter MENU.

2. Invoke Service Directory Maintenance (SM) from the main menu.

3. Define the node and server, and save your changes.

4. Invoke Server Command Execution (XC) from the main menu for the node and server defined in the previous step.

5. Ping the server with the command PI.

   Your environment and the Broker stub are installed correctly if you receive one of the following:

   • An answer from the RPC server.

   • 00070007 Service not registered, meaning that the broker is up but the RPC server is down.

   • 02150148 Connection error, meaning that the broker and the RPC server are down.