Home
Running utilities
HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
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.

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.
- 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 IBM 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 Import utility imports data (CSV files) which is generated from the IBM Subcapacity Reporting Tool.
- Capturing historical SMF data with the SMF Scanner utility
  You can run the SMF Scanner utility to get historical usage information from existing SMF data. This SMF data enables you to view trending results from before HCL Z Asset Optimizer is installed.
- 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).
- 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.
- Verifying database changes since the product was released
  This utility verifies database changes that were introduced after the product was released.

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.

To minimize space utilization and improve SQL query performance, keep no more than three months of detailed module usage data and 13 months of aggregated product usage data.

If you do not run the Usage Deletion utility for some time, select a period of a few months, in order to keep the run times down to a reasonable time.

Running the Usage Deletion utility

To run the Usage Deletion, use the job HZASUDEL, 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.
KEEPDETAIL=: Default is 2. Number of months prior to the current month for which detailed and summarized module usage data are kept. KEEPDETAIL=0 means all detailed and summarized module usage data excluding those from the current month are deleted.
KEEPAGGR=: Default is 12. Number of months prior to the current month for which aggregated product usage data are kept. KEEPAGGR=0 means all aggregated product usage data, excluding those from the current month are deleted.
FIRSTDATE=: Start of the first date range. This is in the form YYYYMM. Only complete months are chosen.
LASTDATE=: End of the last date range. This is in the form YYYYMM.
Note: The date range of deletion is inclusive of the month specified in the FIRSTDATE and LASTDATE parameters.
REPSCHEMA=: Repository qualifier. Name of qualifier is &REPZSCHM.
SID=: System Identifier of system for which usage should be deleted. Specify SID=ALLSIDS to delete usage data for all SIDs.

Note: If KEEPDETAIL is set to a value, then FIRSTDATE / LASTDATE will be ignored. If detailed usage data are to be deleted within a certain date range, then comment out KEEPDETAIL and define dates for FIRSTDATE / LASTDATE. For further details, please see comments described in job HZASUDEL.

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.