This document covers the following topics:
See also Administration of Broker Stubs under z/VM.
| Component | Prerequisites |
|---|---|
| Broker Stubs |
|
| Data Set | Description |
|---|---|
| EXXvrs.TAPE | CMS installation data set: TAPE DUMP format and must be loaded onto the installation mini-disk |
| EXBvrs.INPL | Contains Natural-based tutorial for use with Entire Broker. |
| EXBvrs.ERRN | Error messages for tutorial. |
Note:
In the table above, vrs represents the
version, release and service pack. Make sure you install the
highest patch level available.
This section comprises the following steps:
We recommend that you keep the EntireX Broker environment in a z/VM disk
named EXXvrs. To position the tape for the
TAPE LOAD command, calculate the number of tape
marks as follows: If the sequence number of
EXXvrs.TAPE, as shown by the Software AG Product Delivery Report, is n, you must position over
3n-2 marks (that is FSF 1 if it's the first data
set, FSF 4 if it's the second, etc.).
Access the disk that is to contain the EntireX files as disk A.
Ask the system operator to attach a tape on drive to your virtual machine on address 181 and mount the installation tape.
Position the tape, to tape mark n as
calculated above, by issuing TAPE FSF
n.
Load the tape contents by issuing TAPE LOAD * * A.
This requires Adabas and Natural environments in your z/VM environment to be available.
Use the INPL system command (described in Natural reference documentation) to load SYSETB objects.
Set the Natural profile parameter ESIZE=64.
Load the tutorial error messages using the Natural system utility ERRLODUS.
This step links ADAENTRY against the Adabas link module ADALNK and is needed only if you are going to use the transport mechanism NET to communicate between z/VM and a Broker kernel executing on another mainframe. This step requires Adabas to be already installed in your z/VM environment and for your Adabas text library to be available.
LOAD ETBADUSR (RLDSAVE RESET ETBADUSR) GENMOD ADAENTRY (AMODE 31 RMODE ANY)
This step is needed only if your Broker kernel is running under EntireX Security and if the application is using ACI version 7 or below.
This package contains the Natural tutorial SYSETB and the C test programs BCOS BCOC. Either of these provided applications can be used for installation verification. Prerequisite for installation verification is a running remote Broker kernel. To proceed, you need to know the IP address and port number of your Broker kernel for TCP/IP communications, or the Entire Net-Work Broker ID if using Adabas / Entire Net-Work transport.
To execute Natural and load the Broker stub dynamically
Enter the following command:
NAT42 RCA=BROKER,RCALIAS=(BROKER,BKIMBCMS),ESIZE=64,STACK=(LOGON SYSETB)
BCOS and BCOC are Language Environment programs provided in C source and also in MODULE format. The modules can be executed without rebuilding them (REXX script MAKEBCO is provided if you do want to rebuild these programs).
Logon to z/VM with two sessions.
Check you have access to the EXXvrs disk where EntireX was installed.
In session 1, execute the following on the z/VM command line:
bcoc ENVAR(ETB_STUBLOG=1)/-b<ip-address>:<port-number>:TCP -i10
In session 2, execute the following on the z/VM command line:
bcos ENVAR(ETB_STUBLOG=1)/-b<ip-address>:<port-number>:TCP -i10
With Broker kernel API version 9, the screen output of BCOC will look similar to this:
CLIENT: ETB Version 9 CLIENT: Number of repeats (10) CLIENT: Broker ID <ip-address>:<port-number> CLIENT: Using default class ACLASS CLIENT: Using default server ASERVER CLIENT: Using default service ASERVICE CLIENT: Maximum stub ACI version: 9 CLIENT: Maximum kernel ACI version: 9 CLIENT: Kernel Version 8.0.0.00 Platform z/OS CLIENT: Using ACI version: 9 Request issued (9, 2037) Request issued (8, 2037) Request issued (7, 2037) Request issued (6, 2037) Request issued (5, 2037) Request issued (4, 2037) Request issued (3, 2037) Request issued (2, 2037) Request issued (1, 2037) Request issued (0, 2037) CLIENT: Test successfully performed Press ENTER to end terminal session.
The screen output of BCOS will look similar to this:
SERVER: ACI Version 9 SERVER: Number of repeats (10) SERVER: Broker ID <ip-address>:<port-number> SERVER: Using default class ACLASS SERVER: Using default server ASERVER SERVER: Using default service ASERVICE SERVER: Maximum stub ACI version: 9 SERVER: Maximum kernel ACI version: 9 SERVER: Kernel Version 8.0.0.00 Platform UNIX SERVER: Using ACI version: 9 Incoming data (2037, 9) Incoming data (2037, 8) Incoming data (2037, 7) Incoming data (2037, 6) Incoming data (2037, 5) Incoming data (2037, 4) Incoming data (2037, 3) Incoming data (2037, 2) Incoming data (2037, 1) Incoming data (2037, 0) SERVER: Test successfully performed Press ENTER to end terminal session.
If this is the case, the test with the remote Broker was successful.
You can link the Broker stub BKIMBCMS with the Natural nucleus or load it dynamically using the following parameter at Natural startup:
NAT42 RCA=BROKER,RCALIAS=(BROKER,BKIMBCMS)
You must not link the Broker stub into the Natural nucleus if it is intended to execute this in a shared segment.
Link your application with the Broker stub BKIMBCMS.
