Estructura del trabajo

After you have collected raw software inventory data for z/OS and z/OS UNIX using the Surveyor and Extractor components, you are ready to generate an inventory of software products.

3.3.1 Identifying products

The Identifier component is used to generate a software product inventory. The Identifier uses three sets of data as input to generate a software product inventory:

򐂰 The raw software data collected by the Surveyor

򐂰 The CSI data collected by the Extractor

򐂰 The Software Catalog

Chapter 3. IBM Tivoli License Compliance Manager for z/OS 41 Figure 3-5 Identifier flow

Software catalog

The Software Catalog (called the Knowledge Base in the previous version of the IBM Tivoli License Compliance Manager for z/OS) is a proprietary database containing information used to associate objects discovered by the Surveyor with software products. Contents of the Software Catalog include:

򐂰 Vendor information (Vendor Name, Vendor ID, and so on)

򐂰 Product information (Product Name, Product ID, Vendor ID)

򐂰 FMID to Product ID mapping table (for use with data extracted from SMP/E) IBM Software Catalog is constantly updated with new and changed products and vendors, and is released quarterly to customers.

The Identifier uses a set of algorithms to compare the raw software data to the contents of the Software Catalog to produce a software product inventory. This raw software data is used to generate a file of installed software products that includes the vendor name, the fully qualified product name, and the version of the product.

The Identifier produces a data set and a report that contains all of the installed software products. The data set contains names of the z/OS load libraries and z/OS UNIX directories where the product was discovered.

New editions of the Software Catalog are made available four times a year. The product definitions that are contained in the Software Catalog represent the profiles of software products at a point in time. That is, various elements contained in the Software Catalog will become superseded or replaced. This is because software products are not static. For example, product names change, new versions of products become available, vendors acquire and divest software products, and new load module names attributed to a software product.

There are four optional data sets that you can include in an Identifier run to further adjust, enhance, and influence product identification to achieve your goals:

򐂰 User product data (USRPDATA)

򐂰 Software customization tool (SCCUT)

򐂰 Reference identification file (RIF)

򐂰 Signature Software Catalog

User product data (USRPDATA)

Since new editions of the Software Catalog are made available approximately every calendar quarter, there may be instances when you need to adjust various elements that define the individual software products that are not yet contained in your edition of Software Catalog. You may want to modify various elements of the software products contained in the Software Catalog to conform to your local tracking and licensing of software products. The Software Catalog contains definitions of commercially available software products. You may have the need to have the License Compliance Manager for z/OS track internally developed applications and utilities.

The user product data (USRPDATA) statements provide you with the mechanism to make adjustments to product identification. The USRPDATA statements enable you adjust and influence software product identification to fit your enterprise requirements. Some of the adjustments that you can make to product identification include:

򐂰 Define new products not contained in the Software Catalog

򐂰 Change the external name of software products

򐂰 Attribute a software product to a different vendor

򐂰 Define locally developed applications and utilities

To use the facility to influence product identification, you include the appropriate USRPDATA statements that you develop in the particular run of the Identifier.

Chapter 3. IBM Tivoli License Compliance Manager for z/OS 43 There are some things to consider when using USRPDATA statements to influence product identification:

򐂰 The USRPDATA statements do not alter the contents of the Software Catalog.

򐂰 The changes that you make using USRPDATA statements are contained only in the output from the Identifier - the Identifier data set and the Identifier report.

򐂰 You run as many iterations of the Identifier using the USRPDATA statements as necessary to achieve your product identification goal.

Software Customization Tool (SCCUT)

Another option that is available to you to adjust and influence software product identification, is the Software Customization Tool (SCCUT). SCCUT enables you to change product identification in much the same way as USRPDATA with one major difference - SCCUT applies your changes to the Software Catalog. The input statements to SCCUT are similar in format and content to USRPDATA statements. The SCCUT component provides you with a safeguard by

generating a copy of the Software Catalog. The end result of an SCCUT run is a Software Catalog that contains your changes defined by the SCCUT statements, a copy of the Software Catalog without your changes, and a report detailing your changes. The theory for and reasons why to use USRPDATA and SCCUT are the same, the difference is that SCCUT applies permanent changes to a copy of the Software Catalog.

Reference identification file (RIF)

Many enterprises choose to centrally install software on a base system and then roll out or clone the base system to deploy the software on subordinate systems.

This process results in effectively replicating the same set of base system software on all of the subordinate systems. When the Identifier has identified a set of modules in one library as belonging to a particular product-version-release, that identification is available for reference in the identification of the same set of modules in other libraries. Use of the reference identification file (RIF) will help ensure consistent software product identification across the enterprise.

Signature Software Catalog

The Software Catalog contains several releases/versions of products with their modules and module signatures. It is used to perform version identification.