Configuring CICS to execute rules on zRule Execution Server for z/OS

After you configure a zRule Execution Server for z/OS server group, you can optionally configure CICS® to execute rules on a server instance.

Before you begin

Verify that you meet the following prerequisites:

You configured a zRule Execution Server for z/OS server group as described in Configuring topology 1: zRule Execution Server group with a shared console.

You configured a CICS environment by adding the CICS control statement to HBRCTRL. For example:

CREATE CICS HBRWORKDS=RULES.WORK.REGION1 CICSHLQ=CTS320.CICS650 CICSCSDDSN=CTS320.REGION2.DFHCSD

In Step 3: Customizing the z/OS configuration and runtime variables, you have customized the CICS related JCL variables that are listed in Configuration variables for configuring CICS to execute rules on a zRule Execution Server for z/OS instance.

See Step 2: Choosing your topology for information about topology configuration options.

About this task

Use the following procedure to configure CICS to execute rules on zRule Execution Server for z/OS.

You can optionally configure CICS to execute the HBRC transaction at startup to connect to the server instance automatically, if it is running. With this option, CICS is immediately ready to execute rules. If the server is not running, CICS starts normally but you must execute the HBRC transaction manually before rule execution can begin.

Note: This configuration is supported for CICS version 3.2 or later. If you are using CICS 5.1 or later, consider running zRule Execution Server for z/OS inside the CICS JVM server. For more information, see Configuring a CICS rule-owning region to execute rules in a CICS JVM server.

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

Procedure

Submit the ++HBRWORKDS++.SHBRJCL(HBRCSD) job to define the resources that are required by CICS.
In the CICS system initialization parameters, add the list name that is represented by ++CICSLIST++ to the list of resource definition groups that are specified by the GRPLIST parameter.
Edit the CICS JCL to include the zRule Execution Server for z/OS data sets:
1. Ensure that the ++HBRHLQ++.SHBRCICS data set is added to the DFHRPL concatenation.
2. Pass the necessary runtime variables to the server by adding the SHBRPARM(HBRCICZ) and SHBRPARM(HBRCMMN) dataset members to the HBRENVPR DD statement as shown in the following DD statements:
```
//HBRENVPR DD DISP=SHR,DSN=++HBRWORKDS++.SHBRPARM(HBRCICSZ)
//         DD DISP=SHR,DSN=++HBRWORKDS++.SHBRPARM(HBRCMMN) 
```
3. If you plan to run the Miniloan sample application to verify your configuration, add the SHBRPARM(HBRSCEN) data set member to the SCENARIO DD statement. The HBRSCEN member contains input values to the Miniloan application.
```
//SCENARIO DD DISP=SHR,DSN=++HBRWORKDS++.SHBRPARM(HBRSCEN)
```
Start the zRule Execution Server for z/OS and the Rule Execution Server console.
Start CICS and install the HBRGROUP resources by using the following command:
```
CEDA INSTALL GROUP(HBRGROUP)
```
Test the configuration by running the HBRC transaction to connect CICS to zRule Execution Server for z/OS. If CICS succeeds in connecting to the server, message GBRZC9001I is issued. If CICS fails to connect to the server, message GBRZC9000E is issued with a return code that contains diagnostic information.
Optional: To configure CICS to connect automatically at startup to the running server instance, take either of the following actions:
- If you do not have a program list table defined, add the PLTPI=HB parameter to the CICS system initialization parameters.
  For CICS 5.5 and 6.1 users, do one of the following:
  - Copy ++HBRHLQ++.SHBRCPLT(DFHPLTHB) to one of the existing PROCLIB concatenation datasets.
  - Add ++HBRHLQ++.SHBRCPLT(DFHPLTHB) to your PARMLIB concatenation.
- If you already have a program list table defined and specified in your CICS system initialization parameters, add the HBRCCON program to the list by including the following statement: DFHPLT TYPE=ENTRY,PROGRAM=HBRCCON.
Optional: You can verify your configuration by running the Miniloan sample application as a CICS application. For more information, see Sample: running the Miniloan application as a CICS application.