Automating data collection and reporting activities

When you configure the Usage Monitor, the Automation Server, and the Analyzer to run as started tasks, these data collection and reporting activities are automated.

Procedure

  1. Configure the Usage Monitor utility to start automatically:
    1. In the HZASMNPM member of the PARMLIB data set, modify settings if necessary so that the DSN(hzainst.UM&SMF) command generates hzainst.UM&SMF.D*.T* data sets.
    2. Schedule a change request to roll out the new HZAJMON started task on all z/OS® LPARs.
    3. Copy the HZAJMON started task from the JCLLIB libray to the system PROCLIB data set.
    4. Arrange for the HZAJMON started task to start early in the initial program load (IPL) cycle to ensure that all usage activity is recorded.
  2. Configure the Automation Server utility to start automatically and to automate data collection and import tasks:
    1. Schedule a change request to roll out a new HZAJAUTO started task on all z/OS® LPARs.
    2. Run the HZAASALC job to define the automation control Virtual Storage Access Method (VSAM) data set.
    3. Configure the HZAAPARM settings to perform the following tasks every weekend:
      • Remote hosts: Runs an Inquisitor scan job to collect data, runs the ZCAT to amalgamate usage data, and transfers collected data via file transfer protocol (FTP).
      • Database host: Runs an Inquisitor Import job, runs a usage import job, and aggregates the data.
    4. If necessary, run the HZAASSCT job to mark existing data sets as being already processed in the automation control data set.
    5. Copy the HZAJAUTO started task from the JCLLIB library to the system PROCLIB data set.
    6. Arrange for the HZAJAUTO to start automatically at any time in the IPL cycle.
  3. Configure the Analyzer utility to start automatically:
    1. Schedule a change request to roll out the new HZAJANLO started task to the production database host.
    2. Copy the HZAJANLO started task from the JCLLIB data set to the system PROCLIB data sets.
  4. Configure the Analyzer utility to work with a secure socket layer (SSL) for HTTPS transport and to logon with a RACF® user ID and password:
    1. In the HZASANP2 member of the PARMLIB data set, change the security parameter to SECURITY=SYSTEM,
    2. Review and edit the comments in the HZASANS1, HZASANS2, and HZASANS3 members of the JCLLIB data set to create a digital certificate that is required for SSL.
    3. Configure the HTTPPORT parameter, if you require a value other than the default value.
    4. Review the Analyzer reports to confirm that all expected products are identified.