Creating a DB2 database for your rules runtime persistence layer

zRule Execution Server for z/OS® and Rule Execution Server can use a DB2® database to store RuleApps and other artifacts.

1. Define a RACF® group to control access to the database by completing the following steps:
   1. Create the ++DB2GROUP++ RACF group and add it to an existing superior group by using the following command:

      ADDGROUP ++DB2GROUP++ SUPGROUP(SYS1) OWNER(SYS1)

   2. Give the ++DB2GROUP++ RACF group access to the DB2 class and the profiles for batch and CICS® by using the following commands. The database administrator performs this task.

      PERMIT <MY_DB2_SSID>.BATCH CLASS(DSNR) ID(++DB2GROUP++) ACCESS(READ)

      PERMIT <MY_DB2_SSID>.SASS CLASS(DSNR) ID(++DB2GROUP++) ACCESS(READ)

      Note: After you enter the PERMIT commands, RACLISTed profiles for DSNR will not reflect the updates until a SETROPTS REFRESH is issued.
2. Create the database tables by running the jobs that are listed in the following table, in the order shown. The data set members are in the ++HBRWORKDS++.SHBRJCL data set, where ++HBRWORKDS++ represents the high-level qualifier that is assigned to the working data sets.
   Note: Verify that the jobs contain the correct settings. The settings were copied from the ++HBRHLQ++.SHBRPARM(HBRINST) member when you created the working data sets.

   Data set member	Description
   HBRDSCDB	Creates the table for storing the deployed RuleApps.
   HBRDSXOM	Creates the table for storing the deployed Execution Object Models (XOMs).
   HBRDSCTR	Creates the trace tables.
   HBRDSCDR	Creates the Decision Runner tables.

3. If you did not run the HBRDSCTR job, edit the ++HBRWORKDS++.SHBRJCL(HBRDSGRN) job to remove the entries to grant access to those trace tables.
4. Give the ++DB2GROUP++ RACF group access to the newly created tables by running the following job:

   ++HBRWORKDS++.SHBRJCL(HBRDSGRN)

5. Give database access to the user ID to be used by the server to connect to the database. Use the following command:

   CONNECT ++DB2USER++ GROUP(++DB2GROUP++)

   where ++DB2USER++ represents the user ID used to access the database.