Verifying the z/OS Installation

Once you have installed EntireX, you can verify the installation of the following components.

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

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 Sample Programs for Client (BCOC) and Server (BCOS).

Sample Programs for 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 EXX107.LOAD.

The execution JCL for the example programs is located in the EXX107.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 the Broker Attributes. 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`
`-jreply_error`	Test `REPLY-ERROR.`
`-kconversation_flag`	Using conversational mode.
`-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 Broker Attributes. Together with `class` and `service` it forms the fully qualified server name.	`SERVER-NAME`
`-twait_time`	Set the wait time.	`WAIT`
`-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). The default is `ASERVICE`. Value must be configured in Broker Attributes. 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`
`-ysleep_time`	Delay between messages in seconds.
`-zstore[uwstatp[,uowtime]]`	Test unit of work.
`-1..12`	By default, if omitted, the highest possible API version is used. Note that if you specify the API version, certain features might depend on a minimum API version.	`API-VERSION`

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 accepted. If `num_uows` is specified, the number of UOWs and messages therein that are accepted before deregistration. Example: `bcos -i10`
`-iunit_of_work_flag`	Test unit of work.

RPC Server for CICS

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 Installing RPC Examples for z/OS.