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.
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.

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.
  - 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 set names matching the mask are to be processed.

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

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.

If the HZASIQIM job processes the same data that is generated by the Inquisitor scan for a specified system, the job terminates with an error to indicate that the input file is a duplicate input file.

Procedure

In the HZASIQIM job, update the following parameters, according to your requirements:
- FULLREMATCH: Set to N (no) to skip import from scanned libraries where no member directories have changed since a previous Inquisitor Import to the same Repository. Set to Y (yes) to import and match process all libraries.
  When FULLREMATCH is set to Y, an extra check is performed on libraries 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.
- PRODUCTONLY: Set to N (no) to import all modules, including unidentified modules. Set to Y (yes) 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.
Submit the HZASIQIM job.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.