Home
Running utilities
HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
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.
HZAZIP data set support
The data control block (DCB) attributes of the original data set that the HZAZIP utility compresses are not encoded into the archive. The success of a compress and decompress cycle requires the user to supply suitable DCB attributes for the ultimate destination of the data.

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.
  - Text data processing
    The HZAZIP utility processes text data to be compatible with the zip processing utilities available on other platforms.
  - Binary data processing
    The HZAZIP utility processes binary data in order to preserve record boundaries, while other platforms typically consider binary data to be a byte stream without structure.
  - HZAZIP program parameters
    The HZAZIP utility can accept up to two program parameters. The first parameter specifies the function the program is to perform and the second parameter can provide a data definition override list for programs that dynamically invoke the utility.
  - HZAZIP files
  - Dynamic invocation by other programs
    Other programs can call the HZAZIP utility to perform compression and decompression processing requests. When the HZAZIP utility receives control, it examines the program parameter list and proceeds accordingly.
  - HZAZIP data set support
    The data control block (DCB) attributes of the original data set that the HZAZIP utility compresses are not encoded into the archive. The success of a compress and decompress cycle requires the user to supply suitable DCB attributes for the ultimate destination of the data.
  - HZAZIP return codes
    When you run the HZAZIP utility, several codes are returned that indicate whether the program ran successfully.
- 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.

HZAZIP data set support

The data control block (DCB) attributes of the original data set that the HZAZIP utility compresses are not encoded into the archive. The success of a compress and decompress cycle requires the user to supply suitable DCB attributes for the ultimate destination of the data.

The following points are provided to help you to assess whether the HZAZIP utility can successfully process a data set:

When processing a whole partitioned data set, the file name specified after ZIP= or ADD= is ignored because the member names are used to label the archived files.
When ZIP processing detects that a PDS member is a zip archive, the member is stored as a byte stream as is without attempting further compression or record boundary preservation.
ZIPBIN processing of PDS members containing zip archives usually causes the compressed size to be larger than the uncompressed size, due to the inability to further compact the data and the insertion of RDWs to preserve record boundaries. So, if the only non-text data in a PDS is in members which are themselves zip archives, specify ZIP rather than ZIPBIN to minimize the resultant file size.
When using ADD or ADDBIN, avoid duplicate file names in the resultant archive.
You can use the ADD and ADDBIN parameters to create an archive with a mixture of text and binary file members.
The binary or text nature of an unzip process is set by the program parameter and not from the attribute values in the file header.
When the HZAZIP utility creates a zip archive, the data set name of the input file is stored as the zip archive comment.
PDS member user data such as system status information (SSI), ISPF statistics, and load module attributes are stored in the comment field of the central file header of the archive member and can be restored during unzip operations.
Alias members are stored as files with zero bytes. The alias member data is preserved only if the real member associated with the alias member is also processed.
Use ZIPBIN and UNZIPBIN when processing load module libraries.
Segment overlay programs are not restored properly, unless the TTRs happen to match, because the TTRs in the segment tables are not updated by the HZAZIP utility.
The HZAZIP utility cannot restore program PDSE data sets because only the program binder can write to program PDSEs. There is no restriction on data PDSEs.

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.