Scenario 1: Implementing a single Repository database with a single GKB database

The most common deployment scenario is an implementation with a single Repository database and a single global knowledge base (GKB) database.

About this task

The example deployment is for a Db2® database environment and includes the key parameters that influence this scenario.

Procedure

  1. Customize an instance of the HSISCUST member in the hsi.SHSISAMP data set with the following parameters:
    • DBTYPE=DB2
    • REPZSCHM=REPHLQ1
    • GKBZSCHM=GKBHLQ1
    • DB=REPDB1
    • DBGKB=GKBDB1
  2. Submit the HSISCUST job.
  3. Create the Repository and GKB databases and grant access to them:
    1. Run the HSISDB01 job to create storage groups.
    2. Run the HSISDB02 job to create the GKB database and database objects.
    3. Run the HSISDB03 job to create the Repository database and database objects.
    4. Run the HSISGKBL job to load GKB data.
    5. Run the HSISGRNT job to grant DBADMIN access to IBM Z Software Asset Management administrator.
    6. Optional - Run the HSISGRTB job to grant SELECT access to database tables.
  4. Collect Inquisitor and Usage Monitor data:
    1. Run the HSISINQZ job on all z/OS® LPARs to collect Inquisitor data.
    2. Run the HSISINQU job on all z/OS LPARs to collect Inquisitor data for UNIX®.
    3. Run the HSISUMON job on all z/OS LPARs to collect usage data.
    4. Run the HSISZCAT 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 HSISIQIM job to import Inquisitor data into the Repository database for each LPAR.
    2. Run the HSISUIMP job to import Usage data into the Repository database for each LPAR.