Welcome
IBM Z Software Asset Management 9.1
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.
Collecting usage data with the Usage Monitor
The Usage Monitor is a server address space that runs as a started task. Work is queued to the Usage Monitor from all address spaces where programs are used. The Usage Monitor moves captured program usage data into the collection repository and periodically writes the accumulated data to a sequential file. The Usage Monitor runs APF authorized and is non-swappable.
Customizing a CICS region to provide usage data

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.
- 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.
  - Updating the Global Knowledge Base
    IBM Z Software Asset Management provides monthly updates to the Global Knowledge Base (GKB) so that you can keep your product inventory definitions up-to-date. You can also submit items to IBM support for inclusion in GKB updates.
  - Applying Updates to GKB Database Via MHS Website
  - Collecting scanned libraries with the Inquisitor for z/OS
    The Inquisitor is a program that scans and collects information about partitioned data set (PDS) and partitioned data set extended (PDSE) program libraries. The Inquisitor Import program takes the collected data as input to form the basis of your software inventory.
  - Collecting UNIX files with the Inquisitor for z/OS UNIX
    The Inquisitor for z/OS® UNIX™ is a program that collects information about executable software existing in HFS and zFS data sets currently mounted and accessible to z/OS UNIX. The Inquisitor Import program takes the collected data as input to form the basis of your z/OS UNIX software inventory.
  - Collecting usage data with the Usage Monitor
    The Usage Monitor is a server address space that runs as a started task. Work is queued to the Usage Monitor from all address spaces where programs are used. The Usage Monitor moves captured program usage data into the collection repository and periodically writes the accumulated data to a sequential file. The Usage Monitor runs APF authorized and is non-swappable.
    - Setting up the Usage Monitor
      The Usage Monitor uses the HSISUMON job in the JCLLIB library. This job is generated from the HSISCUST post-installation customization job. This job will call the HSIJMON procedure from the JCLLIB library.
    - Starting and stopping the Usage Monitor
      A Usage Monitor member named HSIJMON is provided in SHSIPROC. If you want to start HSIJMON as a started task, copy the customized member from the JCLLIB to an authorized PROCLIB.
    - Refresh processing for the Usage Monitor
      The Usage Monitor includes commands that you can issue dynamically to alter processing but that are active only for the duration of the current Usage Monitor session. To implement a change to both the running Usage Monitor and to the initialization commands for starting subsequent Usage Monitor sessions, you can use the refresh facility.
    - Usage Monitor general commands
    - Usage Monitor Trace Facility
    - IBM CICS® Transaction Server for z/OS®
      The CICS® Transaction Server for z/OS® performs much of its program management outside of the contents supervisor framework that most applications use. For the Usage Monitor to accurately detect and record the use of programs in a CICS region, you must customize each CICS region where you require detailed program usage monitoring.
    - Customizing a CICS region to provide usage data
  - Importing Inquisitor data
    The Inquisitor Import reads data from Inquisitor scans, where the data is filtered and matched to products. The filtered, matched data is then copied to the Repository tables where it can be viewed and queried by the Analyzer reporting utility.
  - Importing Usage data
    The Usage Import job imports data generated by the Usage Monitor and aggregates usage data for discovered or identified modules in the Repository tables in the database.
  - Aggregating usage and discovery data
    The Aggregator is a program that populates the Asset tables.
  - Activating the Automation Server
    The Automation Server discovers new data sets and processes them by starting a set of predefined actions that associate the data with data set name masks that form a catalog search. This search determines if any data sets with names matching the mask are to be processed.
- 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

Customizing a CICS region to provide usage data

Procedure

Copy the appropriate HSIZFTCx and HSIZEIIx global user exit (GLUE) programs from the SHSIMOD1 library to a DFHRPL library of the CICS region.
Customize and submit the HSISENAX job to create a program that enables the HSIZFTCxx and HSIZFTCxx exit programs:
1. Customize the sample job for translating, assembling, and binding the enabling program that is provided in the HSISENAX member in the customized JCLLIB library.
  For convenience, you can name this program HSIZENAx, where x is the same suffix character as the suffix of the HSIZFTCx and HSIZEIIx programs that it enables.
2. Check that the name specified in the PROGRAM operand of EXEC CICS ENABLE statement is the name of the enabling program.
3. Check that the name specified in EXEC CICS ENABLE PROGRAM statement is the name of the of the GLUE programs.
4. Link the HSIZENAx enabling program into the same DFHRPL library where you copied the HSIZFTCx and HSIZEIIx GLUE programs.
5. Submit the HSIZENAx job.
Add an entry in the following format to the active program library table (PLT) of the CICS Transaction Server to install the HSIZENAx module:
```
DFHPLT TYPE=ENTRY,PROGRAM=HSIZENA
```
Place the entry before the DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM entry to load it early during CICS initialization and minimize the need for program resource definitions.
Ensure that the PLTPI setting for the CICS region specifies your newly updated PLT.
Optional: Use the HSITAGP tagger program to tag non-vendor application programs that you want to be identified in usage reports.

Results

When you complete this task, the use of programs that are given control by various mechanisms in the CICS Transaction Server are attributed to the CICS region address spaces that invoke them.

What to do next

You can stop data collection from all HSIZFTCx and HSIZEIIx glue programs with the CIC(N) Usage Monitor setting. The CIC(Y) option is the default if you do not issue a CIC Usage Monitor command.