Configuring a zRule Execution Server for z/OS server group

Configure a group of zRule Execution Server for z/OS® instances to execute rules for z/OS applications (COBOL or PL/I applications) running as batch jobs.

Before you begin

Before you begin, you must complete the initial configuration tasks that are described in Configuring (authorize the load library, customize the variables, decide on a topology, create the working data sets and directory, configure DB2®, and configure security).

About this task

Complete the following steps to configure a group of 1 to 32 zRule Execution Server for z/OS instances with a shared console.

For information about topology configuration options, see Step 2: Choosing your topology.

In the following procedure, the server group is defined by the ++HBRSSIDLIST++ JCL variable.

Note: If the zRule Execution Server for z/OS servers and the Rule Execution Server console are spread across different LPARs, you must configure ++HBRCONSOLECOMPORT++ and ++HBRCONSOLECOMHOST++ variables. For more information about these variables, see z/OS configuration variables.

Procedure

Define a new subsystem for each server instance to run in. The system programmer performs this task by using the following command:
```
SETSSI ADD,SUBNAME=<HBRSSID_NAME>
```
If the command completes successfully, the following message is displayed: IEFJ022I SETSSI ADD COMMAND FOR SUBSYSTEM <HBRSSID_NAME> COMPLETED SUCCESSFULLY.

Consider adding a definition to the system parameter library (parmlib) member IEFSSNxx to make this permanent. For example:
```
SUBSYS SUBNAME(<HBRSSID_NAME>)
```
Enable each server instance to run as a started task. For each server instance, copy the following data sets to the SYS1.PROCLIB data set or to a suitable equivalent. The system programmer performs this task.
1. Copy the ++HBRWORKDS++.SHBRPROC(HBRXMSTR) data set member of each server instance to SYS1.PROCLIB(<HBRSSID_NAME>MSTR).
  For example, to enable as started tasks server instances HBR1 and HBR2, copy HBR.WORKDS.HBR1.SHBRPROC(HBRXMSTR) to SYS1.PROCLIB(HBR1MSTR) and HBR.WORKDS.HBR2.SHBRPROC(HBRXMSTR) to SYS1.PROCLIB(HBR2MSTR).
2. Authorize the MSTR member for each server. Use the following commands:
```
RDEFINE STARTED <HBRSSID_NAME>MSTR.* STDATA(USER(<HBRSSID_USER>)GROUP(<HBRSSID_GROUP>))
```
```
SETR REF RACLIST(STARTED)
```
  where <HBRSSID_USER> represents the server user ID and <HBRSSID_GROUP> represents the name of the RACF® security group that is provided to you by your security administrator.
If security is enabled for a zRule Execution Server for z/OS that is running in CONSOLE, HTDS, or TEST mode, you must configure the Liberty angel process.
1. If a Liberty angel process is not already running on the LPAR where the zRule Execution Server for z/OS will run, configure and start the Liberty angel process by following the steps in Configuring the Liberty server angel process.
2. Once the angel process is configured and running. Create the necessary profiles for each zRule Execution Server for z/OS running in CONSOLE, HTDS, or TEST mode:
```
RDEFINE SERVER BBG.SECPFX.<HBRSSID_NAME> UACC(NONE)
PERMIT BBG.SECPFX.<HBRSSID_NAME> CLASS(SERVER) ACCESS(READ) ID(<HBRSSID_USER>)
SETR RACLIST(SERVER) REFR
```
```
RDEFINE APPL <HBRSSID_NAME> UACC(NONE)
PERMIT <HBRSSID_NAME> CLASS(APPL) ACCESS(READ) ID(WSGUEST)
SETR RACLIST(APPL) REFR
```

Results

For more information, see Liberty: Accessing z/OS security resources using WZSSAD