Configuring CICS to run rules through WOLA

After you configure a Rule Execution Server on WebSphere® Application Server for z/OS® instance, you can configure CICS® to run rules on the newly configured server through WOLA.

About this task

Use the following procedure to configure CICS to run rules on Rule Execution Server on WebSphere Application Server for z/OS through WOLA.

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

Procedure

  1. Submit the ++HBRWORKDS++.SHBRJCL(HBRCSD) job to define the resources that are necessary for CICS.
  2. Submit the ++HBRWORKDS++.SHBRJCL(HBRCSDW) job to define the resources that are necessary for WOLA under CICS.
  3. In the CICS system initialization parameters, add the list names BBOLIST and ++CICSLIST++ to the list of resource definition groups that are specified by the GRPLIST parameter.
  4. Edit the CICS JCL to include the Rule Execution Server data sets:
    1. Add the ++HBRHLQ++.SHBRCICS and the ++HBRWOLALOADLIB++ libraries to the DFHRPL concatenation.
    2. Pass the necessary runtime variables to the server by adding the SHBRPARM(HBRWOLA) and SHBRPARM(HBRCMMN) data set members to the HBRENVPR DD statement. These variables are shown in the following DD statements:
      //HBRENVPR DD DISP=SHR,DSN=++HBRWORKDS++.SHBRPARM(HBRWOLA)
      //         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 as a SCENARIO DD statement. The HBRSCEN member contains input values to the Miniloan application.
      //SCENARIO DD DISP=SHR,DSN=++HBRWORKDS++.SHBRPARM(HBRSCEN)
  5. Start the Rule Execution Server.
  6. Start CICS and install the HBRGROUP resources by using the following command:
    CEDA INSTALL GROUP(HBRGROUP)
  7. Install the BBOACSD group by using the following command:
    CEDA INSTALL GROUP(BBOACSD)
  8. Activate the optimized local adapters TRUE program by using the following command:
    BBOC START_TRUE

    You can use the BBOC transaction to start, stop, enable, or disable tracing for the TRUE module.

  9. Test the configuration by running the HBRC transaction to connect CICS to Rule Execution Server. If CICS succeeds in connecting to the server, message GBRZC9001I is produced. If CICS fails to connect to the server, message GBRZC9000E is produced with a return code that contains diagnostic information. If you forget to do BBOC START_TRUE, the message Transaction HBRC failed with abend AEY9 is produced when HBRC is run.
  10. 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 that is defined, add the PLTPI=HB parameter to the CICS system initialization parameters.
    • If you already have a program list table that is 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.
  11. Optional: To perform WOLA registration externally to Operational Decision Manager for z/OS, use the JCL variable HBRWOLAREGNAME to inform Operational Decision Manager for z/OS of the registration name to use. When the JCL variable HBRWOLAREGNAME is not set, the default is to call BBOA1REG when HBRC is called by using a randomly created name. For example, you might run the transaction BBOC REG RGN=ILKREGNAME DGN=CILK NDN=NILK SVN=WSVRILK, then set HBRWOLAREGNAME=ILKREGNAME.