Deployment data processes

HCL Z Asset Optimizer is structured on several key data processes.

Inquisitor data
The Inquisitor scans DASD volumes for libraries containing load modules and HFS/zFS files for z/OS® UNIX™ program objects and produces Inquisitor data. These load modules and program objects are matched and associated to a particular vendor and product and the matched information is then loaded into the Repository tables. These processes are performed by running the Inquisitor Import job.
Usage event
A usage event describes a unique load of a load module or program object for an address space that can contain an account code. The Usage Monitor records these usage events as they occur on a particular operating system. After the usage data is imported into the Repository, each usage event is identified by the load module name, library name, and volume. It can then be associated to a particular product discovered on that system.
Repository
The Repository is a collection of database tables that contain processed Inquisitor and Usage Monitor data. To ensure that accurate data is stored in the Repository tables, the following criteria must be met:
  • The DASD VOLSERs of the data being imported must be unique unless the DASD VOLSERs are shared or are clones of each other with identical contents.
  • The data imported must be from systems with unique SMF IDs.

When you are designing the scope of a Repository, there are a few common scenarios that most installations fit into. It is common to define the scope of a Repository based upon a data center. In this scenario, each data center in the organization has a separate Repository.

CAUTION: Import only DASD volumes with a unique VOLSER into your Repository.

The only way to prevent this sharing from taking place is to divide the z/OS® systems with conflicting DASD/SMF IDs into separate Repositories. This can entail running one Repository for each sysplex or stand-alone z/OS® system. With HCL Z Asset Optimizer, it is common for IT service providers to define separate Repositories for each customer. This definition also satisfies the need for separation of data and ease of reporting.

It is recommended to have a central Db2® subsystem or SQLite databases that contain all the Repositories in your entire enterprise. The usage and Inquisitor data that require processing should be transmitted to this central Db2® subsystem or SQLite database by using the HCL Z Asset Optimizer Automation Server or equivalent automation product.