Jump to main content
Program Directory
PDF
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 Z Asset Optimizer core architecture.
Implementing HCL Z Asset Optimizer with SQLite database
You can implement HCL Z Asset Optimizer with an SQLite database if you do not have a Db2® for z/OS® license, or if you are currently unable to deploy one. If you implement Z Asset Optimizer with an SQLite database, there are certain functional and performance limitations.
Accessibility
Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully.
How to read the syntax diagrams
What’s New in HCL Z Asset Optimizer version 2.2
New features and capabilities in HCL Z Asset Optimizer version 2.2 help your organization achieve greater efficiency in asset discovery.
Before you deploy HCL Z Asset Optimizer, consider which deployment option is best suited to your environment.
Predeployment considerations
You can deploy Z Asset Optimizer to use a single Repository or multiple Repositories.
Deployment data processes
HCL Z Asset Optimizer is structured on several key data processes.
Deployment for a single Repository
The recommended procedure for deploying the Inquisitor and Usage Monitor to collect raw data is to deploy both components on every system in your organization.
Deployment for multiple Repositories
Multiple Repositories can be required to provide support for more than one data center, for different geographical regions, and for running multiple customers.
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.
Installation prerequisites
Before you install HCL Z Asset Optimizer, verify that the required hardware and software are available in the installation environment.
System configuration requirements
Security and authorization requirements
A z/OS® user ID with appropriate RACF® access is required to submit the batch jobs used in the customizing and operation of Z Asset Optimizer . Additional security and authorization configurations can be necessary, depending on your environment.
Checklist of installation and customization tasks
This checklist includes a set of procedures for installing the product, creating a test database, populating data, and validating the test installation. When you complete these procedures, you are ready to create a production environment for HCL Z Asset Optimizer.
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 a SQLite Repository database.
Scenario 1: Implementing a single Repository database with a single GKB database
The most common deployment scenario is an implementation with a single Repository database and a single global knowledge base (GKB) database.
Scenario 2: Implementing multiple Repositories with a shared GKB database
This deployment scenario implements two Repositories in a single Db2® subsystem that share a single global knowledge base (GKB) database. The advantage of sharing the same GKB is that you need only apply monthly updates to a single GKB database.
Scenario 3: Implementing multiple Repositories with multiple GKB databases
This deployment scenario implements two Repositories in a single Db2® subsystem, each with its own global knowledge base (GKB) database. This deployment scenario is not common because you must apply monthly updates to each GKB database.
Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites
This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.
Scenario 5: Implementing in a sysplex environment
This deployment scenario is for a sysplex environment, where the DASD is fully shared across all z/OS® LPARs that belong to the sysplex. This special deployment is similar to the deployment scenarios 1, 2, or 3, but the implementation steps are slightly different. This approach is intended to achieve operational efficiency by processing only a single z/OS LPAR within a sysplex.
When you migrate to the latest version of HCL Z Asset Optimizer from an earlier version, you must convert existing data to be compatible with your new environment.
Migrating from version 1.1 to HCL Z Asset Optimizer version 2.2 (Db2® database)
When you upgrade to HCL Z Asset Optimizer version 2.2 for Db2 database, there is no porting of data within the Repository database. New Db2 objects are defined to the Repository. The existing version 1.1 GKB database is dropped and re-created with the same database name for version 2.2.
Migrating from version 1.1 to HCL Z Asset Optimizer version 2.2 (SQLite database)
When you upgrade to HCL Z Asset Optimizer version 2.2 for SQLite database, there is some porting of data within the Repository database. New SQLite objects are defined and obsolete objects dropped from the Repository. The existing version 1.1 GKB database is dropped and re-created with the same database name for version 2.2.
Migrating from IBM Tivoli Asset Discovery for z/OS version 8.1 to HCL Z Asset Optimizer version 2.2
If you wish to port data from IBM Tivoli Asset Discovery for z/OS version 8.1 to HCL Z Asset Optimizer version 2.2, you need to unload data from the version 8.1 repository and reload the unloaded data into a new version 2.2 repository.
Migrating from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2
If you wish to port data from IBM Z Software Asset Management version 8.2 to HCL Z Asset Optimizer version 2.2, you need to unload data from the version 8.2 repository and reload the unloaded data into a new version 2.2 repository.
Post migration errors
If migration from version 1.1 to version 2.2 is incomplete, or if a wrong combination of files, jobs, or PARMLIB members are used between the two versions, then you might get the following errors.
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.
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.
The license verification feature enables you to upload your license information into Z Asset Optimizer and verify that these licenses match the Z Asset Optimizer data that has been identified. Using this feature, you can run the following reports:
The primary reporting facility in HCL Z Asset Optimizer is the Analyzer.
Analyzer prerequisites
The Analyzer uses the Db2® Call Library Interface (ODBC/CLI), also used by the Inquisitor Import, Usage Import and other batch components, and the z/OS® socket application programming interface. For the SQLite database, the Analyzer uses an internal ODBC interface.
Analyzer JCLLIB and PARMLIB members
Several JCLLIB and PARMLIB members are used when you run the Analyzer to generate reports.
Running the Analyzer in online mode
The primary reporting facility in HCL Z Asset Optimizer is the Analyzer. You can use the Analyzer in online mode to view reports, run queries, and drill down to related reports.
Running the Analyzer in batch mode
If you want to automate report generation, you can run the Analyzer in batch mode.
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 are generated from the IBM 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.
Filtering out non-IBM® programs from the Inquisitor and Usage data utility
You can run the IBM Filter utility to filter out non-IBM® programs. The output file generated from this utility can be sent to HCL support for diagnosis.
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.
HCL Z Asset Optimizer allows you to configure your system to provide specific language support.
Configuring the Turkish Db2 subsystem for use with HCL Z Asset Optimizer
If Db2 for z/OS is configured with SCCSID=1026, additional customization is required in setting up HCL Z Asset Optimizer.
Reference information includes messages, repository table layouts, and performance and tuning.
Repository table layouts
This topic describes the tables in the Repository including column names, types, and length.
Post-installation jobs
After installation, you can create a custom version of any job in the JCLLIB library or any parameter in the PARMLIB library, by copying and editing the relevant job in the HZASCUST member in the hza.SHZASAMP data set.
Database performance and tuning
You can perform various configurations to tune your database to provide the best performance for your HCL Z Asset Optimizer environment.
Database resources used by HCL Z Asset Optimizer
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.
Troubleshooting a problem
Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.
You can identify the type of message by the message prefix.
Notices