Welcome
HCL Z Asset Optimizer 9.1
Planning for deployment
Before you deploy HCL Z Asset Optimizer, consider which deployment option is best suited to your environment.
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.

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.
  - Predeployment considerations
    You can deploy HCL 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.
- 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.
- 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

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.

Db2® only: It is recommended that not more than 50 repositories be defined in a Db2® subsystem that is referenced by each Analyzer. This is to prevent overload to the Analyzer and also for easier management of repositories.

You can locate multiple Repositories in one central location, or you can locate them in geographically dispersed locations. Multiple Repositories may be organized as follows:

For a central location
For geographically dispersed locations

Central location

Each Repository contains data that is divided up into logical units, for example:

Data center
Outsourced customer
Sysplex

Each Repository has its own database. For Db2®, all repositories must reside in the same Db2® subsystem. For SQLite, each repository must reside in its own SQLite database. For Db2® only, the advantage of this configuration is that reporting can be performed on data across all repositories. With this configuration, all repositories can share the same Global Knowledge Base (GKB) and you only have to maintain a single copy of the GKB.

Geographically dispersed locations

Each Repository is defined with its own database at a specific geographic site as a stand-alone operation. Reporting can only be performed for each specific Repository. The disadvantage with this configuration is that it can be necessary to consolidate Repository data to a central site for reporting purposes.