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 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.
Running the Usage Import

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.
    - Running the Usage Import
    - TPARAM parameters
      The TPARAM parameters that you specify for Usage Import define what data is included in the import.
  - 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 Usage Import

About this task

The HZASUIMP job in the JCLLIB library performs the Usage import. This job is generated from the HZASCUST post-installation customization job. Because run-time for this job depends on the volume of usage data to load, run this job during off-peak periods.

Usage data files can be either outputs from the Usage Monitor or condensed outputs from the ZCAT utility. These output files can be concatenated as a single input in the job. When you are priming a new repository, use a single small file as input when loading usage data for the first time.

If the HZASUIMP job processes the same data that is generated by the Usage Monitor for a specified system, the job skips with a warning message and continues processing the remaining files.

When running Usage import for an LPAR that belongs to a shared sysplex environment, all library records already identified in the LPAR where the IQ Import was run, are also populated into the LPAR where Usage import was run. For example, if IQ import is run only for MVSA (with PLX=Y), and Usage import for MVSB is run for the first time, then all library records identified in MVSA are now propagated for MVSB. This means that when viewing the Analyzer product inventory report for LPAR MVSB, all products belonging to the shared sysplex are displayed. This propagation of library records does not occur if PLX=N is set in MVSA.

For Db2® only: If you are running Db2® in a Data Sharing Group, you can use the Group Attach Name. See Step 2 of Importing Inquisitor data.