Home
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.
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.
Configuring a test Repository database
Configuring the test Repository database includes setting up database objects, creating the Global Knowledge Base (GKB) database, and configuring access to the Repository and the GKB databases. Most sites maintain both a test Repository database and a production Repository database. After you configure and validate the test Repository database, repeat this task to create the production Repository database.
Populating the test Repository database with data
You can populate the test Repository database in stages. Begin by collecting and importing Inquisitor and Usage Monitor data on the local LPAR, and then verify that this process is successful before collecting and importing data from other LPARs.
Verifying the results of the data import with the Analyzer
After you complete the collection and import of Inquisitor and Usage Monitor data, use the Analyzer to verify that the import was successful.

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.
- Installation prerequisites
  Before you install HCL Z Asset Optimizer, you need to verify that the required hardware and software are available in the installation environment.
- System configuration requirements
  This section explains tbe system configuration requirements, as well as the names of the zip files you need to install.
- 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.
  - Installing target libraries
    Before you can install HCL Z Asset Optimizer in a production environment, you can create a test environment.
  - Preparing Db2® database prerequisites
    The Db2® environment for the test z/OS® installation has prerequisites that you must configure.
  - Preparing local environment settings
    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.
  - Configuring a test Repository database
    Configuring the test Repository database includes setting up database objects, creating the Global Knowledge Base (GKB) database, and configuring access to the Repository and the GKB databases. Most sites maintain both a test Repository database and a production Repository database. After you configure and validate the test Repository database, repeat this task to create the production Repository database.
    - Creating a test Repository database in Db2®
      Creating the HCL Z Asset Optimizer database includes setting up storage groups, the database name, and the administrator logon details. You also create the Global Knowledge Base (GKB) environment and then grant access to the database.
    - Creating a test Repository database in SQLite
      Creating the test Repository database includes allocating, formatting, and mounting a zFS file system and also granting access to z/OS® OMVS groups. This is followed by creating the database name and administrator logon details.
    - Populating the test Repository database with data
      You can populate the test Repository database in stages. Begin by collecting and importing Inquisitor and Usage Monitor data on the local LPAR, and then verify that this process is successful before collecting and importing data from other LPARs.
      - Collecting and importing data to the test Repository database
        After creating the databases and database objects, you are ready to collect Inquisitor and Usage Monitor data. You can then import the collected data into the test Repository database.
      - Verifying the results of the data import with the Analyzer
        After you complete the collection and import of Inquisitor and Usage Monitor data, use the Analyzer to verify that the import was successful.
      - Collecting and importing data from other systems
        After you verify that all components are correctly installed on the test Repository database, you can now discover and import Inquisitor and Usage Monitor data from other z/OS® logical partitions (LPARs).
  - Configuring a production Repository database
    Most implementations include a test Repository database and a production Repository database. Configuring a production Repository database involves creating the database and importing data, configuring security, and automating data collection activities

Verifying the results of the data import with the Analyzer

After you complete the collection and import of Inquisitor and Usage Monitor data, use the Analyzer to verify that the import was successful.

Procedure

Review the HZASANP1 PARMLIB library settings and modify if necessary.
These settings specify the Z Asset Optimizer administrator user ID and password.
Run the HZASANLO JCLLIB job on the test Repository database.
This job, typically, runs continually but you can enter the F HZASANLO, STOP command to stop it.
On your PC browser, logon to the Analyzer utility with the values specified in member HZASANP1 of PARMLIB library.
Review the Analyzer reports to confirm that all expected products have been identified.
If a product is missing, perform the following tasks to identify the reason why a product is not included:
- Check that the product is in the GKB and report any missing product to HCL support so that they can provide an updated GKB for the product.
- If the product exists in the GKB, check that the product is installed on the test z/OS®. If the product is not installed on the test z/OS®, run the Inquisitor utility on a system where the product is installed and then import that data into the test database.