Home
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.
Collecting usage data with the Usage Monitor
The Usage Monitor is a server address space that runs as a started task. Work is queued to the Usage Monitor from all address spaces where programs are used. The Usage Monitor moves captured program usage data into the collection repository and periodically writes the accumulated data to a sequential file. The Usage Monitor runs APF authorized and is non-swappable.
Customizing a CICS region to provide usage data

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.
- Updating the Global Knowledge Base
  HCL provides monthly updates to the Global Knowledge Base (GKB) so that you can keep your product inventory definitions up-to-date. You can also submit items to HCL support for inclusion in GKB updates.
- Collecting scanned libraries with the Inquisitor for z/OS
  The Inquisitor is a program that scans and collects information about partitioned data set (PDS) and partitioned data set extended (PDSE) program libraries. The Inquisitor Import program takes the collected data as input to form the basis of your software inventory.
- Collecting UNIX files with the Inquisitor for z/OS UNIX
  The Inquisitor for z/OS® UNIX™ is a program that collects information about executable software existing in HFS and zFS data sets currently mounted and accessible to z/OS UNIX. The Inquisitor Import program takes the collected data as input to form the basis of your z/OS UNIX software inventory.
- Collecting usage data with the Usage Monitor
  The Usage Monitor is a server address space that runs as a started task. Work is queued to the Usage Monitor from all address spaces where programs are used. The Usage Monitor moves captured program usage data into the collection repository and periodically writes the accumulated data to a sequential file. The Usage Monitor runs APF authorized and is non-swappable.
  - Setting up the Usage Monitor
    The Usage Monitor uses the HZASUMON job in the JCLLIB library. This job is generated from the HZASCUST post-installation customization job. This job will call the HZAJMON procedure from the JCLLIB library.
  - Starting and stopping the Usage Monitor
    A Usage Monitor member named HZAJMON is provided in SHZAPROC. If you want to start HZAJMON as a started task, copy the customized member from the JCLLIB to an authorized PROCLIB.
  - Refresh processing for the Usage Monitor
    The Usage Monitor includes commands that you can issue dynamically to alter processing but that are active only for the duration of the current Usage Monitor session. To implement a change to both the running Usage Monitor and to the initialization commands for starting subsequent Usage Monitor sessions, you can use the refresh facility.
  - Usage Monitor commands
  - Monitoring usage in CICS® regions
    The CICS® Transaction Server for z/OS® performs much of its program management outside of the contents supervisor framework that most applications use. For the Usage Monitor to accurately detect and record the use of programs in a CICS region, you must customize each CICS region where you require detailed program usage monitoring.
  - Customizing a CICS region to provide usage data
- Importing Inquisitor data
  The Inquisitor Import reads data from Inquisitor scans, where the data is filtered and matched to products. The filtered, matched data is then copied to the Repository tables where it can be viewed and queried by the Analyzer reporting utility.
- Importing usage data
  The Usage import job imports data generated by the Usage Monitor and aggregates usage data for discovered or identified modules in the Repository tables in the database.
- Aggregating usage and discovery data
  The Aggregator is a program that populates the Asset tables.
- Activating the Automation Server
  The Automation Server discovers new data sets and processes them by starting a set of predefined actions that associate the data with data set name masks that form a catalog search. This search determines if any data set names matching the mask are to be processed.

Customizing a CICS region to provide usage data

Procedure

Copy the appropriate HZAZFTCx and HZAZEIIx global user exit (GLUE) programs from the SHZAMOD1 library to a DFHRPL library of the CICS region.
Customize and submit the HZASENAX job to create a program that enables the HZAZFTCx and HZAZEIIx exit programs:
1. Customize the sample job for translating, assembling, and binding the enabling program that is provided in the HZASENAX member in the customized JCLLIB library.
  For convenience, you can name this program HZAZENAx, where x is the same suffix character as the suffix of the HZAZFTCx and HZAZEIIx programs that it enables.
2. Check that the name specified in the PROGRAM operand of EXEC CICS ENABLE statement is the name of the enabling program.
3. Check that the name specified in EXEC CICS ENABLE PROGRAM statement is the name of the of the GLUE programs.
4. Link the HZAZENAx enabling program into the same DFHRPL library where you copied the HZAZFTCx and HZAZEIIx GLUE programs.
5. Submit the HZAZENAx job.
Add an entry in the following format to the active program library table (PLT) of the CICS Transaction Server to install the HZAZENAx module:
```
DFHPLT TYPE=ENTRY,PROGRAM=HZAZENA
```
Place the entry before the DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM entry to load it early during CICS initialization and minimize the need for program resource definitions.
Ensure that the PLTPI setting for the CICS region specifies your newly updated PLT.
Optional: Use the HZATAGP tagger program to tag non-vendor application programs that you want to be identified in usage reports.

Results

When you complete this task, the use of programs that are given control by various mechanisms in the CICS Transaction Server are attributed to the CICS region address spaces that invoke them.

What to do next

You can stop data collection from all HZAZFTCx and HZAZEIIx glue programs with the CIC(N) Usage Monitor setting. The CIC(Y) option is the default if you do not issue a CIC Usage Monitor command.

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.