Welcome
HCL Z Asset Optimizer 9.1
Reporting with the Analyzer
The primary reporting facility in HCL Z Asset Optimizer is the Analyzer.
Running the Analyzer in online mode
The primary reporting facility in HCL Z Asset Optimizer is the Analyzer. You can use the Analyzer in online mode to view reports, run queries, and drill down to related reports.

HCL Z Asset Optimizer 9.1
- PDF manual
- Program Directory
- Product overview
  HCL Z Asset Optimizer is built on the concept of remote and central mainframe components which work together to produce reports on z/OS® mainframe products and their usage. This section provides you with a high-level overview of the HCL Z Asset Optimizer core architecture.
- Planning for deployment
  Before you deploy HCL Z Asset Optimizer, consider which deployment option is best suited to your environment.
- Implementing deployment scenarios
  Most implementations of HCL Z Asset Optimizer are based on one of the common deployment scenarios. An example is provided for implementing each of these common deployment scenarios with a Db2® Repository database. You can adapt an example for use with an SQLite Repository database.
- 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.
- Migrating to HCL Z Asset Optimizer 9.1
  When you migrate to the latest version of HCL Z Asset Optimizer 9.1 from an earlier version, you must convert existing data to be compatible with your new environment.
- 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.
- Reporting with the Analyzer
  The primary reporting facility in HCL Z Asset Optimizer is the Analyzer.
  - Analyzer prerequisites
    The Analyzer uses the Db2® Call Library Interface (ODBC/CLI), also used by the Inquisitor Import, Usage Import and other batch components, and the z/OS® socket application programming interface. For the SQLite database, the Analyzer uses an internal ODBC interface.
  - Analyzer JCLLIB and PARMLIB members
    Several JCLLIB and PARMLIB members are used when you run the Analyzer to generate reports.
  - Running the Analyzer in online mode
    The primary reporting facility in HCL Z Asset Optimizer is the Analyzer. You can use the Analyzer in online mode to view reports, run queries, and drill down to related reports.
    - Analyzer communication port
      The Analyzer communication port is defined by using the HTTPPORT setting.
    - Analyzer inactivity timeout
      The Analyzer communication inactivity timeout is defined by using the INACTIVITY_TIMEOUT setting.
    - Analyzer security
      You can view Analyzer reports in a web browser, such as Firefox, and you can communicate with the Analyzer utility to perform interactive queries.
    - Analyzer BASIC security
      HZASANP1 in the PARMLIB defines basic user ID security settings for running the Analyzer.
    - Analyzer SYSTEM and SYSTEM-TLS security
      HZASANP2 in the PARMLIB defines the security settings for running the Analyzer.
    - SSL Certificates
      When the Analyzer is running with SYSTEM=SECURITY, you must have an SSL Certificate defined in your SAF/RACF® security system. You can either generate your own certificate, or connect to an existing certificate.
    - Online login to the Analyzer
      With the Analyzer reporting utility, you can log in with a browser to gain access to the Analyzer Asset, Discovery, and Administration reports and to any Custom reports that you create.
    - Controlling the Analyzer address space
      The Analyzer supports the STOP, REFRESH, and TRACE z/OS® modify commands.
  - Running the Analyzer in batch mode
    If you want to automate report generation, you can run the Analyzer in batch mode.
- Running utilities
  HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
- REST API
- Configuring Language support
  HCL Z Asset Optimizer includes Japanese language support for MVS™ Message Service (MMS) message information. You can also configure the Analyzer utility to create and view reports in Japanese.
- Reference information for HCL Z Asset Optimizer
  Reference information includes messages, repository table layouts, and performance and tuning.
- Troubleshooting and support
  To isolate and resolve problems with your HCL software, you can use the troubleshooting, messages, and support information. This information contains instructions for using the problem determination resources that are provided with your HCL products.
- HCL Z Asset Optimizer messages
  You can identify the type of message by the message prefix.
- Appendix A: Description of output message content
  Messages generated during batch processing are explained in detail here.
- Notices
HCL Z Asset Optimizer Container 9.1

Running the Analyzer in online mode

The primary reporting facility in HCL Z Asset Optimizer is the Analyzer. You can use the Analyzer in online mode to view reports, run queries, and drill down to related reports.

About this task

Note:

Db2® only: It is recommended that not more than 50 repositories be defined in a Db2® subsystem that is referenced by each Analyzer. This is to prevent overload to the Analyzer and also for easier management of repositories.

Some Analyzer reports may require extensive searches and sorts. For performance reasons, increase the sizes of the tablespaces belonging to the work file database and, also consider using different definitions for the Bufferpool (instead of the default BP0 or BP32K).

Db2® only:

The Db2® subsystem must first be active before starting up the Analyzer. After the Analyzer starts, it needs to access the Db2 Catalogs to obtain the list of repositories. If the Db2® subsystem is not active, the error message below appears in the Analyzer job log.

13:15:09(0) COULD NOT QUERY SYSIBM.SYSTABLES FOR REPOSITORY - 
SQLAllocHandle for connection handle failed - rc -1                                                      
{DB2 FOR OS/390}{ODBC DRIVER}  SQLSTATE=58004  ERRLOC=2:56:9  
  CAF "CONNECT" failed using DB2 system:DSN1                  
  RC=08 and REASON=00f30012

The Db2® subsystem can be stopped while the Analyzer is still active, but it will remain in a wait state. If a user logs in and tries to access a repository, the error message below will appear on the Analyzer report. When the Db2® subsystem is next started, users can login again and will automatically re-establish connection to Db2®.
```
SQLAllocHandle for connection handle failed
 - rc -1
{DB2 FOR OS/390}{ODBC DRIVER}  SQLSTATE=58004  ERRLOC=2:56:9
  CAF "CONNECT" failed using DB2 system:DSN1
  RC=08 and REASON=00f30012         
```

HZASANLO job in the JCLLIB is used to run Analyzer in online mode as a batch job.

//HZASANLO EXEC HZAJANLO,TPARAM=HZASANP1

To run the Analyzer in online mode as a Started Task, copy the HZAJANLO from the JCLLIB to a system PROCLIB data set. Here is a sample for running the started task in a Db2® subsystem.

When the Analyzer is run with online mode, configuration options must be defined in the TPARAM DD, including the communication port, security mode, and inactivity timeout.