Collecting and importing data to the test Repository database

After creating the databases and database objects, you are ready to collect Inquisitor and Usage Monitor data. You can then import the collected data into the test Repository database.

Procedure

  1. Run the HZASINQZ job to scan the DASD for z/OS® product modules and generate output to the DD HZAPZIP output file.
    For large sites, this operation can take up to an hour. You can perform step 3 while the job is running.
  2. Run the HZASINQU job to scan z/OS® UNIX files and generate output to the DD HZAXZIP output file.
    For large sites, this operation can take up to an hour. You can perform step 3 while the job is running.
  3. To run the Usage Monitor to gather initial usage data, perform the following tasks:
    1. Run the HZASUMON job to start the Usage Monitor as a batch job.
      The Usage Monitor is typically run as a started task, but you can run it as a batch job for this test. This job runs continually until you stop it manually and most of the time this job is idle.
    2. Stop the Usage Monitor to generate the hzainst.UM&SMF.D*.T* output file.
      For example, enter the following command to stop the started task: 
      P HZAJMON
  4. To import Inquisitor (IQ) data into the test Repository database, perform the following tasks:
    1. Verify that the HZASINQZ and HZASINQU jobs that you started in steps 1 and 2 have completed.
      If the jobs are still running, wait until they are completed.
      The output logs from these jobs provide information on the number of records collected.
    2. Run the HZASIQIM job to import the data from the HZAPZIP and HZAUZIP output files that were created by the HZASINQZ and HZASINQU jobs.
      For large sites, this job can take more than two hours to run the first time. Performance is significantly faster on subsequent runs.
  5. Run the HZASUIMP job to import usage data from the hzainst.UM&SMF.D*.T* file.