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.
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).

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, 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.
  - 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

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).

Procedure

Run the following jobs to collect Inquisitor and Usage data from other systems:
1. Run the HZASINQZ job to scan all other LPARs and generate output to the hzainst.HZAPZIP.Z&SMF file.
2. Run the HZASINQU job and generate output to the hzainst.HZAUZIP.U&SMF file.
3. Run the HZASUMON job to start the Usage Monitor as a batch job on the other LPARS.
Transfer collected data to the central site via file transfer protocol (FTP).
Run the following jobs to import Inquisitor and Usage data at the central site:
1. Run the HZASIQIM job to import Inquisitor data from the hzainst.HZAPZIP.Z&SMF and hzainst.HZAUZIP.U&SMF files for each LPAR.
2. Run the HZASUIMP job to import Usage data from the hzainst.UM&SMF.D*.T* file for each LPAR.

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.