Scenario 2: Implementing multiple Repositories with a shared GKB database

This deployment scenario implements two Repositories in a single Db2® subsystem that share a single global knowledge base (GKB) database. The advantage of sharing the same GKB is that you need only apply monthly updates to a single GKB database.

About this task

The example deployment is for two Repositories in the same Db2® subsystem to enable the Analyzer to browse both Repositories at the same time.

Procedure

  1. Customize an instance of the HZASCUST member in the hza.SHZASAMP data set with the following parameters.
    • DBTYPE=DB2
    • REPZSCHM=REPHLQ1
    • GKBZSCHM=GKBHLQ1
    • DB=REPDB1
    • DBGKB=GKBDB1
  2. Submit the HZASCUST job.
  3. Create the Repository and GKB database and grant access to them:
    1. Run the HZASDB01 job to create storage groups.
    2. Run the HZASDB02 job to create the GKB database and database objects.
    3. Run the HZASDB03 job to create the Repository database and database objects.
    4. Run the HZASGKBL job to load GKB data.
    5. Run the HZASGRNT job to grant DBADMIN access to HCL Z Asset Optimizer administrator.
    6. Run the HZASGRTB job to grant SELECT access to database tables.
  4. Collect Inquisitor and Usage Monitor data to:
    1. Run the HZASINQZ job on all z/OS LPARs to collect Inquisitor data.
    2. Run the HZASINQU job on all z/OS LPARs to collect Inquisitor data for UNIX®.
    3. Run the HZASUMON job on all z/OS LPARs to collect usage data.
    4. Run the HZASZCAT job to condense usage data, separately for each z/OS LPAR (if there are usage data from 3 LPARs, then there should be 3 condensed output files).
  5. Transfer the collected Inquisitor and condensed ZCAT usage data to the central site via file transfer protocol (FTP).
  6. Import Inquisitor and Usage Monitor data at the central site:
    1. Run the HZASIQIM job to import Inquisitor data into the Repository database for each LPAR.
    2. Run the HZASUIMP job to import Usage data into the Repository database for each LPAR.
  7. Customize another instance of the HZASCUST member in the hza.SHZASAMPdata set with the following parameters:
    • DBTYPE=DB2
    • REPZSCHM=REPHLQ2
    • GKBZSCHM=GKBHLQ1
    • DB=REPDB2
    • DBGKB=GKBDB1
  8. Submit the HZASCUST job.
  9. Create the second Repository and grant access to it: It is not necessary to run jobs to create and populate the GKB database in this step because the second Repository shares the GKB that was created in steps 3b and 3d.
    1. Run the HZASDB01 job to create storage groups.
    2. Run the HZASDB03 job to create the Repository database and database objects.
    3. Run the HZASGRNT job to grant DBADMIN access to HCL Z Asset Optimizer administrator.
    4. Run the HZASGRTB job to grant SELECT access to database tables.
  10. Collect Inquisitor and Usage Monitor data to add to the second Repository database:
    1. Run the HZASINQZ job on all z/OS LPARs to collect Inquisitor data.
    2. Run the HZASINQU job on all z/OS LPARs to collect Inquisitor data for UNIX.
    3. Run the HZASUMON job on all z/OS LPARs to collect usage data.
    4. Run the HZASZCAT job to condense usage data, separately for each z/OS LPAR (if there are usage data from 3 LPARs, then there should be 3 condensed output files).
  11. Transfer the collected Inquisitor and condensed ZCAT usage data to the central site via file transfer protocol (FTP).
  12. Import Inquisitor and Usage Monitor data at the central site:
    1. Run the HZASIQIM job to import Inquisitor data into the second Repository database for each LPAR.
    2. Run the HZASUIMP job to import Usage data into the second Repository database for each LPAR.

What to do next

Repeat steps 7-12 for each additional Repository that you want to create, changing the values for the REPZSCHM and DB parameters for each new Repository.