Home
Collecting and importing data with HCL Z Asset Optimizer
HCL Z Asset Optimizer includes programs that collect system and usage data, import, filter, and match this data, update the Repository tables, and make the data available for review and query.
Activating the Automation Server
The Automation Server discovers new data sets and processes them by starting a set of predefined actions that associate the data with data set name masks that form a catalog search. This search determines if any data set names matching the mask are to be processed.
Running the Automation Server
To run the Automation Server, you must create a control data set, configure the Automation Server as a started task, design request control statements, and exclude data sets from processing.
Copying the started JCL task to a library
The Automation Server is run by the HZAJAUTO member in the JCLLIB library that is supplied in the SHZAPROC data set. To start the HZAJAUTO member as a started task, you must customize the JCLLIB member and copy it to an authorized PROCLIB library.
Files used by the Automation Server
Several files must be available for use by the Automation Server.

Collecting and importing data with HCL Z Asset Optimizer
HCL Z Asset Optimizer includes programs that collect system and usage data, import, filter, and match this data, update the Repository tables, and make the data available for review and query.
- Updating the Global Knowledge Base
  HCL provides monthly updates to the Global Knowledge Base (GKB) so that you can keep your product inventory definitions up-to-date. You can also submit items to HCL support for inclusion in GKB updates.
- Collecting scanned libraries with the Inquisitor for z/OS
  The Inquisitor is a program that scans and collects information about partitioned data set (PDS) and partitioned data set extended (PDSE) program libraries. The Inquisitor Import program takes the collected data as input to form the basis of your software inventory.
- Collecting UNIX files with the Inquisitor for z/OS UNIX
  The Inquisitor for z/OS® UNIX™ is a program that collects information about executable software existing in HFS and zFS data sets currently mounted and accessible to z/OS UNIX. The Inquisitor Import program takes the collected data as input to form the basis of your z/OS UNIX software inventory.
- Collecting usage data with the Usage Monitor
  The Usage Monitor is a server address space that runs as a started task. Work is queued to the Usage Monitor from all address spaces where programs are used. The Usage Monitor moves captured program usage data into the collection repository and periodically writes the accumulated data to a sequential file. The Usage Monitor runs APF authorized and is non-swappable.
- Importing Inquisitor data
  The Inquisitor Import reads data from Inquisitor scans, where the data is filtered and matched to products. The filtered, matched data is then copied to the Repository tables where it can be viewed and queried by the Analyzer reporting utility.
- Importing usage data
  The Usage import job imports data generated by the Usage Monitor and aggregates usage data for discovered or identified modules in the Repository tables in the database.
- Aggregating usage and discovery data
  The Aggregator is a program that populates the Asset tables.
- Activating the Automation Server
  The Automation Server discovers new data sets and processes them by starting a set of predefined actions that associate the data with data set name masks that form a catalog search. This search determines if any data set names matching the mask are to be processed.
  - Automation Server overview
    The Automation Server provides the ability to select data sets if you have data set names that are variable, such as those created by the Usage Monitor, which have low-level qualifiers containing time stamps.
  - Running the Automation Server
    To run the Automation Server, you must create a control data set, configure the Automation Server as a started task, design request control statements, and exclude data sets from processing.
    - Creating the Automation Server control data set
      To create the Automation Server control data set, use member HZAASALC in the JCLLIB. This member is generated from the HZASCUST post-installation customization job.
    - Copying the started JCL task to a library
      The Automation Server is run by the HZAJAUTO member in the JCLLIB library that is supplied in the SHZAPROC data set. To start the HZAJAUTO member as a started task, you must customize the JCLLIB member and copy it to an authorized PROCLIB library.
      - Files used by the Automation Server
        Several files must be available for use by the Automation Server.
    - Designing request control statements
      Automation Server action requests are specified in the HZAAPARM member of the SHZAPARM file.
    - Starting and stopping the Automation Server
      When you install the Automation Server as a started task, you can run operator commands to start it and stop it. This task requires RACF® security access.
    - Excluding data sets
      You can exclude data sets from Automation Server processing. To exclude a data set, it must have a record in the Automation Server control data set, with an indication in the record that the data set is already processed.
  - Automation Server control data set maintenance
    A record is kept for every data set processed by the Automation Server in the Automation Server control data set, ACDS. The purpose of this record is to prevent the repeated processing of a data set for the same data set name mask. As records accrue, the size of the data in the ACDS continues to grow.

Files used by the Automation Server

Several files must be available for use by the Automation Server.

STEPLIB: Load library containing the product software. Not required if Z Asset Optimizer is installed into the system link list.
HZAACNTL: Partitioned data set containing fixed-length 80-byte records. Member HZAAPARM of this partitioned data set contains the Automation Server control statements that specify the actions to be performed. For each action in the HZAAPARM member, there is a corresponding member of the same name containing the template data for that action. The template data is made up of JCL or an FTP command stream containing symbolic references, to be resolved by the Automation Server when the action is performed.
HZAACDS: A VSAM KSDS control data set used by the Automation Server.
HZAAMSG: Specifies the message report file for the Automation Server. Initialization statements, error messages, and activity logging messages, are written to this file.
SYSPRINT: Specifies the message report file for Language Environment®.
SYSOUT: Specifies the message report file for Language Environment®.
OUTPUT: Specifies the message report file for the FTP program. The contents are determined by the FTP program installed in the system.
INPUT: Specifies a fixed length 120-byte record file containing FTP commands read by the FTP program. The FTP commands are written to this file before the Automation Server FTP action is performed.
INTRDR: Specifies a fixed length 80-byte record file to be directed to the internal reader used by the system. The Automation Server writes a job stream to this file whenever a JOB action is to be performed.