Version 4 - IBMpublib.boulder.ibm.com/tividd/td/ITLCMfzOS/GC32-2266-00/... · 2006-01-24 · † Chapter 3. Upgrading from Version 3.2 Explains how to upgrade IBM Tivoli License Compliance

IBM
Tivoli®
IBM Tivoli License Compliance Manager for z/OS

Version 4.1

Installation Guide

GC32-2266-00

12

1

2

IBM
Tivoli®
IBM Tivoli License Compliance Manager for z/OS

Version 4.1

Installation Guide

GC32-2266-00

12

1

First Edition, January 2006

This edition applies to version 4.1 of IBM Tivoli License Compliance Manager for z/OS (product number 5698-A86) and to all subsequent releases and modifications until otherwise indicated in new editions.

IBM welcomes your comments.

Address your comments to:IBM License Compliance Management Information Development330 Seventh AvenueNew York, NY 10001U.S.A.

© Copyright International Business Machines Corporation 2006. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

2

Before using this information and the product it supports, read the information under Notices on page 25.

Note

Contents

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho should read this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiConventions in the guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiPublications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Accessing publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiOrdering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Tivoli technical training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixContacting software support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Determining the business impact of your problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xDescribing your problem and gathering background information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xSubmitting your problem to IBM software support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xSearching Knowledge Bases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Search the information center on your local system or network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiSearch the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Obtaining fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiUpdating support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1. Concepts and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Components and data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Base components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Customization components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Chapter 2. Installing IBM Tivoli License Compliance Manager for z/OS . . . . . . . . . . . . . . . 5Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Data set naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Installing IBM Tivoli License Compliance Manager for z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Step 1: Authorize the Surveyor and Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Step 2: Pre-allocate Surveyor and Monitor data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Step 3: Enable security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Step 4: Modify the execution JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Modify the JCL for an SMS environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Choose a method to execute the Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Choose a method to empty usage data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Step 5: Install the ISPF interface (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Verify the ISPF interface library names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Step 6: Install Spotlight+ (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Chapter 3. Upgrading from Version 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Data set upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11UPGRADER job stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Copyright © 2006 v

Chapter 4. Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installing an enhanced Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15AUDINFO load module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Collecting Monitor diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Applying maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Information checklist for reporting problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Appendix A. JCL Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Appendix B. Disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Surveyor data set (SURVDATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Extractor data set (UPDATXOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Work data sets SYSWORK2 through SYSWORKB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Monitor data sets (MONDTLxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Sort work data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Usage work data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Distiller data sets (DISTOUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

vi IBM Tivoli License Compliance Manager for z/OS Installation Guide

About this guide

This guide describes how to install and maintain IBM Tivoli License Compliance Manager for z/OS Version 4.1.

This guide contains the following chapters:• Chapter 1. Concepts and terminology

Describes the key components and data sets of IBM Tivoli License Compliance Manager for z/OS.

• Chapter 2. Installing IBM Tivoli License Compliance Manager for z/OS

Provides the installation procedures.• Chapter 3. Upgrading from Version 3.2

Explains how to upgrade IBM Tivoli License Compliance Manager for z/OS.• Chapter 4. Maintenance

Describes how to maintain the IBM Tivoli License Compliance Manager for z/OS product.

• Appendix A. JCL Library

Lists the members of IBM Tivoli License Compliance Manager for z/OS JCL library.

• Appendix B. Disk space requirements

Provides the guidelines for estimating the sizes of various data sets.

Who should read this book

This book is intended for system administrators and operation personnel who are responsible for setting up the license compliance management environment.

Conventions in the guide

This guide uses the following conventions in diagrams:

Copyright © 2006 vii

When referring to syntax, this guide uses the following conventions:

Publications

The IBM Tivoli License Compliance Manager for z/OS documentation describes the concepts, methods, and procedures needed to help generate and manage the software inventory information. The related documentation includes the following documents:• IBM Tivoli License Compliance Manager for z/OS Version 4.1 Installation

Guide• IBM Tivoli License Compliance Manager for z/OS Version 4.1 Administration

Guide

Accessing publications

The IBM Tivoli License Compliance Manager for z/OS Version 4.1 documentation CD contains all documents for this release in the PDF format. To access the publications from the web, open http://publib.boulder.ibm.com/tividd/td/tdprodlist.html.

IBM posts publications for this and all other Tivoli products to the Tivoli Software Information Center Web site. To access the Tivoli Software Information Center, go to the following Web address:

www.ibm.com/software/tivoli/library/

Ordering publications

You can order the IBM Tivoli License Compliance Manager for z/OS documentation from online web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone at the following numbers:• In the United States: 800-879-2755• In Canada: 800-426-4968

UPPERCASE TYPE Commands or syntax that you must enter exactly as shown, e.g., //DISTILL EXEC DISTILLR

Italic Emphasis of words; variables and values you must provide; citations of titles and chapters of books, diskettes, and CDs

Bold Column headings in a table; keywords

viii IBM Tivoli License Compliance Manager for z/OS Installation Guide

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: www.ibm.com/software/tivoli/education/

Contacting software support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:• For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage® in one of the following ways:– Online: Go to the Passport Advantage Web page and click How to Enroll.

The Web address is the following:www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home

– By phone: For the phone numbers to call in your country, go to the IBM Software Support Web site (techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region.

• For IBM eServer™ software products (including, but not limited to, DB2 and WebSphere products that run in zSeries®, pSeries®, and iSeries™ environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web page (www.ibm.com/servers/eserver/techsupport.html).

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contact page of the IBM Software Support Handbook on the Web (techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location.

Follow the steps in the topic to contact IBM Software Support:1. “Determine the business impact of your problem” on page x.2. “Describe your problem and gather background information” on page x.3. “Submit your problem to IBM Software Support” on page x.

About this guide ix

Determining the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:

Describing your problem and gathering background information

When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: • What software versions were you running when the problem occurred? • Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information. • Can the problem be recreated? If so, what steps led to the failure? • Have any changes been made to the system? (For example, hardware,

operating system, networking software, and so on.) • Are you currently using a workaround for this problem? If so, please be

prepared to explain it when you report the problem.

Submitting your problem to IBM software support

You can submit your problem in one of the two ways:• Online: Go to the “Submit and track problems” page on the IBM Software

Support site (www.ibm.com/software/support/probsub.html). Enter your information into the appropriate problem submission tool.

• By phone: For the phone number to call in your country, go the contacts page of the IBM Software Support Handbook on the Web (techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions.

For more information about problem resolution, see the following sections “Searching Knowledge Bases” and “Obtaining fixes”.

Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.

Severity 2 Significant business impact: The program is usable but is severely limited.

Severity 3 Some business impact: The program is usable with less significant features (not critical to operations) unavailable.

Severity 4 Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.

x IBM Tivoli License Compliance Manager for z/OS Installation Guide

Searching Knowledge Bases

If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available Knowledge Bases to determine whether the resolution to your problem is already documented.

Search the information center on your local system or network

IBM provides extensive documentation that can be installed on your local machine or on an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, reference information, and support documents.

Search the Internet

If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. To search multiple Internet resources for your product, expand the product folder in the navigation frame to the left and select Support on the Web. From this topic, you can search a variety of resources including: • IBM technotes• IBM downloads• IBM Redbooks™

• IBM DeveloperWorks• Forums and newsgroups• Google

Obtaining fixes

A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site: 1. Go to the IBM Software Support Web site (www.ibm.com/software/support). 2. Under Products A - Z, select your product name. This opens a product-specific

support site. 3. Under Self help, follow the link to Search all Downloads, where you will find

a list of fixes, fix packs, and other service updates for your product. For tips on refining your search, click Search tips.

4. Click the name of a fix to read the description and optionally download the fix.

To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps: 1. From the support page for any IBM product, click My support in the

upper-right corner of the page. 2. If you have already registered, skip to the next step. If you have not registered,

click register in the upper-right corner of the support page to establish your user ID and password. 3. Sign in to My support.

3. On the My support page, click Edit profiles in the left navigation pane, and scroll to Select Mail Preferences. Select a product family and check the appropriate boxes for the type of information you want.

About this guide xi

4. Click Submit. 5. For e-mail notification for other products, repeat Steps 4 and 5.

For more information about types of fixes, see the Software Support Handbook (techsupport.services.ibm.com/guides/handbook.html).

Updating support information

Information centers typically include one or more support information plug-ins. These plug-ins add IBM technotes and other support documents to the information center. The following steps describe how to update your support information plug-ins:1. Go to the IBM Software Support Web site (www.ibm.com/software/support). 2. Under Products A - Z, select your product name. This opens a product-specific

support site. 3. Under Search support for this product, type the keyword phrase:

com.ibm.support. Click the Download check box, and click Submit. 4. Check the search results for updates to support information plug-ins. All

support information plug-ins follow the naming convention, “com.ibm.support.product.doc”. If an update is available, select it from the list and view the download instructions.

5. Save the attached zip file to a temporary location on your hard drive. 6. Unzip the downloaded file, making sure that you retain the subfolders. 7. From the location where you unzipped the file, copy the support information

plug-in folder to your Eclipse plug-ins folder. For example, if your IBM software product is installed at c:\IBM\WebSphere\, copy the updated plug-in folder (com.ibm.support.product.doc) to c:\IBM\WebSphere\eclipse\plugins.

8. To see the updated support information, start the information center (or shut it down and restart it), and expand the Support information node in the navigation tree.

xii IBM Tivoli License Compliance Manager for z/OS Installation Guide

Chapter 1. Concepts and terminology

This chapter describes the key concepts of components and data sets of IBM Tivoli License Compliance Manager for z/OS and their terminology.

Components and data sets

The following figure shows the key user components of IBM Tivoli License Compliance Manager for z/OS and data sets needed to produce and view inventory and usage data.

Base components

The following are the IBM Tivoli License Compliance Manager for z/OS base components.

Monitor

The Monitor determines which load modules on your system are being used.

Surveyor

The Surveyor produces an inventory of the load libraries that are present and the load modules they contain by examining the DASD on your system.

Copyright © 2006 1

Extractor

The Extractor provides information to identify IBM products by their product numbers and versions, by extracting relevant information from SMP/E data sets.

Knowledge Base

The Knowledge Base is a comprehensive list of product names and detailed information about selected associated load modules.

Identifier

The Identifier uses the Knowledge Base load library inventory collected by the Surveyor, and, optionally, USRPDATA, the Reference Identifier File and information from the Extractor, to produce an inventory of all your system’s products.

Reporter

The Reporter uses the software product inventory data produced by the Identifier and the usage data produced by the Monitor to produce reports about inventory and usage information.

Exporter

The Exporter uses the software product inventory data produced by the Identifier and the usage data produced by the Monitor to produce sequential data sets that you can use with analysis tools and reporting programs (such as SAS).

Distiller

The Distiller uses the software product inventory data produced by the Identifier and the usage data produced by the Monitor to produce a file for Spotlight+.

Spotlight+

Spotlight+ is a Windows-based application that provides enterprise-wide display and reporting of the inventory and usage information generated by IBM Tivoli License Compliance Manager for z/OS.

Customization components

The following are the IBM Tivoli License Compliance Manager for z/OS customization components.

User Product Data File

The User Product Data File (USRPDATA) allows you to temporarily supplement or override the information in the Knowledge Base.

Knowledge Base Customization Tool

The Knowledge Base Customization Tool allows you to make permanent changes to the Knowledge Base. Changes are specified through Control Statements.

2 IBM Tivoli License Compliance Manager for z/OS Installation Guide

Reference Identification File

The Reference Identification File (RIF) is an input of the Identifier that contains information about modules that can be used to identify the same set of modules wherever they are installed.

Selector

The Selector is an optional component that organizes the usage data collected by the Monitor to create output files used as input by the Distiller, Reporter, or Exporter.

Chapter 1. Concepts and terminology 3


Chapter 2. Installing IBM Tivoli License Compliance Manager for z/OS

This chapter describes how to install IBM Tivoli License Compliance Manager for z/OS Version 4.1. It provides the installation requirements and step-by-step procedures to ensure a successful installation.

Requirements

Before installing IBM Tivoli License Compliance Manager for z/OS Version 4.1, verify that you meet the following requirements:• z/OS Version 1 Release 4 or later is required for the installation and operation

of IBM Tivoli License Compliance Manager for z/OS.• ISPF Version 5 Release 1 or later is required for the installation and operation

of the ISPF interface.• The modules that comprise the Surveyor and Monitor must reside in an

authorized load library, but an IPL will not be necessary if the modules are moved to an existing authorized load library or if the IBM Tivoli License Compliance Manager for z/OS load library is added dynamically to the authorized program list.

• To fully scan your installation’s disk devices, the Surveyor must be run with a userid that has read-access authority to all volumes and load libraries. The Extractor must have read-access authority to all SMP/E data (CSI data sets), and the Monitor must have read authority to all LPA libraries.

Data set naming conventions

The recommended names assigned to IBM Tivoli License Compliance Manager for z/OS libraries have the following structure:• A first-level qualifier: the default value used throughout this manual is

AUDITLCM. You can change this value during the installation process.• A middle-level qualifier: the default value for Version 4.1 is V4R1M0. It

specifies the IBM Tivoli License Compliance Manager for z/OS release being installed.

• A library qualifier: it specifies the library type, e.g., LOADLIB.

Installing IBM Tivoli License Compliance Manager for z/OS

This section describes the post-installation steps necessary to complete the installation of IBM Tivoli License Compliance Manager for z/OS. Before beginning this installation, you must have completed the steps described in “Program Directory for IBM Tivoli License Compliance Manager for z/OS Version 4.1”, Program ID 5698-A86.

Copyright © 2006 5

Step 1: Authorize the Surveyor and Monitor

To install IBM Tivoli License Compliance Manager for z/OS Version 4.1, both the Surveyor and Monitor components must be APF authorized. You can use either of the following methods: • Dynamically add the IBM Tivoli License Compliance Manager for z/OS load

library to the APF authorized library list using the SETPROG operator command.

• Copy AUDSURV, AUDMONTR, AUDINSVC, AUDUTIL, AUDLPALB, AUDCP1P, and AUDIGNLD from the IBM Tivoli License Compliance Manager for z/OS library to a currently APF-authorized library, using the job LOADAUTH in the IBM Tivoli License Compliance Manager for z/OS JCL library. Modify the default values for the symbolic parameters on the PROC statement or provide overriding values on the calling EXEC statement, as appropriate. Submit the LOADAUTH job.

• Add the IBM Tivoli License Compliance Manager for z/OS load library to the authorized program list and re-IPL.

Step 2: Pre-allocate Surveyor and Monitor data sets

The job ALOCDATA in the IBM Tivoli License Compliance Manager for z/OS JCL library can be used to allocate these data sets. The sample execution JCL on the distribution tape assumes that the data sets used by the Surveyor and the Monitor have been pre-allocated. Note that the Surveyor data set must be defined as a PDSE (JCL specifies DSNTYPE=LIBRARY).

To pre-allocate a data set, you must specify the full data set name on the calling EXEC statement, as in the following example: //ALOCDATA JOB . . . // EXEC ALOCDATA,SRVVOL=AUDVOL, // SRVDATA='AUDITLCM.SURVEY.DATA', // MDTVOL=AUDVOL, // MONDTL='AUDITLCM.MONITOR.DETAIL'

When allocating space for the Monitor data sets, use the following guidelines: • A Monitor data set must be allocated with only a primary space allocation of

at least two tracks. The Monitor does not use a secondary allocation, even if one is specified.

• Once allocated, the size of a Monitor data set must not change. The specified or default SMS parameters must not allow SMS to shrink the size of the data set.

• Do not specify the RLSE parameter. • Allocate at least two Monitor data sets to avoid losing data while a full data

set is being emptied. In a very active system, you may specify more than two data sets with any name you choose. These data sets must be made available to the Monitor via DD statements with names of the form MONDTLxx, where "xx" can be any two characters valid in a DD name.

• When running the SPINOFF jobs to empty the Monitor data sets, if the accumulation data set specified in the MONDTLSV DD is allocated to DASD, it must have the same attributes as the Monitor files.

For more information, see Appendix B. Disk space requirements on page 21.


Step 3: Enable security

If you are using a security package (RACF, ACF2, TopSecret, etc.), you must ensure that you meet the following requirements:• The Surveyor has authority to read every load library on every volume at your

installation. It needs this authority to read the directories of these libraries and to search the modules for information it needs for the various reports. For the Surveyor to detect disks being used by FlashCopy, the Surveyor must have read access to STGADMIN.ANT.ESFC.FCQUERY in the FACILITY class.

• The Extractor (EXTRACTR) is authorized to read the SMP/E data sets for the system on which it is run.

• The Monitor is authorized to read all the LPA libraries defined to the system where it is running. If it is not authorized, you can specify the parameter NOLPA to allow the Monitor to be started without that authority. In this case, the Monitor does not read the LPA libraries, and the information collected about executions from LPA will be less comprehensive.

• Jobs do not need to reside in the IBM Tivoli License Compliance Manager for z/OS JCL library, they can be in any JCL library, however, all jobs must be in the same JCL library. Also, the MONDTL started procedure and the MONDTLxx jobs, which copy and empty the usage data sets (MONDTLxx), must be authorized to access the usage files and the data sets they are copied to.

For more information, see Choose a method to empty usage data sets on page 8.

Step 4: Modify the execution JCL

JCL to execute the components of IBM Tivoli License Compliance Manager for z/OS is included in the IBM Tivoli License Compliance Manager for z/OS JCL library. As noted in the comments in the members themselves, these members have to be modified as appropriate for your installation before they can be used.

Note: The IBM Tivoli License Compliance Manager for z/OS jobs may require large amounts of virtual storage. As supplied, the JCL for some jobs specify REGION=0M, which allows up to the installation-specified maximum value (often 32M).

Modify the JCL for an SMS environment

In an SMS environment, most of the allocation parameters required can be automatically supplied by using explicit or implicit storage class and data class parameters. Thus, many DD statements might omit all parameters except DSN and DISP. If the default storage class or data class is not appropriate, you can specify them explicitly, and you can specify individual parameters (such as SPACE) to override the defaults.

Choose a method to execute the Monitor

The Monitor can be run as a batch job or as a started task. For more information about running the Monitor, see IBM Tivoli License Compliance Manager for z/OS Administration Guide.

To install the Monitor to execute as a batch job, modify the MONITOR job as appropriate.

Chapter 2. Installing IBM Tivoli License Compliance Manager for z/OS 7

To install the Monitor and run it as a started task, modify the AUDITLCM procedure and move it into a system library, from which procedures may be started. Then execute the Monitor by issuing the MVS START command from the operator console: S AUDITLCM

Choose a method to empty usage data sets

When a usage data set becomes full, the Monitor must empty it. To empty usage data sets, choose one of the following required methods:• A cataloged procedure, which is submitted via an internal START command

issued by the Monitor• A set of jobs, which are written to a JES internal reader by the Monitor

Indicate that you are using a cataloged procedure by including the execution parameter DTLPROC= (followed by the procedure name) in the PARM field of the Monitor program, like this: // EXEC AUDITLCM,PARM.AUDITLCM='DTLPROC=MONDTL'

A cataloged procedure named MONDTL is included in the JCL library. Modify it as appropriate for your installation, and make sure that it resides in a system library, from which procedures may be started, such as SYS1.PROCLIB.

Indicate that you are using a set of jobs by omitting the parameter DTLPROC=, and instead specifying the name of a PDS containing the jobs as a parameter to the procedure, like this: // EXEC AUDITLCM,DTLCOPY='USER1.JCL.CNTL'

In the specified PDS, there must be a matching MONDTLxx member for each MONDTLxx DD specified in the.Monitor job. This job is to be initiated when the corresponding MONDTLxx data set becomes full.

The name of the Authorized Library (AUTHLIB) and the prefix for the Monitor Detail data sets (MONDTL) must also be supplied.

Step 5: Install the ISPF interface (optional)

IBM Tivoli License Compliance Manager for z/OS provides an interface to ISPF. The IBM Tivoli License Compliance Manager for z/OS ISPF interface facility is used for job submission. To install the interface, do the following:

Verify the ISPF interface library names

This procedure ensures that the correct library names are available to the IBM Tivoli License Compliance Manager for z/OS ISPF interface.

Edit the member SACUSTOM in the CLIB data set. If you are not using the standard IBM Tivoli License Compliance Manager for z/OS names, the changes must be made to the lines containing the following:audlib=“AUDITLCM”audver=“V4R1M0”


where:– audlib is your first-level qualifier for the IBM Tivoli License Compliance

Manager for z/OS data sets.– audver is your middle-level qualifier for the IBM Tivoli License

Compliance Manager for z/OS data sets.

The IBM Tivoli License Compliance Manager for z/OS ISPF interface can be invoked from ISPF option 6 by issuing the command: exec ‘AUDITLCM.V4R1M0.CLIB’

Step 6: Install Spotlight+ (optional)

Refer to the appropriate product documentation to install Spotlight+.

Chapter 2. Installing IBM Tivoli License Compliance Manager for z/OS 9


Chapter 3. Upgrading from Version 3.2

To get the full benefit of IBM Tivoli License Compliance Manager for z/OS Version 4.1, IBM recommends that you run all data collecting components, that is, Surveyor and Extractor. You may, however, convert IBM Tivoli License Compliance Manager for z/OS Version 3.2 data for use by Version 4.1.

The IBM Tivoli License Compliance Manager for z/OS Version 4.1 UPGRADE utility converts Surveyor, Extractor, and Identifier output data sets created by IBM Tivoli License Compliance Manager for z/OS Version 3.2. Releases prior to Version 3.2 cannot be migrated, you must run the full process, that is, Surveyor, Extractor (if appropriate), and Identifier.

Data set upgrades

The UPGRADE utility accepts Surveyor, Identifier, or Extractor data sets created by IBM Tivoli License Compliance Manager for z/OS Version 3.2 only. It converts the data sets to the IBM Tivoli License Compliance Manager for z/OS Version 4.1 format.

The Surveyor output data set has been redesigned for IBM Tivoli License Compliance Manager for z/OS Version 4.1 and is required to be an extended PDS (PDSE). The IBM Tivoli License Compliance Manager for z/OS Version 4.1 Surveyor no longer supports the COPYR (collect copyrights) option, however, if the copyright members are present in the IBM Tivoli License Compliance Manager for z/OS Version 3.2 Surveyor data set, they will be copied to the corresponding members in the IBM Tivoli License Compliance Manager for z/OS Version 4.1 data set.

History information in the Extractor and Identifier data sets is added to indicate that they have upgraded to the IBM Tivoli License Compliance Manager for z/OS Version 4.1 level.

Input

The UPGRADE utility converts Surveyor, Extractor, and Identifier input data sets. The specified input files determine the type of upgrade.

Copyright © 2006 11

Dataset ddnames

The following ddnames are used by the UPGRADE Utility: – AUDITDB; the latest version of the Knowledge Base used for inventory

generation. – SURVIN; Surveyor data set to be upgraded.

– SURVOUT; upgraded Surveyor data set1. – IDNTIN; Identifier data set to be upgraded. – IDNTOUT; upgraded Identifier data set. – XOFIN; Extractor data set to be upgraded – XOFOUT; upgraded Extractor data set

Users can convert a maximum of one Surveyor plus one Identifier plus one Extractor data set, in a single run. This is determined by the presence or absence of the necessary DD statements.

UPGRADER job stream

Users may find this file in the IBM Tivoli License Compliance Manager for z/OS JCL library://UPGRADER JOB <<<< ADD APPROPRIATE JOB STATEMENT PARAMETERS >>>> //* //* THIS JOB CREATES THE UPGRADED SURVEYOR DATA SET, AND/OR //* THE UPGRADED IDENTIFIER DATA SET AND/OR THE UPGRADED //* EXTRACTOR DATA SET. //* //* NOTE: UPGRADING OF A SURVEYOR DATA SET IS BASED ON THE //* THE CURRENT KNOWLEDGEBASE. //* //* NOTE: UPGRADING OF AN IDENTIFIER DATA SET IS BASED ON THE //* THE PREVIOUS KNOWLEDGEBASE. //* //* NOTE: WHEN SPECIFYING A VALUE FOR "SURVIN", "SURVOUT", //* "IDNTIN", "IDNTOUT", "XOFIN" AND "XOFOUT" ON THE //* CALLING EXEC STATEMENT, REMEMBER TO SPECIFY THE //* FULL DATA SET NAMES IN SINGLE QUOTES. //* //* NOTE: BLOCKSIZE 0 LETS SYSTEM PICK THE BEST FIT. //* //* NOTE: IF YOU WISH TO ALLOW IBM TIVOLI LICENSE COMPLIANCE MANAGER FOR A/OS TO MANAGE THE DELETION OF //* THE "SURVOUT", "IDNTOUT", OR "XOFOUT" DATA SETS, REMOVE THE //* APPROPRIATE "*"S AT BEGINNING OF THE "CLEAR" STEP DD //* STATEMENTS. //* //* //* NOTE: THE OPTIONAL DD-STATEMENT "FILTERS" //* MUST INCLUDE THE STEP-NAME "UPGRADE", IF ADDED //* AS AN OVERRIDING STATEMENT, AS IN //* //* //UPGRADE.FILTERS DD .... //* //*-------------------------------------------------------------------- //UPGRADER PROC IDX=AUDITLCM, - IBM TIVOLI LICENSE COMPLIANCE MANAGER FOR A/OS HIGH-LEVEL DATA SET QUALIFIER // VER=V3R2, - CURRENTLY INSTALLED VERSION // SRVIN=NULLFILE, - CURRENT SURVEYOR-DATA DATA SET NAME

1. This must be defined as a PDSE.


// SRVOUT=NULLFILE, - UPGRADED SURVEYOR-DATA DATA SET NAME // IDIN=NULLFILE, - CURRENT IDENTIFIER-DATA DATA SET NAME // IDOUT=NULLFILE, - UPGRADED IDENTIFIER-DATA DATA SET NAME // XOFIN=NULLFILE, - CURRENT EXTRACTOR-DATA DATA SET NAME // XOFOUT=NULLFILE, - UPGRADED EXTRACTOR-DATA DATA SET NAME // UNIT=SYSALLDA, - UNIT FOR OUTPUT DATA SETS // SRVVOL=, - VOLSER FOR UPGRADED SURVEYOR DATA SET // IDVOL=, - VOLSER FOR UPGRADED IDENTIFIER DATA SET // XOFVOL=, - VOLSER FOR UPGRADED EXTRACTOR DATA SET // PARAM=, - UPGRADER PARM FIELD // SRVSPAC=50, - PRI/SEC SPACE FOR SURVEYOR DATA SET // SRVBLK=0, - BLOCKSIZE FOR SURVEYOR DATA SET // IDSPACE=50, - PRI/SEC SPACE FOR IDENTIFIER DATA SET // IDBLK=0, - BLOCKSIZE FOR IDENTIFIER DATA SET // XOFSPAC=50, - PRI/SEC SPACE FOR EXTRACTOR DATA SET // XOFBLK=0, - BLOCKSIZE FOR EXTRACTOR DATA SET // WRKUNIT=SYSALLDA, - UNIT FOR WORK DATA SETS // WRKSPAC=50 - PRI/SEC SPACE FOR WORK DATA SETS //*-------------------------------------------------------------------- //* //*========= DELETE OLD DATA SETS ================================ //* //CLEAR EXEC PGM=IEFBR14 //*SURVOUT DD DISP=(MOD,DELETE,DELETE),DSN=&SRVOUT, //* UNIT=&UNIT,SPACE=(TRK,0) //*IDNTOUT DD DISP=(MOD,DELETE,DELETE),DSN=&IDOUT, //* UNIT=&UNIT,SPACE=(TRK,0) //*XOFOUT DD DISP=(MOD,DELETE,DELETE),DSN=&XOFOUT, //* UNIT=&UNIT,SPACE=(TRK,0) //* //*-------------------------------------------------------------------- //* //*========= EXECUTE THE UPGRADER ============================= //* //UPGRADE EXEC PGM=AUDUPGRM,REGION=0M, // PARM='&PARAM' //STEPLIB DD DISP=SHR,DSN=&IDX..&VER..LOADLIB //SYSPRINT DD SYSOUT=* //AUDLOG DD SYSOUT=* //SYSABEND DD SYSOUT=* //AUDITDB DD DISP=SHR,DSN=&IDX..&VER..PRODDATA //SURVIN DD DISP=SHR,DSN=&SRVIN //SURVOUT DD DISP=(NEW,CATLG,DELETE),DSN=&SRVOUT, // UNIT=&UNIT,VOL=SER=&SRVVOL, // SPACE=(CYL,(&SRVSPAC,&SRVSPAC,3)), // DSNTYPE=LIBRARY. // DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&SRVBLK) //IDNTIN DD DISP=SHR,DSN=&IDIN //IDNTOUT DD DISP=(NEW,CATLG,DELETE),DSN=&IDOUT, // UNIT=&UNIT,VOL=SER=&IDVOL, // SPACE=(CYL,(&IDSPACE,&IDSPACE,3)), // DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&IDBLK) //XOFIN DD DISP=SHR,DSN=&XOFIN //XOFOUT DD DISP=(NEW,CATLG,DELETE),DSN=&XOFOUT, // UNIT=&UNIT,VOL=SER=&XOFVOL, // SPACE=(CYL,(&XOFSPAC,&XOFSPAC,3)), // DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=&XOFBLK) //SYSUT1 DD UNIT=&WRKUNIT,SPACE=(CYL,(&WRKSPAC,&WRKSPAC)) //SYSUT2 DD UNIT=&WRKUNIT,SPACE=(CYL,(&WRKSPAC,&WRKSPAC)) //SYSWORK1 DD UNIT=&WRKUNIT,SPACE=(CYL,(0,&WRKSPAC)) //SYSWORK2 DD UNIT=&WRKUNIT,SPACE=(CYL,(0,&WRKSPAC)) // PEND //*==================================================================== //* //UPGRADER EXEC UPGRADER,

Chapter 3. Upgrading from Version 3.2 13

// IDIN='NULLFILE', <=== SPECIFY DATA SET NAME IN QUOTES // IDOUT='NULLFILE', <=== SPECIFY DATA SET NAME IN QUOTES // IDVOL=XXXXXX, <=== SPECIFY VOLSER FOR IDOUT DATA SET // SRVIN='NULLFILE', <=== SPECIFY DATA SET NAME IN QUOTES // SRVOUT='NULLFILE', <=== SPECIFY DATA SET NAME IN QUOTES // SRVVOL=XXXXXX, <=== SPECIFY VOLSER FOR SRVOUT DATA SET // XOFIN='NULLFILE', <=== SPECIFY DATA SET NAME IN QUOTES // XOFOUT='NULLFILE', <=== SPECIFY DATA SET NAME IN QUOTES // XOFVOL=XXXXXX <=== SPECIFY VOLSER FOR XOFOUT DATA SET


Chapter 4. Maintenance

This chapter describes how to maintain IBM Tivoli License Compliance Manager for z/OS.

Installing an enhanced Knowledge Base

To enhance the identification of products, IBM periodically distributes updated versions of the Knowledge Base. (For more information on the Knowledge Base, see Knowledge Base on page 2). The existing Knowledge Base can be replaced with a newer one within the same version of IBM Tivoli License Compliance Manager for z/OS. For example, you can replace the Version 3.1.2 Knowledge Base with the Knowledge Base from Version 3.2. For more information, see the Release Notes for each Knowledge Base distribution.

The SAMPLIB data set contains members (for example, KBPRDLST, KBVNDLST, KBVRGLST) that list the major changes made to the Knowledge Base for the given version. Additional SAMPLIB members contain changes made for prior editions of the Knowledge Base.

To replace the existing Knowledge Base, you must perform the following instruction:1. The newer Knowledge Base is supplied to you as an SMP/E-installable PTF.

The name of the library containing the Knowledge Base is an installation option and does not affect the operation of IBM Tivoli License Compliance Manager for z/OS. As supplied, however, the execution JCL assumes that this library has the same VER qualifier as the other IBM Tivoli License Compliance Manager for z/OS components. Naming the library, which contains this component with the same VER qualifier as the other components you are running, will avoid the need to find and change all the references to the Knowledge Base in the IBM Tivoli License Compliance Manager for z/OS execution JCL.

2. The newer Knowledge Base may require changes to the User Product Data File or Knowledge Base Customization Input. After it is installed, it is recommended that the Identifier be run without any User Product Data to see what statements are still necessary.

3. After running the Identifier, you can then reproduce whatever reports, exported files, and Distiller files that may be affected by this new information.

AUDINFO load module

Whenever maintenance is applied to IBM Tivoli License Compliance Manager for z/OS, an entry is also made in the AUDINFO load module. Thus, this module contains a record of all maintenance applied. Be sure to keep only one copy of this module and apply all fixes to it. If you apply fixes to a test library first, for example, be sure to reapply them to the production library to keep this status information accurate.


List of applied fixes

To get a listing of all fixes that have been applied to IBM Tivoli License Compliance Manager for z/OS, execute a job like the following (modified as required)://AUDUTIL JOB ...//AUDUTIL EXEC PGM=AUDUTIL,REGION=4M//STEPLIB DD DSN=AUDITLCM.V4R1M0.LOADLIB,DISP=SHR//AUDUTIL DD SYSOUT=A

Collecting Monitor diagnostic data

To investigate a Monitor installation problem, IBM technical support staff may need some diagnostic data produced by the Monitor while it is running. To produce the requested diagnostic data, execute a job as follows (modified as required)://AUDUTIL JOB ...//AUDUTIL EXEC PGM=AUDUTIL,PARM=SNAP//STEPLIB DD DSN=AUDITLCM.V4R1M0.LOADLIB,DISP=SHR//AUDUTIL DD SYSOUT=A

Note: If AUDUTIL fails to locate the diagnostic data area, change the parameter SNAP to FINDALL and resubmit the job.

Applying maintenance

Maintenance is distributed as SMP/E-installable PTFs.

Note: During the post-installation, some modules may have been copied into an authorized library. If so, make sure that these modules are copied again after any maintenance has been applied to them.

Starting an updated version of the Monitor

All prior maintenance has been included in this version. After applying maintenance, you need to load a new copy when you restart the Monitor.

Note: It is a statement that pertains to the entire product, not just the Monitor.

The Monitor maintains a portion of its running code in system storage. If maintenance includes modifications to the Monitor, it is necessary to force the Monitor to refresh the resident code. To do so, specify the parameter NEWCOPY in the PARM field of the EXEC statement that starts the Monitor:

//MONITOR EXEC PGM=AUDMONTR,PARM=NEWCOPY

In addition to loading a new copy, the Monitor tries to remove the previous version from resident storage.


Information checklist for reporting problems

The following table lists information you need to report a problem to IBM Product Support. A detailed description of the problem being reported is also required.

Table 1. General Information

Checklist Item Notes

Product version and release

Component name

Knowledge base maintenance level (for example, “Q405”)

Maintenance (PTFs) that has been applied (the AUDUTIL utility may help provide this information)

z/OS version and release values, and which JES is part of the system (JES2 or JES3)

Problem specifics (for example, name of report or screen where the error appears) and problem description

For U100 abends, the information from the SYSPRINT error message that identifies the problem (for example, the “AUDxxxxx” value and the two-character code that follows)

Table 2. General Job Information


SYSPRINT output from the component (for example, Surveyor and Identifier logs, report output)

Other job output (for example, JES message log, the JCL log, the system message log)

Dump output – SYSABEND output is generally required for problem resolution. SYSMDUMP, SYSUDUMP, dump formatter output (for example, ABENDAID) are occasionally sufficient.

Chapter 4. Maintenance 17

Table 3. IBM Tivoli License Compliance Manager for z/OS Component Information (if applicable)


Surveyor output data sets

Identifier output data sets

USRPDATA input file

KBCUTIN customization statements

Extractor output file

AUDUTIL run output with SNAP and/or FINDALL options may be requested (Monitor)

Examples of reports in error should be available

Flat file output files from the Exporter

Distiller output file, as well as Spotlight+ screen shots of suspected error conditions

Table 4. Additional Information


For “short on storage” conditions (for example, U3011, S878 abends), the REGION= value in effect

“IEF374I” message produced at the end of each job step

Installation exit (for example, IEFUSI) storage limitation values for jobs

Value of the DSP= parameter in effect

Any “AUD” prefixed messages


Appendix A. JCL Library

The IBM Tivoli License Compliance Manager for z/OS JCL library includes the following members.

Table 1. JCL Library Members

Name Function

ALOCDATA Job to allocate the Monitor and Surveyor data sets

AUDITLCM Procedure to run the Monitor as a started task

COPYAUTH Member used by LOADAUTH

DISTILLR Job to run the Distiller

EXPORTER Job to run the Exporter

EXTRACTR Job to run the Extractor

IDNTFIER Job to run the Identifier

KBCUSTOM Job to run the Knowledge Base Customization Tool

LOADAUTH Job used to copy the Monitor and utility modules to an authorized library

MONDTL Procedure started by the Monitor or via SPINOFF to copy Monitor data into pre-allocated data sets

MONDTLXX Job submitted by the Monitor or via SPINOFF to copy Monitor data into pre-allocated data sets

MONITOR Job to run the Monitor as a standard batch job

REPORTER Job to run the Reporter

RIFUTIL Job to run the RIFUTIL

SELECTOR Job to run the Selector

SPINOFF Job to spin off the Monitor data manually

SURVEYOR Job to run the Surveyor

UPGRADER Job to run the Upgrader



Appendix B. Disk space requirements

This appendix provides guidelines for estimating the sizes of various data sets used during processing.

Surveyor data set (SURVDATA)

To estimate the number of blocks created by the Surveyor on the SURVDATA data set (allocated by the ALOCDATA job that is run during the IBM Tivoli License Compliance Manager for z/OS installation), use the following formula:

BLOCKS = (200V + 2L + M)/250

where:– V is the estimated number of volumes;– L is the estimated number of load libraries– M is the estimated number of modules.

Note: The formula assumes a block size of 27920.

Use this formula to estimate the size for SURVDATA. The ALOCDATA job uses a default space allocation assuming the installation has 3,000 load libraries and 120,000 load modules.

Extractor data set (UPDATXOF)

To estimate the number of blocks created by the Extractor on the UPDATXOF data set, use the following formula: BLOCKS = (((25 + Z + T + C + M + H) + (block size/80) - 1) / (block size/80))

where:– Z is 2 * the number of target zones;– T is the number of syslibs;– C is the number of destination libraries;– M is the number of load modules in all syslibs;– H is 3 * the number of times the Extractor is run.

Work data sets SYSWORK2 through SYSWORKB

The SYSWORK2 through SYSWORKB work data sets allocated via DD statements of the IDNTFIER, REPORTER, UPGRADER, KBCUSTOM, DISTILLR, and EXPORTER JCL procedures should be created with a space allocation similar to the SURVDATA data set.


Monitor data sets (MONDTLxx)

The MONDTLxx data sets are created with a block size of 6,144 bytes, with DSORG=PS, RECFM=VB, and LRECL=2048.

Note: These characteristics are fixed and cannot be overridden via JCL. You can use these characteristics for a DASD monitor data accumulation file (MONDTLSV).

To estimate the number of blocks created each hour, use the following formula:

BLOCKS=(J*300+T*800)/6144

where: – J is the average number of batch jobs or job steps (if information is gathered

on a step basis) per hour;– T is the average number of TSO sessions started per hour.

Use this formula to estimate the number of data sets to allocate, the size of each data set, and the amount of space required to hold the data accumulated. The default allocations assume 100,000 batch jobs or job steps (if data is gathered on a step basis) and 5,000 TSO sessions. In most cases, the defaults supplied are sufficient.

Sort work data sets

The allocations necessary for the sort work data sets (SORTWRKnn) depend on the amount of data to be sorted. In most cases, the defaults supplied are sufficient. However, you may have to provide larger allocations when processing a very large number of job or step records. If necessary, the sort work data sets can be assigned to tape.

Usage work data sets

IBM Tivoli License Compliance Manager for z/OS uses work data sets AUDWORK1 through AUDWORK6 for usage data. The amount of space required for these data sets depends on the following:• The number of jobs or steps (if data is captured at the step level) in the usage

data• The average number of unique modules per job or step• Whether or not you are producing summary or usage reports.

The following table shows the formula for estimating the number of bytes required for each data set, where J is the number of jobs or job steps (if information is gathered on a step basis).


If necessary, you can assign some or all of these data sets to tape.

Distiller data sets (DISTOUT)

The DISTOUT data set is created with a block size of 32760 bytes, with DSORG=PS, RECFM=VB, and LRECL=32756. If you are running with an older version of a DISTOUT data set, delete it and reallocate it. Specifying LRECL and BLKSIZE values in the JCL is not necessary; they will be set by the Distiller.

Table 1. Usage Work Data Sets

Data Set Estimated Storage Required

AUDWORK1 J*190

AUDWORK2 J*1200

AUDWORK3 N/A

AUDWORK4 J*266

AUDWORK5 J*1200

AUDWORK6 J*1200

Appendix B. Disk space requirements 23


Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application


programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information in soft copy form, the photographs and color illustrations might not display.

Trademarks

AIX, DB2, IBM, the IBM logo, IBMLink, Informix, OS/2, OS/400, Tivoli, the Tivoli logo, Tivoli Enterprise Console, and TME are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

Notices 27


Index

A

ACF2, 7ALOCDATA, 6, 19, 21APF-authorized library, 6AUDITLCM, 5, 8, 19

D

Data Set, 21Data Sets, 1, 6, 8, 21, 22, 23data sets, vii, 6, 7, 8, 9, 11, 18, 19, 21Distiller, 2

E

Exporter, 2

J

jobsALOCDATA, 6, 21DISTILLR, 19KBCUSTOM, 21LOADAUTH, 6, 19MONITOR, 7, 19REPORTER, 19RIFUTIL, 19SELECTOR, 19SPINOFF, 6SURVEYOR, 19UPGRADER, 19

K

KBCUSTOM, 19, 21KBPRDLST, 15KBVNDLST, 15Knowledge Base, 2, 12, 15, 17, 19knowledge base, xiKnowledge Base Customization Tool, 19

L

libraries, 5, 7, 21load library, 5, 6, 7LOADAUTH, 6LOADLIB, 5

M

Maintenance, 15, 17maintenance, ix, 15, 16, 17middle-level qualifier, 5, 9MONDTL, 6, 7, 8, 19MONITOR, 7Monitor, 5, 6, 7, 8, 16, 18, 19, 22monitor, 16

N

NEWCOPY, 16NOLPA, 7

R

RACF, 7read-access authority, 5RIFUTIL, 19

S

SACUSTOM, 8SAMPLIB, 15

KBPRDLST, 15KBVNDLST, 15KBVRGLST, 15

Security, 7SELECTOR, 19SMS, 6, 7SNAP, 16, 18Sort work data sets, 22SPINOFF, 6, 19Spotlight+, 2, 9, 18SURVDATA, 21Surveyor, 5, 6, 7, 11, 12, 17, 18, 19, 21Surveyor data set, 6, 11, 12


T

TopSecret, 7

U

UPDATXOF, 21USRPDATA, 18


Documents

Version 4 - IBMpublib.boulder.ibm.com/tividd/td/ITLCMfzOS/GC32-2266-00/... · 2006-01-24 · † Chapter 3. Upgrading from Version 3.2 Explains how to upgrade IBM Tivoli License Compliance