Note:
Support for EntireX Broker and RPC servers under z/VSE ended 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:
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.
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:
ETBUEVA
ETBUPRE
ETBVPRE
ETBVEVA
ETBENC
ETBTP
The following job control is delivered and may be used for relinking the various stub modules:
BKIMB.J
BKIMC.J
Additionally, a detailed description of how to link the stubs and your application can be found under Administering Broker Stubs under z/VSE.
Rename the phase SECUEXI0.PHASE
in library EXX960 to SECUEXIT.PHASE
.
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:
if you are using the EntireX Adapter, see Connection Parameters for CICS Socket Listener Connections
if you are using the RPC Server for CICS Socket Listener, see Configuring an RPC Server Instance > CICS using the Command Central GUI | Command Line
To run the CICS programs in a separate user transaction
Define your user transaction ID in the RPC Server for CICS Socket Listener, for example:
cics.sl.user.transaction.id=UTSK
For more information see Configuring the CICS Socket Listener Side in the RPC Server for CICS Socket Listener documentation.
Create the CSD for the user transaction ID.
In this CSD definition, specify EXXRFECU
for the PROGRAM
attribute.
To define, for example, UTSK
as user transaction ID, use the following commands:
DEFINE TRANSACTION(UTSK) GROUP(...) DESCRIPTION(CICS Socket Listener user transaction) PROGRAM(EXXRFECU)