IBM DB2 Setup

The following steps are required in order to use Database Monitors with an IBM DB2 database. Cleo provides the EXT_DBMON1 and EXT_DBMON2 scripts in the DB2 directory. Use these scripts to execute the required setup of your database.

Before you begin:

Procedure

Before you begin this procedure, please note the actual DB2 directory can be obtained two different ways - each with their own specialised procedures.
  • The directory is found on the Product DVD, or;
  • The directory has been provided by Support or obtained from a source other than a DVD.

If using the Product DVD

  1. Load the image into the image catalog (or restore the SAV file).
  2. Log on with profile having class *SECOFR
  3. LODRUN DEV(*OPT) DIR(‘/DB2’)
    Note: The device DEV(*OPT) may be different than *OPT based on you system.

If using the DB2 directory (not from DVD)

You must create an image catalog on the IBM i to hold the directory.
  1. Log on with profile having class *SECOFR
  2. WRKIMGCLG
  3. For the image catalog being used, make sure it is Not Ready
  4. Use option 12=Work with entries
  5. Use option 1 = Add on the first line
  6. F10=Additional parameters:
    • From image file: *NEW
    • To image file: DBMON
  7. Use option 6=Mount on the DBMON Image
  8. Use F6=Load/Unload image catalog
  9. Use option 10 = Initialize on the DBMON Image
  10. Use option 12 = Work with volume on the DBMON Image
  11. Use option 11 = Work with object links
    • Note the directory. Should start with /QOPT/
  12. Drag the /DB2 directory to the /QOPT directory noted above.
  13. LODRUN DEV(OPTVRT01) DIR('/DB2')

Results

Completion of the configuration process results in the following:
  • Creates the EXTOL_DBMON schema.
  • Loads and registers the stored procedure code, including dependencies.
  • Creates a database queuing table (EXTOL_DBMONITOR); the stored procedure uses this table to queue messages for delivery to Clarify.
  • Grants required permissions to the queuing table (EXTOL_DBMONITOR).
  • Creates the stored procedures used to invoke the stored procedure code.
  • Grants necessary execute permissions to the stored procedures.
  • Creates a DB2 sequence object used as primary key on the queuing table.