Creating a production Repository database

The production Repository database runs on a development logical partition (LPAR), and it is not necessary to run it on a business workload LPAR. You can duplicate the content of test Repository database to populate production Repository database without collecting and importing Inquisitor and Usage Monitor data again.

About this task

You can create the production Repository database on a Db2® or SQLite database. This procedure combines instructions for both database environments. See Configuring a test Repository database for database-specific instructions.

Procedure

  1. Run the HSISDB01 job.
    • For Db2, the job creates storage groups.
    • For SQLite, the job allocates the zFS file system.
  2. Run the HSISDB02 job to create the database objects for the Global Knowledge Base (GKB).
  3. Run the HSISDB03 job to create the Repository database and database objects.
    For Db2 databases: Before running the HSISDB03 job, review and change definitions in PARMLIB members HSISSQ17 and HSISSQ18 as needed to meet site requirements:
    • In member HSISSQ17 of PARMLIB library, use the MAXPARTITIONS parameter to increase the number of partitions for the three largest table spaces (VMODULE, VUSEMTD, and VPRODDET) according to site requirements.
    • In member HSISSQ18 of the PARMLIB library, the COMPRESS keyword is set for all indexes. Bufferpool BP8K0 must first be activated in Db2 before these compressed indexes can be created. Rename and activate different Bufferpool names according to site requirements.
  4. Run the HSISGKBL job to load the GKB.
  5. Run the HSISGRNT job.
    • For Db2, the job grants DBADMIN access to the IBM Z Software Asset Management administrator for the Repository and GKB databases.
    • For SQLite, the job grants access to the z/OS® OMVS groups.
  6. Optional - Run the HSISGRTB job.
    For Db2, this job grants SELECT access to database tables.
  7. To populate the production Repository database, repeat the procedure for collecting and importing data that you performed to populate the test Repository database.

What to do next

Configure security for the production Repository database.