Welcome
IBM Z Software Asset Management 8.3.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 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.
Running the Inquisitor for z/OS® UNIX® program
The HSISINQU job in the JCLLIB library performs the Inquisitor for z/OS® UNIX® collection. This job is generated from the HSISCUST post-installation customization job.

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.
- 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.
  - Updating the Global Knowledge Base
    IBM 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.
  - 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.
    - Inquisitor for z/OS® UNIX® overview
      The Inquisitor for z/OS® UNIX® produces a set of record types which are different from those produced by the Inquisitor for z/OS. However, both programs collect the same types of information about installed software.
    - Running the Inquisitor for z/OS® UNIX® program
      The HSISINQU job in the JCLLIB library performs the Inquisitor for z/OS® UNIX® collection. This job is generated from the HSISCUST post-installation customization job.
    - Inquisitor for z/OS® UNIX® program parameters and files
      The Inquisitor for z/OS® UNIX® program has mandatory and optional parameters that affect how data is collected. The program uses some mandatory files as well as some optional files.
    - z/OS® UNIX® Inquisitor example
      In this example, the requirement is for a full scan of the file system, but it is known that the DEPLOY 1 product has a vast subdirectory structure containing thousands of files, with the actual software for the product being confined to its bin subdirectory. Accordingly, to reduce unproductive processing the decision is made to exclude the product’s files from the z/OS® UNIX® Inquisitor scan except for its bin subdirectory. The main DEPLOY 1 directory is called deploy1 and it is a subdirectory of the system’s root directory.
    - Security considerations
      If you want to collect all relevant z/OS® UNIX® data, you must have access to all UNIX directories, including the root directory. This access ensures that all z/OS UNIX data is collected.
  - 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.
  - 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.
- 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

Running the Inquisitor for z/OS® UNIX® program

The HSISINQU job in the JCLLIB library performs the Inquisitor for z/OS® UNIX® collection. This job is generated from the HSISCUST post-installation customization job.

About this task

Run-time for this job depends on the size and complexity of the UNIX® directory structure to be scanned. Run this job during off-peak periods.

Procedure

In the HSISINQU job, check the values for the following parameter and change if necessary:
- The PACK parameter is set to 1 to request that zipped output is written using the fastest level of the deflate algorithm. Higher values up to 9 can be used for better compression, but they will use more CPU time. Specify PACK=0 if use of the shrink zip algorithm is required.
- The LLQ parameter is set to Z&SMF. You can change this value if you want to generate data sets with unique names without changing the JCL library. This value is set when the HSISINQU job is submitted.
In the program parameter string, you can specify a report message level, an override to the system identifier, and whether you want compressed or uncompressed output. Use commas to separate the various settings specified within the program parameter string.
Run the HSISINQU job.