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 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.
Populating the test Repository database with data
You can populate the test Repository database in stages. Begin by collecting and importing Inquisitor and Usage Monitor data on the local LPAR, and then verify that this process is successful before collecting and importing data from other LPARs.
Collecting and importing data from other systems
After you verify that all components are correctly installed on the test Repository database, you can now discover and import Inquisitor and Usage Monitor data from other z/OS® logical partitions (LPARs).

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.
      - Creating a test Repository database in Db2®
        Creating the IBM Z Software Asset Management database includes setting up storage groups, the database name, and the administrator logon details. You also create the Global Knowledge Base (GKB) environment and then grant access to the database.
      - Creating a test Repository database in SQLite
        Creating the test Repository database includes allocating, formatting, and mounting a zFS file system and also granting access to z/OS® OMVS groups. This is followed by creating the database name and administrator logon details.
      - Populating the test Repository database with data
        You can populate the test Repository database in stages. Begin by collecting and importing Inquisitor and Usage Monitor data on the local LPAR, and then verify that this process is successful before collecting and importing data from other LPARs.
        Collecting and importing data to the test Repository database
        After creating the databases and database objects, you are ready to collect Inquisitor and Usage Monitor data. You can then import the collected data into the test Repository database.
        Verifying the results of the data import with the Analyzer
        After you complete the collection and import of Inquisitor and Usage Monitor data, use the Analyzer to verify that the import was successful.
        Collecting and importing data from other systems
        After you verify that all components are correctly installed on the test Repository database, you can now discover and import Inquisitor and Usage Monitor data from other z/OS® logical partitions (LPARs).
    - 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.
- 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

Collecting and importing data from other systems

After you verify that all components are correctly installed on the test Repository database, you can now discover and import Inquisitor and Usage Monitor data from other z/OS® logical partitions (LPARs).

Procedure

Run the following jobs to collect Inquisitor and Usage data from other systems:
1. Run the HSISINQZ job to scan all other LPARs and generate output to the hsiinst.HSIPZIP.Z&SMF data set.
2. Run the HSISINQU job and generate output to the hsiinst.HSIUZIP.U&SMF file.
3. Run the HSISUMON job to start the Usage Monitor as a batch job on the other LPARS.
Transfer collected data to the central site via file transfer protocol (FTP).
Run the following jobs to import Inquisitor and Usage data at the central site:
1. Run the HSISIQIM job to import Inquisitor data from the hsiinst.HSIPZIP.Z&SMF and hsiinst.HSIUZIP.U&SMF data sets for each LPAR.
2. Run the HSISUIMP job to import Usage data from the hsiinst.UM&SMF.D*.T* data set for each LPAR.