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.
Aggregating usage and discovery data
The Aggregator is a program that populates the Asset 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.
- 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.
  - TPARAM parameters
    The TPARAM parameters that you specify for aggregating usage and discovery data is included in the import.
- 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.

Aggregating usage and discovery data

The Aggregator is a program that populates the Asset tables.

These tables are accessed by Analyzer reports and batch jobs, and offer a higher level view of product discovery and usage at a version rather than a release or module level. The Aggregator also calculates product discovery and usage count totals that are used to speed up the Analyzer queries.

The Aggregator should be run as the final job in a batch run of Inquisitor Import and Usage Import jobs, and before the repository is accessed by the Analyzer. This ensures that asset reports and counts are synchronized with the latest collected discovery and usage details.

It is usual for asset level usage details to be kept longer than module usage details. This is controlled by the KEEPAGGR parameter of the Usage Deletion program, which has a longer default period than the KEEPDETAIL parameter. The aggregated entries are normally kept for the longer KEEPAGGR period and are usually only recalculated for periods where module usage details are available.

The Aggregator run can be time consuming since it is run for the entire repository and periods rather than an individual SID (as in the case of the Inquisitor Import), or system and period (as in the case of the Usage Import). It is therefore more efficient to run the Aggregator only once following several imports of usage or discovery data. Ensure also that you do not keep usage details for longer than is necessary for your site, and that Usage Deletion is run on a regular basis.

An example of how to run the Aggregator can be seen in sample jobs that are generated by HZASCUST, such as HZASIQIM (Inquisitor Import) and HZASUIMP (Usage Import).

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.