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.
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.
Running the Inquisitor Import
The HZASIQIM job in the JCLLIB library performs the Inquisitor Import. This job is generated from the HZASCUST post-installation customization job.

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.
    - Running the Inquisitor Import
      The HZASIQIM job in the JCLLIB library performs the Inquisitor Import. This job is generated from the HZASCUST post-installation customization job.
    - Import filters and matching
      When you import data collected by the Inquisitor, the import procedure reads the data and filters and matches the data before copying the data to the Repository tables.
    - TPARAM parameters
      The TPARAM parameters that you specify for Inquisitor Import define what data is included in the import.
  - 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.
- 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

Running the Inquisitor Import

The HZASIQIM job in the JCLLIB library performs the Inquisitor Import. This job is generated from the HZASCUST post-installation customization job.

About this task

Warning: This job will terminate immediately if the GKB version referenced by the job is older than 12 months. To rerun this job you need to:

Download the PTF containing the latest GKB version.
Run HZASGKBL to load the latest GKB version.
Rerun HZASIQIM.

Run-time for the HZASIQIM job depends on the number of modules to be imported into the database Inquisitor tables. Because the processing is memory-intensive, run the HZASIQIM job during off-peak periods.

Procedure

In the HZASIQIM job, update the following parameters, according to your requirements:
- FULLREMATCH: Set to Y (default), to process all libraries in the in the repository. For a given system ID (SID), existing libraries in the repository are marked as deleted unless the libraries are found in the scanned Inquisitor file. For shared libraries (where PLX=Y), the scanned Inquisitor file can be from any SID that belongs to the sysplex. For non-shared libraries (where PLX=N), the scanned Inquisitor file must be from the same SID. The deletions include products, libraries, and modules. For more information on the setting of PLX=Y, see Scenario 5: Implementing in a sysplex environment.
  Set to N to skip import from scanned libraries where no member directories have changed since a previous Inquisitor Import to the same Repository.
- PRODUCTONLY: Set to N to import all modules, including unidentified modules. Set to Y to import only matched modules.
The settings for both of these parameters influence the duration of the import process.
Review and modify other parameters, as required, in the PARMLIB member.
Db2® only: In PARMLIB member HZASCLI, parameter MVSDEFAULTSSID can be assigned the Group Attach Name for Db2® subsystems configured in a Data Sharing Group. The default value is the Db2® subsystem name.
Submit the HZASIQIM job.