Welcome
HCL Z Asset Optimizer 9.1
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 sets with 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.

HCL Z Asset Optimizer 9.1
- PDF manual
- Program Directory
- Product overview
  HCL Z Asset Optimizer is built on the concept of remote and central mainframe components which work together to produce reports on z/OS® mainframe products and their usage. This section provides you with a high-level overview of the HCL Z Asset Optimizer core architecture.
- Planning for deployment
  Before you deploy HCL Z Asset Optimizer, consider which deployment option is best suited to your environment.
- Implementing deployment scenarios
  Most implementations of HCL Z Asset Optimizer are based on one of the common deployment scenarios. An example is provided for implementing each of these common deployment scenarios with a Db2® Repository database. You can adapt an example for use with an SQLite Repository database.
- Installing and customizing HCL Z Asset Optimizer
  The product installation involves downloading the product and available updates, preparing the database, and configuring and populating a test database. After verifying that all components are correctly installed, you duplicate the test database to create a production database where you automate data collection and import tasks.
- Migrating to HCL Z Asset Optimizer 9.1
  When you migrate to the latest version of HCL Z Asset Optimizer 9.1 from an earlier version, you must convert existing data to be compatible with your new environment.
- 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 Z Asset Optimizer 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.
  - Applying Updates to GKB Database Via MHS Website
  - 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 sets with 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 HZASCUSTpost-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 PARMLIB 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, ASCDS. 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 ASCDS continues to grow.
    - Automation Server Utility program
      The Automation Server Utility program HZAAUTL can be used to extract and modify the contents of the VSAM ASCDS. It can be used as an ad hoc administrative tool or in production jobs to automate retry requirements.
- Reporting with the Analyzer
  The primary reporting facility in HCL Z Asset Optimizer is the Analyzer.
- Running utilities
  HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
- REST API
- Configuring Language support
  HCL Z Asset Optimizer includes Japanese language support for MVS™ Message Service (MMS) message information. You can also configure the Analyzer utility to create and view reports in Japanese.
- Reference information for HCL Z Asset Optimizer
  Reference information includes messages, repository table layouts, and performance and tuning.
- Troubleshooting and support
  To isolate and resolve problems with your HCL software, you can use the troubleshooting, messages, and support information. This information contains instructions for using the problem determination resources that are provided with your HCL products.
- HCL Z Asset Optimizer messages
  You can identify the type of message by the message prefix.
- Appendix A: Description of output message content
  Messages generated during batch processing are explained in detail here.
- Notices
HCL Z Asset Optimizer Container 9.1

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.

Procedure

Review the member in your customized JCLLIB library to ensure that the JCL is suitable for your operational environment, making alterations as necessary. If sourcing the JCL directly from the library, replace the symbols with appropriate values.
Copy the HZAJAUTO member from the JCLLIB library to an authorized PROCLIB library.