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 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
Creating the database
The production Repository database runs on a development logical partition (LPAR), and it is not necessary to run it on a business workload LPAR. You can duplicate the content of test Repository database to populate production Repository database without collecting and importing Inquisitor and Usage Monitor data again.

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.
  - 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
    - Creating the database
      The production Repository database runs on a development logical partition (LPAR), and it is not necessary to run it on a business workload LPAR. You can duplicate the content of test Repository database to populate production Repository database without collecting and importing Inquisitor and Usage Monitor data again.
    - Configuring security
      Resource Access Control Facility (RACF®) security provides authentication, authorization, and auditing control for working with z/OS® systems.
    - Automating data collection and reporting activities
      When you configure the Usage Monitor, the Automation Server, and the Analyzer to run as started tasks, these data collection and reporting activities are automated.
    - Maintaining the production Repository database
      You must perform regular maintenance tasks on the production Repository database to ensure optimal performance. The maintenance tasks cull obsolete and unwanted data and reorganize the database as necessary.

Creating a production Repository database

The production Repository database runs on a development logical partition (LPAR), and it is not necessary to run it on a business workload LPAR. You can duplicate the content of test Repository database to populate production Repository database without collecting and importing Inquisitor and Usage Monitor data again.

About this task

You can create the production Repository database on a Db2® or SQLite database. This procedure combines instructions for both database environments. See Configuring a test Repository database for database-specific instructions.

Procedure

Run the HZASDB01 job.
- For Db2®, the job creates storage groups.
- For SQLite, the job allocates the zFS file system.
Run the HZASDB02 job to create the database objects for the Global Knowledge Base (GKB).
Run the HZASDB03 job to create the Repository database and database objects.
For Db2 databases: Before running the HZASDB03 job, review and change definitions in PARMLIB members HZASSQ17 and HZASSQ18 as needed to meet site requirements:
- In member HZASSQ17 of PARMLIB library, use the MAXPARTITIONS parameter to increase the number of partitions for the three largest table spaces (VMODULE, VUSEMTD, and VPRODDET) according to site requirements.
- In member HZASSQ18 of the PARMLIB library, the COMPRESS keyword is set for all indexes. Bufferpool BP8K0 must first be activated in Db2® before these compressed indexes can be created. Rename and activate different Bufferpool names according to site requirements.
Run the HZASGKBL job to load the GKB.
Run the HZASGRNT job.
- For Db2®, the job grants DBADMIN access to the Z Asset Optimizer administrator for the Repository and GKB databases.
- For SQLite, the job grants access to the z/OS® OMVS groups.
Run the HZASGRTB job.
For Db2®, this job grants SELECT access to database tables.
To populate the production Repository database, repeat the procedure for collecting and importing data that you performed to populate the test Repository database.

What to do next

Configure security for the production Repository database.

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.