Welcome
HCL Z Asset Optimizer 9.1
Running utilities
HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
Loading data into a staging table (for Db2® only)

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.
- 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.
  - Condensing usage data with the ZCAT utility
    The ZCAT utility concatenates and condenses Usage Monitor data sets and generates a file that is then processed by the Usage Import program. When you condense the data produced by the Usage Monitor program, you can save storage space and improve the performance of the Usage Import program.
  - Deleting usage data with the Usage Deletion utility
    Use the Usage Deletion utility to delete detailed, summarized, and aggregated usage data for a specified period for all systems in the repository. Each time you run the utility, usage data is aggregated to update the asset tables.
  - Deleting a specific system with the System Deletion utility
    Use the System Deletion utility to delete discovery, usage, and hardware data for a specified system.
  - Deleting obsolete data with the Physical Deletion utility
    Use the Physical Deletion utility to delete obsolete data that are no longer required.
  - Deleting obsolete audit records with the MDEL Deletion utility
    Use the MDEL Deletion utility to delete obsolete audit records that are no longer required.
  - High-level qualifier listing
    HCL Z Asset Optimizer collects large amounts of usage data. The High-level Qualifier Listing for the Usage Monitor utility creates a list of high-level qualifiers for the products that are to be identified.
  - Updating the TPARAM table
    The TPARAM table in the repository can be set to an inconsistent state due to failures in jobs that update the repository tables. You can reset a parameter in the TPARAM table to rectify this inconsistent state.
  - Tagging unidentified products with the Product Tagging utility
    The Product tagging utility allows you to create local entries for your in-house software in the Local Knowledge Database. It is not intended for creating HCL or ISV software, as this may cause unpredictable results. If you need to add products or versions that are not being identified, then notify HCL Support, so that they can then update the GKB. On certain occasions, HCL Support may consider your request to add HCL or ISV software to the LKB database, but contact them first before doing so.
  - Importing Subcapacity reporting data with the SCRT Import utility
    The SCRT (Subcapacity Reporting Tool) Import utility imports data (CSV files) which are generated from the HCL Subcapacity Reporting Tool. The import tool now also supports the importing of Tailored Fit Pricing (TFP) data. New reports to show TFP data are available in the Analyzer under the Asset tab.
  - Extracting data with the XML Export utility
    The XML Export utility extracts information in XML format that you can then import into IBM Control Desk (ICD).
  - Loading data into a staging table (for Db2® only)
  - Reporting LMOD ownership from the CSI
    The CSI scanning utility scans LMOD ownership in target zones either from the GLOBAL CSI or a TARGET CSI.
  - Compressing and decompressing data sets with the HZAZIP utility
    HZAZIP is a utility program that can compress a sequential or partitioned data set into a zip archive, decompress the contents of a zip archive into a sequential or partitioned data set, and report on the contents of a zip archive.
  - Browsing zipped data
    Components such as the Inquisitor programs, the Usage Monitor, and the ZCAT utility deal with sequential data sets containing zip archives. Processing the data with a zip algorithm allows the same information to be conveyed in a fraction of the original size, but it does mean that browsing the file to quickly confirm the nature of its content becomes a more involved process.
  - Browsing active collection data
    The Usage Monitor collects program usage information and writes out the collected data at least once each day. Once the data is in a data set, it is possible to browse it to determine if some expected usage was collected or not. Sometimes it would be advantageous to be able to determine if expected data collection has taken place without waiting for the collection cycle to end, either at the expected time or because it was triggered manually to facilitate data access.
  - Usage Monitor Trace Reporter
  - Verifying database changes since the product was released
    This utility verifies database changes that were introduced after the product was released.
- 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

Loading data into a staging table (for Db2® only)

Use this utility to load data from a UMON/ZCAT file into the TSTAGE table. Once the TSTAGE table is populated, the data can be browsed using an Analyzer report. Pre-loading into a table that is indexed speeds up the process.

As the search fields are now indexed, there will be better performance when searching for usage data .

Data input

DDNAME INSTAGE contains the UMON or ZCAT file. The file can either be a zipped or unzipped file and multiple UMON/ZCAT files are allowed as input. However, the concatenated UMON/ZCAT files must all be zipped files or all unzipped files.

Note:

To access the loaded data, click on the checkbox: 'Use Preloaded data' in the Analyzer report, 'Usage Monitor File Detail' from the Discovery Tab.

Running the loading utility

To run the loading utility, use the job HZASTAG in the JCLLIB. This job is generated from the HZASCUST post- installation customization job.

TPARAM parameters

COMMIT=: Default is 1000. Number of records stored before issuing of COMMIT.
DSN=: Db2® location. Value assigned, as defined in job HZASCUST.
REPSCHEMA=: Repository qualifier. Name of qualifier is &REPZSCHM.