Additional CA Chorus for DB2 Database Management Configuration

Additional CA Chorus for DB2 Database Management Configuration

Override the DB2 Execution Mode

To support a DB2 subsystem running in Compatibility Mode (CM or CM*), you update a user configurable file to reflect the current executing mode of DB2. The configuration file directs CA Chorus for DB2 Database Management to treat a DB2 subsystem running in CM or CM* as a different version of DB2. This file is located in the following USS directory and is created as part of deploying CA Chorus for DB2 Database Management:

/<chorus-install-home>/roles/dba/DBMzDB2-version-override.txt

Note: This procedure assumes that the applicable CA Chorus servers are already defined.

Follow these steps:

1. Add a DB2 subsystem override definition in comma-separated value (CSV) format for each DB2 running in CM or CM* using the E3KMOD10 member in your_chorusdba_hlq.CE3KPARM. The file is comma-separated value (CSV) format and contains the following columns:

   dsConf

   Specifies the confederation that is used to access this DB2 subsystem. The confederation names are defined in the db2tools.cfg configuration file that is located in the /cai/cetjr3m0/CA_axis2c/config USS directory by default.

   dsGroup

   Specifies the DB2 data sharing group attach name. If the DB2 subsystem is not a data sharing group member, leave this value blank.

   dsSystem

   Specifies the LPAR where the DB2 subsystem is running.

   dsSSID

   Specifies the DB2 subsystem identifier.

   VersionOverride

   Specifies the DB2 override version. Use the following values in place of the actual DB2 version.

   • For DB2 V8, specify 081.
   • For DB2 9, specify 091.
   • For DB2 10, specify 101.

2. Copy the E3KJBCRD member in your_chorusdba_hlq.CE3KJCL into the EK3I0030 member in your_chorusdba_hlq.CE3KJCL, save your changes, and submit the job.

   The CA Chorus for DB2 Database Management DB2 subsystem version override definitions are created. The DBMzDB2-version-override.txt file in <chorus-install-home>/roles/dba is updated.

3. Activate your changes by restarting the CA Chorus JBoss STC.

Example:

In this example, note the following DB2 subsystem settings:

• DA0G and D91A are part of the QA confederation as defined in the db2tools.cfg.
• DA0G is a DB2 10 data sharing group member of data sharing group DA0G running in CM9.
• D91A is a DB2 10 subsystem running in CM8*. The DB2 subsystem is not a data sharing group member.

To support this configuration:

1. Update the E3KMOD10 member as follows:

   dsConf,dsGroup,dsSystem,dsSSID,VersionOverride
   

   QA    ,DA0G   ,CA31    ,DA1G  ,091
   QA    ,       ,CA31    ,D91A  ,081
   

2. Submit the E3KI0030 member in your_chorusdba_hlq.CE3KJCL.