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

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.

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.

The Inquisitor Import loads data and performs the following tasks:

Reads Inquisitor data generated from Inquisitor scans. To exclude importing specific libraries, the Inquisitor data is filtered against a set of supplied Inquisitor filter tables. These Inquisitor filter tables are updated monthly, together with the knowledge databases. The filtering excludes, for example, the ISV distribution libraries.
Matches load modules to best fitting products at the version, release, and modification (VRM) level. Best matches for modules are found based on module names and sizes, and information in the Global Knowledge Base (GKB) and Local Knowledge Base (LKB). Temporary scorecard tables are used to hold all the possible scorecards for modules in a given library while they are matched.
Loads matched load modules, including matching information, into the Repository tables. Data from the Repository tables are now ready for viewing or reporting using the Analyzer reporting facility.
Aggregates usage data for rediscovered modules in the Repository tables.

The Inquisitor Import uses memory intensively in order to efficiently match many Knowledge Base scorecards to library modules. The maximum memory requirements depend on the number of modules in a library of an Inquisitor Import file, and the number of scorecards in the GKB and LKB that affect the processed libraries. To estimate a requirement, allow 5M +1.5k per module. For example, for an Inquisitor file containing a maximum library size of 30000 modules, the requirement is approximately 5M + (0.0015*30000) = 50M.

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.