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.

There is no dependency on any other middleware components. For example, no dependency exists on the HTTP Server, WebSphere® Application Server, or Java™.

The Analyzer has been designed with minimal prerequisites. These are:
  • The Analyzer must be run on the same z/OS® host as the Db2® subsystem or SQLite database that contains the HCL Z Asset Optimizer repositories.
  • The user ID of the Analyzer address space must have previously been granted access to the databases. See the HZASGRNT job in the JCLLIB for sample JCL to grant access.
  • When running the Analyzer in the online mode, you need access to a TCP/IP port. The default is port 9000.
  • When running the Analyzer in online mode with SECURITY=SYSTEM, the Analyzer SHZAMOD1 load library must be defined to the z/OS® Authorized Program Facility (APF). In addition, all data sets in the Analyzer STEPLIB, or JOBLIB DD concatenation, must be defined to APF.
  • You can run the Analyzer in online mode while Inquisitor Import or Usage Import is also updating data into the repositories. However, the Analyzer reports may not display the correct information on the latest updates due to concurrency issues in Db2®. To ensure that the latest correct information is displayed, do not run operational jobs that update data in the repositories while users are running reports with the Analyzer. This is not an issue for the SQLite database, as only single thread is allowed.