Welcome
IBM Z Software Asset Management 9.1
Installing and customizing IBM Z Software Asset Management
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.
Checklist of installation and customization tasks
This checklist includes a set of procedures for installing the product, creating a test database, populating data, and validating the test installation. When you complete these procedures, you are ready to create a production environment for IBM Z Software Asset Management.
Configuring a production Repository database
Most implementations include a test Repository database and a production Repository database. Configuring a production Repository database involves creating the database and importing data, configuring security, and automating data collection activities.
Maintaining the production Repository database
You must perform regular maintenance tasks on the production Repository database to ensure optimal performance. The maintenance tasks cull obsolete and unwanted data and reorganize the database as necessary.

IBM Z Software Asset Management 9.1
- PDF manual
- Program Directory
- Product overview
  IBM Z Software Asset Management 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 IBM Z Software Asset Management core architecture.
- Planning for deployment
  Before you deploy IBM Z Software Asset Management , consider which deployment option is best suited to your environment.
- Implementing deployment scenarios
  Most implementations of IBM Z Software Asset Management 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 IBM Z Software Asset Management
  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.
  - Installation prerequisites
    Before you install IBM Z Software Asset Management, verify that the required hardware and software are available in the installation environment.
  - System configuration requirements
  - Security and authorization requirements
    A z/OS® user ID with appropriate RACF® access is required to submit the batch jobs used in the customizing and operation of IBM Z Software Asset Management. Additional security and authorization configurations can be necessary, depending on your environment.
  - Checklist of installation and customization tasks
    This checklist includes a set of procedures for installing the product, creating a test database, populating data, and validating the test installation. When you complete these procedures, you are ready to create a production environment for IBM Z Software Asset Management.
    - Installing target libraries
      Before you can install IBM Z Software Asset Management in a production environment, you can create a test environment.
    - Preparing Db2® database prerequisites
      The Db2® environment for the test z/OS® installation has prerequisites that you must configure.
    - Preparing local environment settings
      After installation, you can create a custom version of any job in the JCLLIB library or any parameter in the PARMLIB library, by copying and editing the relevant job in the HSISCUST member in the hsi.SHSISAMP data set.
    - Configuring a test Repository database
      Configuring the test Repository database includes setting up database objects, creating the Global Knowledge Base (GKB) database, and configuring access to the Repository and the GKB databases. Most sites maintain both a test Repository database and a production Repository database. After you configure and validate the test Repository database, repeat this task to create the production Repository database.
    - Configuring a production Repository database
      Most implementations include a test Repository database and a production Repository database. Configuring a production Repository database involves creating the database and importing data, configuring security, and automating data collection activities.
      - Creating a production Repository database
        The production Repository database runs on a development logical partition (LPAR), and it is not necessary to run it on a business workload LPAR. You can duplicate the content of test Repository database to populate production Repository database without collecting and importing Inquisitor and Usage Monitor data again.
      - Configuring security for the production Repository database
        Resource Access Control Facility (RACF®) security provides authentication, authorization, and auditing control for working with z/OS® systems.
      - Automating data collection and reporting activities
        When you configure the Usage Monitor, the Automation Server, and the Analyzer to run as started tasks, these data collection and reporting activities are automated.
      - Maintaining the production Repository database
        You must perform regular maintenance tasks on the production Repository database to ensure optimal performance. The maintenance tasks cull obsolete and unwanted data and reorganize the database as necessary.
- Migrating to IBM Z Software Asset Management 9.1
  When you migrate to the latest version of IBM Z Software Asset Management 9.1 from an earlier version, you must convert existing data to be compatible with your new environment.
- Collecting and importing data with IBM Z Software Asset Management
  IBM Z Software Asset Management 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 IBM Z Software Asset Management is the Analyzer.
- Running utilities
  IBM Z Software Asset Management provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
- REST API
- Configuring Language support
  IBM Z Software Asset Management 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 IBM Z Software Asset Management
  Reference information includes messages, repository table layouts, and performance and tuning.
- Troubleshooting and support
  To isolate and resolve problems with your IBM 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 IBM products.
- IBM Z Software Asset Management messages
  You can identify the type of message by the message prefix.
- Description of output message content
  Messages generated during batch processing are explained in detail here.
IBM Z Software Asset Management Container 9.1
Notices

Maintaining the production Repository database

You must perform regular maintenance tasks on the production Repository database to ensure optimal performance. The maintenance tasks cull obsolete and unwanted data and reorganize the database as necessary.

About this task

A database administrator or system programmer performs these maintenance tasks.

Procedure

Run the following jobs on a regular basis to delete obsolete data, save space, and improve processing time:
1. Run the HSISUDEL job to delete usage data that are older than a specified period.
2. Run the HSISLDEL job to delete obsolete discovery and usage data for a specified system (LPAR).
3. Run the HSISPDEL job to physically delete data for all systems.
4. Run the HSISMDEL job to delete obsolete audit records that are older than a specified period.
Run the following jobs on a regular basis to maintain the integrity and performance of data in the production Repository database:
1. Run the HSISUT01 job to backup the Repository database in Db2® or backup the zFS file system in SQLite.
2. Run the HSISUT02 job to restore the Repository database in Db2® or restore the zFS file system in SQLite.
3. Run the HSISUT03 job to reorganize the Repository database in Db2®.
4. Run the HSISUT04 job to update RUNSTATS statistics for the Repository database in Db2®.