Welcome
IBM Z Software Asset Management 8.3.1
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.
Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites
This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.

IBM Z Software Asset Management 8.3.1
- Program Directory
- PDF manual
- 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.
- 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.
- 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.
  - Scenario 1: Implementing a single Repository database with a single GKB database
    The most common deployment scenario is an implementation with a single Repository database and a single global knowledge base (GKB) database.
  - Scenario 2: Implementing multiple Repositories with a shared GKB database
    This deployment scenario implements two Repositories in a single Db2® subsystem that share a single global knowledge base (GKB) database. The advantage of sharing the same GKB is that you need only apply monthly updates to a single GKB database.
  - Scenario 3: Implementing multiple Repositories with multiple GKB databases
    This deployment scenario implements two Repositories in a single Db2® subsystem, each with its own global knowledge base (GKB) database. This deployment scenario is not common because you must apply monthly updates to each GKB database.
  - Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites
    This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.
  - Scenario 5: Implementing in a sysplex environment
    This deployment scenario is for a sysplex environment, where the DASD is fully shared across all z/OS® LPARs that belong to the sysplex. This special deployment is similar to the deployment scenarios 1, 2, or 3, but the implementation steps are slightly different. This approach is intended to achieve operational efficiency by processing only a single z/OS LPAR within a sysplex.
- Migrating to IBM Z Software Asset Management 8.3.1
  When you migrate to the latest version of IBM Z Software Asset Management 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.
- REST API
- Running utilities
  IBM Z Software Asset Management provides utilities that you run to perform routine functional tasks to maintain the product lifecycle.
- Configuring language support
  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.
Notices

Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites

This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.

Procedure

At the remote site, install the target libraries.
Customize an instance of the HSISCUST member in the hsi.SHSISAMP data set with the following parameter:
```
DBTYPE=REMOTE
```
Submit the HSISCUST job.
Collect Inquisitor and Usage Monitor data and transfer the files to the central site for processing:
1. Run the HSISINQZ job on all z/OS® LPARs to collect Inquisitor data.
2. Run the HSISINQU job on all z/OS® LPARs to collect Inquisitor data for UNIX®.
3. Run the HSISUMON job on all z/OS® LPARs to collect usage data.
4. Transfer the collected Inquisitor and Usage Monitor data to the central site using file transfer protocol (FTP).