Installing EntireX under z/VSE

Support for EntireX Broker and RPC servers under z/VSE ends on 31 October 2020 for all EntireX versions (including version 9.6, the last released version on z/VSE). See Features Dropped in Version 10.7.

This document covers the following topics:

Installing Broker Security for Broker Stubs

This section describes the steps for installing EntireX Security for Broker stubs under z/VSE.

The delivered phases BKIMB.PHASE and BKIMC.PHASE are linked for use with internal security, which requires an application to use ACI version 8 or above. If you are running your application at ACI version 7 or below, the steps above are required to install EntireX Security for the Broker stubs in all environments where applications execute. These steps are not required if you are running your application at ACI version 8 or above.

Step 1: Relink the Stub Modules or your Application for Use with External Security

To enable external security, relink the stub modules BKIMB.PHASE, and BKIMC.PHASE (and your application if it does not dynamically load the stub).

Additionally include the following objects:







The following job control is delivered and may be used for relinking the various stub modules:



Additionally, a detailed description of how to link the stubs and your application can be found under Administering Broker Stubs under z/VSE.

Step 2: Rename SECUEXI0

Rename the phase SECUEXI0.PHASE in library EXX960 to SECUEXIT.PHASE.

EntireX CICS Socket Listener

Execute job CICSDEF.J in sublibrary EXP960. This will create all relevant CSD entries for the CICS Socket Listener. This job:

  • installs the load modules EXXRFEC, EXXRFECX, EXXRFECU, EXXRFECA and EXXRFECS

  • creates the following CICS CSD definitions:

    • program definitions for the load modules EXXRFEC, EXXRFECX, EXXRFECU, EXXRFECA and EXXRFECS, where definition for EXXRFECS needs EXECKEY(CICS)

    • transaction XRFE, which is the standard transaction name that can be maintained with the RPC Server or Adapter configuration. If you need to change this CSD entry default, you also need to adapt the configuration parameter CICS transaction ID. More information:

Start of instruction setTo run the CICS programs in a separate user transaction

  1. Define your user transaction ID in the RPC Server for CICS Socket Listener, for example:

    For more information see Configuring the CICS Socket Listener Side in the RPC Server for CICS Socket Listener documentation.

  2. Create the CSD for the user transaction ID.

  3. In this CSD definition, specify EXXRFECU for the PROGRAM attribute. To define, for example, UTSK as user transaction ID, use the following commands:

    DESCRIPTION(CICS Socket Listener user transaction)