Verifying the z/OS Installation

Once you have installed the EntireX Broker and EntireX Developer's Kit, you can verify the installation of the following components.

EntireX Broker
Client (BCOC) and Server (BCOS)
CICS RPC Server
Batch RPC Server
IMS RPC Server

EntireX Broker

Start of instruction set To test the EntireX Broker installation

Start EntireX Broker. See Starting and Stopping the Broker in the z/OS Administration documentation.
Run the example programs:
- BCOS is the example server program
- BCOC is the example client program
See Client (BCOC) and Server (BCOS).

Client (BCOC) and Server (BCOS)

The programs BCOC and BCOS are client and server programs provided for test purposes. They are delivered as load modules in EXX912.LOAD.

The execution JCL for the example programs is located in the EXX912.JOBS library in members EXXBCOS and EXXBCOC. Modify the JCL for your installation, and submit job EXXBCOS first, followed by job EXXBCOC.

A single message will be sent by program BCOC and then received by program BCOS. Both jobs should return a zero condition code. The output from each job is written to SYSPRINT.

BCOC Parameters

Parameter	Description	ACI Field
`-alocale`	`locale_string`,`environment`	`LOCALE-STRING`, `ENVIRONMENT`
`-bbroker_id`	Broker ID (same as the database ID). This is an EntireX Broker configuration parameter. Example: `BCOC -bETB045`	`BROKER-ID`
`-cclass`	Server class (part of the server definition). Default is `ACLASS`. Value must be configured in EntireX Broker. Together with `server` and `service` it forms the fully qualified server name.	`SERVER-CLASS`
`-ginput_file_name`	Use a file as send buffer.
`-h`	Display usage information.
`-inum_messages[,num_uows]`	If `num_uows` is not specified, the number of messages sent. If `num_uows` is specified, the number of UOWs and messages therein sent. Example: `bcoc -i10`
`-l`	Silent mode. Suppress output.
`-ntoken`	Specify the security token, if desired.	`TOKEN`
`-pmessage_size`	The size, in bytes, of the packets that will be transmitted. Used to specify send and receive length in the broker API. Example: `BCOC -p10000`
`-rcompress`	Compression level. Values: `N\|Y\|0-9`.	`COMPRESSLEVEL`
`-sserver`	Name of server. Default is `ASERVER`. Value must be configured in EntireX Broker. Together with `class` and `service` it forms the fully qualified server name.	`SERVER-NAME`
`-uuser_id`	User ID. With a secure broker, this will be used to perform authentication.	`USER-ID`
`-vservice`	Name of service (part of the server definition). Default is `ASERVICE`. Value must be configured in EntireX Broker. Together with `class` and `server` it forms the fully qualified server name.	`SERVER-NAME`
`-wpassword`	Password. With a secure broker, this will be used to perform authentication.	`PASSWORD`
`-xssl_parms`	SSL parameters. For example: `-x"TRUST_STORE=C:\SoftwareAG\EntireX\etc\ExxCACert.pem&VERIFY_SERVER=NO"` See also SSL/TLS Parameters for SSL Clients.
`-1..10`	By default, if omitted, the highest possible ACI version is used. Note that if you specify the ACI version, certain features might depend on a minimum ACI version.	`API-VERSION`
`-ysleep_time`	Delay between messages in seconds.
`-twait_time`	Set the wait time.

BCOS Parameters

Most BCOC parameters apply to BCOS, too. The following table lists additional parameters or parameters that have a different meaning.

Parameter	Description	ACI Field
`-goutput-file-name`	Name of output file for receive buffer (if not running in silent mode).
`-inum_messages[,num_uows]`	If `num_uows` is not specified, the number of messages that are accepted before deregistration. If `num_uows` is specified, the number of UOWs and messages therein that are accepted before deregistration. Example: `bcos -i10`

CICS RPC Server

The installation can be verified by running an example program provided for z/OS. The delivered COBOL and PL/I examples need to be installed separately (either COBOL or PL/I examples). See Extracting the EntireX RPC Examples from their Container Data Set.

Batch RPC Server

The installation can be verified by running an example program provided for z/OS. The delivered COBOL and PL/I examples need to be installed separately (either COBOL or PL/I examples or both). See Extracting the EntireX RPC Examples from their Container Data Set.

IMS RPC Server

The installation can be verified by running an example program provided for z/OS. The delivered COBOL and PL/I examples need to be installed separately (either COBOL or PL/I examples or both). See Extracting the EntireX RPC Examples from their Container Data Set.