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.

Before you deploy HCL Z Asset Optimizer, consider which deployment option is best suited to your environment.

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.

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.

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.

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.

The primary reporting facility in HCL Z Asset Optimizer is the Analyzer.

HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.

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 includes messages, repository table layouts, and performance and tuning.

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.

You can identify the type of message by the message prefix.

Messages generated during batch processing are explained in detail here.

In this section, we will discuss the Customization process in detail.

In this section, we will discuss the detail process to login.