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.
- Running utilities
  HCL Z Asset Optimizer provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
- REST API
  - Prerequisites
  - Installing the REST API
    This topic describes the steps to install REST API.
  - Authorization
  - HTTPS
  - Graceful Server Shutdown Via SDSF
  - End Points
    In this section, let us discuss the end points in detail.
- 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

Authorization

The API uses RACF as the authentication system. Credentials should be provided using the Basic scheme in each request. Basic Authentication (Basic Auth) is a simple authentication scheme built into the HTTP protocol. It works by sending the user credentials — a username and password, separated by “:” — encoded in Base64 within the Authorization header of each HTTP request.

The configurator will prompt whether to have the RACF service case sensitive or not. If is set as case sensitive then credentials are passed to racf as is without modifying, allowing for use of passphrases up to 256 characters. If instead is set a non case sensitive, then both username and password are turned into uppercase characters, allowing for a password of at most 8 characters.

Errors and Workarounds

In the logs each call to RACF returns a 20 error code: This means that the service executable used to query RACF is not APF Authorized. In order to fix this problem you can run extattr +a bin/racfexec from your installation folder. To verify that the APF attribute is set, run ls -E bin/from the installation directory, and check that the a attribute is set.

If the attributes is set but still see missing APF authorization verify that the HFS where the API reside is mounted with the SETUID options set to true.