Accounting Feature for z/os

Transcription

1 Tivoli Decision Support for z/os Accounting Feature for z/os Version 1.7 SH

2

3 Tivoli Decision Support for z/os Accounting Feature for z/os Version 1.7 SH

4 Note Before using this information and the product it supports, read the information in Notices on page 91. Sixth Edition (November 2004) This edition applies to version 1, release 7 of Tivoli Decision Support for z/os (program number 5698-A07) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SH Copyright International Business Machines Corporation 1994, All rights reserved. Note to U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

5 Contents Figures v Preface vii Who should read this book vii What this book contains vii Publications viii Tivoli Decision Support for z/os library... viii Using LookAt to look up message explanations.ix Accessing publications online ix Ordering Publications x Accessibility x Tivoli technical training x Contacting IBM Software Support x Determine the business impact of your problem xi Describe your problem and gather background information xi Submit your problem to IBM Software Support.xi Searching knowledge bases xii Obtaining fixes xii Updating support information xiii Conventions used in this book xiii Typeface conventions xiv Changes in this edition xiv Part 1. Accounting Feature for z/os guide Chapter 1. Overview of the Accounting Feature for z/os Collecting usage data Producing billing information Setting prices Output from the Accounting Feature for z/os..4 Working with the Accounting Feature for z/os an example Considerations Customers and accounts Billing units Prices Chapter 2. Preparing the Accounting Feature for z/os How the Accounting Feature for z/os works...9 Setting up security Trimming the data tables Installing the Accounting component Maintaining the lookup tables Workload period and special day tables DCOLLECT LAST_RUN lookup table Network resource translation table Preparing for collect Chapter 3. Implementing the Accounting Feature for z/os Understanding Accounting Feature for z/os tables 15 Table types Data tables Summary tables Lookup tables Views Chapter 4. Prorating overhead accounts DRLJPROR sample job Distributing overhead accounts based on fixed percentages Distributing overhead accounts based on relative percentages Part 2. Accounting Feature for z/os reference Chapter 5. Data flow Overview of data flow CICS data flow Credit debit processing data flow DB2 data flow DFSMS data flow IMS data flow NPM and NetView data flow STC, BATCH, TSO data flow Overhead accounts data flow Billing process data flow Chapter 6. Data tables and views RAFBATCH data table RAFJOBLOG data table RAFCICS data table RAFDASD data table RAFDB2 data table RAFHSMBKUP data table RAFHSMMIGR data table RAFIMS data table RAFNETSES20 data table RAFNETSES4X data table RAFNETV data table RAFSTC data table RAFADDRLOG data table RAFTSO data table RAFSESLOG data table USE_SUMMARY_D data table USE_SUMMARY_D2 data table USE_SUMMARY_D3 data table USE_SUMMARY_D4 data table ACCT_PRORATEV1 view ACCT_PRORATEV2 view iii

6 BILLED_DATA data table Chapter 7. Lookup tables ACCOUNT ACCT_PRORATE BILLING_PERIOD CPU_NORMAL_DATA CREDIT_DEBIT CUSTOMER PRICE_LIST Chapter 8. Accounting Feature for z/os translation tables RAFABATCH RAFACICS RAFADASD RAFADB RAFAHSMBKUP RAFAHSMMIGR RAFAIMS RAFANETSESM RAFANETV RAFASTC RAFATSO Chapter 9. Accounting Feature for z/os reports Accounting Feature for z/os report definitions..83 Prorated account percentage validation report..83 Charges by billing period report Charges by billing period, with two currencies report Billing details report Charges for selected billing period report...87 Chapter 10. Considerations for dpam users Notices Trademarks List of abbreviations Glossary Index iv Tivoli Decision Support for z/os: Accounting Feature for z/os

7 Figures 1. Partial view of an RAFBATCH summary table General overview of data flow CICS component data flow Credit debit processing data flow DB2 component data flow DFSMS component data flow IMS component data flow NPM and NETV components data flow STC, Batch, TSO component data flow Overhead accounts data flow Billing process data flow Prorated account percentage validation Charges by charge type Charges by billing period, with two currencies Billing details, partial view Charges by charge type v

8 vi Tivoli Decision Support for z/os: Accounting Feature for z/os

9 Preface The Accounting Feature for z/os describes how to use IBM Tivoli Decision Support for z/os (hereafter referred to as Tivoli Decision Support for z/os) to collect and report performance data generated by the Accounting Feature for z/os (previously known as Accounting feature). Tivoli Decision Support for z/os was previously known as Tivoli Decision Support for OS/390. The terms MVS, OS/390, and z/os are used interchangeably throughout this book. Who should read this book What this book contains The Accounting Feature for z/os is for: v Anyone who is going to install or use the Accounting Feature for z/os. v Data processing accounting personnel who use the Accounting Feature for z/os to produce reports or who bill the customers of a data processing center. v Administrators who wish to get information about the log records generated by the producing systems. This is important in Tivoli Decision Support for z/os applications for deciding which services can be charged for and on what basis the charges should be made. v Administrators, primarily as a guide to feature installation and as a reference to table and report definitions. v Users who are interested in analyzing the Accounting Feature for z/os data. This book contains two parts: v Use Part 1, Accounting Feature for z/os guide, for an overview of the Tivoli Decision Support for z/os Accounting Feature for z/os and as a guide to using it. Chapter 1, Overview of the Accounting Feature for z/os contains an overview of the feature and gives an example of how you can use it. Chapter 2, Preparing the Accounting Feature for z/os explains how the Accounting Feature for z/os and Tivoli Decision Support for z/os work together. This contains installation information and explains how to work with the Accounting Feature for z/os tables. Chapter 3, Implementing the Accounting Feature for z/os explains the Accounting Feature for z/os tables. Chapter 4, Prorating overhead accounts explains how to allocate overhead costs on a fixed or percentage basis. v Use Part 2, Accounting Feature for z/os reference as a reference while you use the Accounting Feature for z/os. Chapter 5, Data flow explains the data flow. Chapter 6, Data tables and views contains examples of the data tables. Chapter 7, Lookup tables contains examples of the lookup tables. vii

10 Chapter 8, Accounting Feature for z/os translation tables contains examples of the translation tables. Chapter 9, Accounting Feature for z/os reports contains examples of the Accounting Feature for z/os reports. Chapter 10, Considerations for dpam users compares the functions provided with the Tivoli Decision Support for z/os Accounting Feature for z/os with those provided with dp Accounting Manager (dpam). A list of abbreviations, glossary and index follow these chapters. Publications This section lists publications in the Tivoli Decision Support for z/os library and any other related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications. Tivoli Decision Support for z/os library The following documents are available in the Tivoli Decision Support for z/os library: v Accounting Feature for z/os, SH Provides information for users who want to use Tivoli Decision Support for z/os to collect and report performance data generated by the Accounting Feature for z/os. v Administration Guide, SH Provides information about initializing the Tivoli Decision Support for z/os database and customizing and administering Tivoli Decision Support for z/os. v AS/400 System Performance Feature Guide and Reference, SH Provides information for administrators and users about collecting and reporting performance data generated by AS/400 systems. v CICS Performance Feature Guide and Reference, SH Provides information for administrators and users about collecting and reporting performance data generated by Customer Information and Control System (CICS ). v Distributed Systems Performance Feature Guide and Reference, SH Provides information for administrators and users about collecting and reporting performance data generated byoperating systems and applications running on a workstation. v Guide to the Reporting Dialog, SH Provides information for users who display existing reports, for users who create and modify reports, and for administrators who control reporting dialog default functions and capabilities. v IMS Performance Feature Guide and Reference, SH Provides information for administrators and users about collecting and reporting performance data generated by Information Management System (IMS ). v Language Guide and Reference, SH Provides information for adminstrators, performance analysts, and programmers who are responsible for maintaining system log data and reports. v Messages and Problem Determination, SH Provides information to help operators and system programmers understand, interpret, and respond to Tivoli Decision Support for z/os messages and codes. viii Tivoli Decision Support for z/os: Accounting Feature for z/os

11 v Network Performance Feature Installation and Administration, SH Provides information for network analysts or programmers who are responsible for setting up the network reporting environment. v Network Performance Feature Reference, SH Provides information for network analysts or programmers who are responsible for setting up the network reporting environment. v Network Performance Feature Reports, SH Provides information for network analysts or programmers who use the Network Performance feature reports. v System Performance Feature Guide, SH Provides information for performance analysts and system programmers who are responsible for meeting the service-level objectives established in your organization. v System Performance Feature Reference Vol. I, SH Provides information for administrators and users with a variety of backgrounds who want to use Tivoli Decision Support for z/os to analyze Multiple Virtual Storage (MVS) or Virtual Machine (VM) performance data. v System Performance Feature Reference Vol. II, SH Provides information for administrators and users with a variety of backgrounds who want to use Tivoli Decision Support for z/os to analyze Multiple Virtual Storage (MVS) or Virtual Machine (VM) performance data. v IBM Online Library z/os Software ProductsCollection Kit, SK2T-6012 CD containing all z/os documentation. Using LookAt to look up message explanations LookAt is an online facility that lets you look up explanations for most messages you encounter, as well as for some system abends and codes. Using LookAt to find information is faster than a conventional search because in most cases LookAt goes directly to the message explanation. You can access LookAt from the Internet at: or from anywhere in z/os or z/os.e where you can access a TSO/E command line (for example, TSO/E prompt, ISPF, z/os UNIX System Services running OMVS). The LookAt Web site also features a mobile edition of LookAt for devices such as Pocket PCs, Palm OS, or Linux -based handhelds. So, if you have a handheld device with wireless access and an Internet browser, you can now access LookAt message information from almost anywhere. Accessing publications online IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the Tivoli Decision Support for z/os link to access the product library at the Tivoli software information center. Preface ix

12 Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper. Ordering Publications You can order many Tivoli publications online at the following Web site: cgibin/pbi.cgi You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: In other countries, see the following Web site for a list of telephone numbers: Accessibility Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface.you can also use the keyboard instead of the mouse to operate all features of the graphical user interface. For additional information, see the Accessibility Appendix in the Administration Guide. Tivoli technical training For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: Contacting IBM 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: v 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 ( Passport_Advantage_Home) and click How to Enroll By phone: For the phone number to call in your country, go to the IBM Software Support Web site ( and click the name of your geographic region. x Tivoli Decision Support for z/os: Accounting Feature for z/os

13 Contacting IBM Software Support v 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 ( If you are not sure what type of software maintenance contract you need, call IBMSERV ( ) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web ( and click the name of your geographic region for phone numbers of people who provide support for your location. Follow the steps in this topic to contact IBM Software Support: 1. Determine the business impact of your problem 2. Describe your problem and gather background information 3. Submit your problem to IBM Software Support Determine 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: 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. Describe your problem and gather 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: v What software versions were you running when the problem occurred? v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can the problem be recreated? If so, what steps led to the failure? v Have any changes been made to the system? (For example, hardware, operating system, networking software, and so on.) v Are you currently using a workaround for this problem? If so, please be prepared to explain it when you report the problem. Submit your problem to IBM Software Support You can submit your problem in one of two ways: Preface xi

14 Contacting IBM Software Support v Online: Go to the Submit and track problems page on the IBM Software Support site ( Enter your information into the appropriate problem submission tool. v By phone: For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook on the Web ( 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 Searching knowledge bases and Obtaining fixes. 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: v IBM technotes v IBM downloads v IBM Redbooks v IBM DeveloperWorks v Forums and newsgroups v Obtaining Google 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 ( 2. Under Products A - Z, select your product name. This opens a product-specific support site. xii Tivoli Decision Support for z/os: Accounting Feature for z/os

15 Contacting IBM Software Support 3. Under Self help, follow the link to All Updates, 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 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. 4. 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. 5. Click Submit. 6. For notification for other products, repeat Steps 4 and 5. For more information about types of fixes, see the Software Support Handbook ( 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 ( 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. Conventions used in this book This guide uses several conventions for special terms and actions, operating system-dependent commands and paths, and margin graphics. The terms MVS, OS/390, and z/os are used interchangeably throughout this book. Preface xiii

16 Contacting IBM Software Support Typeface conventions This guide uses the following typeface conventions: Bold Italic Changes in this edition v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Column headings in a table v Keywords and parameters in text v Citations (titles of books, diskettes, and CDs) v Words defined in text v Emphasis of words (words as words) v Letters as letters v New terms in text (except in a definition list) v Variables and values you must provide Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options This edition is an updated version that replaces the previous edition of the same book. The changes are: v The name of the product has been changed to Tivoli Decision Support for z/os (except in figures). Except for editorial changes, updates to this edition are marked with a vertical bar to the left of the change. xiv Tivoli Decision Support for z/os: Accounting Feature for z/os

17 Part 1. Accounting Feature for z/os guide Chapter 1. Overview of the Accounting Feature for z/os Collecting usage data Producing billing information Setting prices Output from the Accounting Feature for z/os..4 Working with the Accounting Feature for z/os an example Considerations Customers and accounts Billing units Prices Chapter 2. Preparing the Accounting Feature for z/os How the Accounting Feature for z/os works...9 Setting up security Trimming the data tables Installing the Accounting component Maintaining the lookup tables Workload period and special day tables DCOLLECT LAST_RUN lookup table Network resource translation table Preparing for collect Chapter 3. Implementing the Accounting Feature for z/os Understanding Accounting Feature for z/os tables 15 Table types Data tables Summary tables Lookup tables Views Chapter 4. Prorating overhead accounts DRLJPROR sample job Distributing overhead accounts based on fixed percentages Distributing overhead accounts based on relative percentages

18 2 Tivoli Decision Support for z/os: Accounting Feature for z/os

19 Chapter 1. Overview of the Accounting Feature for z/os Collecting usage data The Accounting Feature for z/os is designed to meet the requirements of both the independent data processing center that offers services to external clients, and the DP department that is part of a large organization offering services to internal departments in the same organization. The Accounting Feature for z/os helps you run your DP center either as a cost center, distributing the budgeted costs equitably among the defined customers, or as a profit center, with the focus on prices, revenue, cost, and profit. The complex process of distributing data processing costs often confuses the users, who find it difficult to relate the billed costs to the services provided. You can use the flexible pricing and billing options of the Tivoli Decision Support for z/os Accounting Feature for z/os to provide the customers of your data processing center with a better understanding of their data processing costs, thus enabling them to manage their use of DP services more efficiently. The billing records provided by the Accounting Feature for z/os can be forwarded to your existing invoicing system, thus helping you to integrate the financial management of your DP center with your corporate financial systems. The Accounting Feature for z/os provides you with the means to successfully manage the business aspects of DP across the entire enterprise. The data is stored in a DB2 relational database, and QMF or an equivalent DB2 query program can be used to create standard reports. In addition, you can use QMF or another report writer to generate your own reports, using the SQL statements supplied with the Accounting Feature for z/os as a model. With the Accounting Feature for z/os you can collect and summarize the usage data from each of your subsystems. For all usage data, the Accounting Feature for z/os determines: v The workload period (for example, first shift). You can define workload periods based on the time of day, the day of the week, and whether a day is a holiday. v The account that should be charged. You can specify which values in the usage logs correspond to each account. If your DP center has more than one processor, you can specify normalization factors to account for different processor speeds. The Accounting Feature for z/os then records both the number of CPU seconds used and the number of normalized CPU seconds. Producing billing information You first define the billing periods for which customers will be billed. For example, the billing periods could be January 1998, February 1998, and so on. You have to specify a start date and an end date for each billing period. For each billing period, customers are charged according to their level of system usage. You specify which measurement units are used. For example, you can use 3

20 Overview of the Accounting Feature for z/os Setting basic resource units such as CPU seconds, for resource billing, or functional units such as CICS transactions, for functional billing. You can use the default measurement units or define your own. When you have defined your measurement units, you can define billing units. Your billing units can be the same as your measurement units, or more complex. For example, you can create one billing unit for CPU seconds during the day and another billing unit for CPU seconds at night. You can also base your billing units on factors like job class and priority. You can use the default billing units or define your own. Each customer is billed according to the quantity of each billing unit that is used, and the prices and discounts that you specify for that billing unit. You can also supplement the usage logs by specifying recurrent charges and occasional charges and refine your accounting records with corrections, credits, and reconciliation amounts. prices You specify the price of each billing unit by creating price lists. In each price list, you can specify the price for each billing unit in two different currencies (for example, dollars and euros). You can create a single price list to use for all customers or create a different price list for individual customers or each category of customers. Output from the Accounting Feature for z/os You can get both detailed reports and summaries from the Accounting Feature for z/os. You can use the predefined report definitions that are included with the Accounting Feature for z/os to produce standard reports in either QMF or an equivalent DB2 query program. You can also define your own reports from the information in the Accounting Feature for z/os DB2 database by writing new QMF procedures or by using an equivalent product. From the Accounting Feature for z/os billing data, you can extract billing records to be used by your DP center s invoicing system. A billing record specifies the total charge for a customer s use of DP services during a specified period. Each billing record has a related billing specification that contains detailed information about the bill. Working with the Accounting Feature for z/os an example Ace Inc. is a manufacturing company. As a result of rationalization and consolidation, it possesses more computer resources than it needs for its manufacturing process and company administration. The data processing department of Ace Inc. has for some time provided computer services to external customers. The financial department of Ace Inc. is concerned that the computer department is responsible for a considerable portion of the internal budget, but there is very little control over the contribution of different DP services. The DP manager believes that the external customers are profitable, and that investments in new applications would be worthwhile. As a result of discussions between the financial department and the DP department, Ace Inc. decides to implement a new DP accounting policy using the 4 Tivoli Decision Support for z/os: Accounting Feature for z/os

21 Overview of the Accounting Feature for z/os Considerations Accounting Feature for z/os. The DP department will first test the Accounting Feature for z/os with internal customers and later extend the test to include external customers. The producing systems used by Ace Inc. are all predefined to the Accounting Feature for z/os. The program administrator decides to use the default values provided. Each department of Ace Inc. is defined to the Accounting Feature for z/os as a customer. Some departments have several accounts; other departments have only one. The terminal ID and user ID for each log record determine which account is charged. The program administrator decides to use some of the default measurement units defined for the different producing systems. The DP manager wants to charge different prices for day service and night service. Two service types (DAY and NIGHT) are defined. Each billing unit consists of a measurement unit and one of the two service types. The DP manager decides to try three different price lists: v If Ace Inc. decides to practice resource billing, CPU seconds can be defined as a unit for billing with a fixed price per second. v Alternatively, using functional billing, a price can be set for each transaction ID based on the average number of CPU seconds used for that transaction. v By using service billing, prices can also be set for a combination of billing units and service types. The different price lists are tested on this log data. The purpose of the Accounting Feature for z/os is to help you bill customers for computer services. To do this, the Accounting Feature for z/os needs to know: v Whom you want to bill (your customers and accounts) v What you want to bill for (your billing units) v How much you want to charge for each billing unit (your prices) v How to find out which customer used which service and when Most of this information is contained in logs that are produced by the various computer systems that a customer uses. The computer systems that produce these logs are called producing systems. With this information, the Accounting Feature for z/os can produce billing records for each customer. The Accounting Feature for z/os can work with three types of computer-usage information: v Logs produced by computer systems such as Customer Information Control System (CICS). Each time the system is used, a record (containing information such as account number, time stamp, and number of CPU seconds used) is added to the log. v Snapshots showing resource usage at a particular moment. For example, you could take a weekly snapshot of the amount of DASD used by each account. Chapter 1. Overview 5

22 Overview of the Accounting Feature for z/os v Information that is not contained in logs or snapshots. For example, you might want to charge customers for education. You can enter this information in the Accounting Feature for z/os directly. The basic function of the Accounting Feature for z/os can thus be summarized as follows: Input Producing system summary tables Output Billing records Processing Using the information that you provide (such as customers, billing units, and prices), transform the producing system summary tables into billing records Customers and accounts You must provide the following information to the Accounting Feature for z/os: Billing v Which customers you want to bill v Which accounts correspond to each customer v Which column or combination of columns in each producing system log identifies the account You can also define certain expenses as overheads to be distributed among various customers. units A billing unit is any unit that you use to bill customers. You can bill customers at a resource level or a functional level. Billing customers at a functional level is called functional billing. If you bill customers at a resource level, each billing unit will fall into one of these categories: v A column in a producing system summary table (a base measurement unit, or BMU). For example, the number of CPU seconds. v A BMU combined with a service type. For example, the number of CPU seconds during the day shift. v A BMU combined with more than one service type. For example, the number of CPU seconds during the day shift for jobs with priority 1. If you bill customers at a functional level, you can also define the following types of billing units: v A column combined with a specific value in another column (a derived measurement unit, or DMU). For example, the number of CICS transactions when TRANS is TXN1. A billing unit that uses a DMU by itself is similar to a billing unit that uses a BMU combined with one service type. You should use the DMU construct rather than the service type when you want to avoid double charging at both the functional and resource levels. v A DMU combined with one or more service types. For example, the number of CICS transactions when TRANS is TXN1 during the day shift. If you decide to use service types that are related to time, you specify when each shift begins and ends, and which days of the year are holidays for your organization. 6 Tivoli Decision Support for z/os: Accounting Feature for z/os

23 Overview of the Accounting Feature for z/os Prices You must specify the price for each billing unit in a price list. In the price list, you can specify the price for each billing unit in two different currencies (for example, dollars and euros). You can specify one price list that applies to all customers, or specify different price lists for different customers. You can also specify discounts based on the volume of service that a customer uses. Chapter 1. Overview 7

24 8 Tivoli Decision Support for z/os: Accounting Feature for z/os

25 Chapter 2. Preparing the Accounting Feature for z/os Tivoli Decision Support for z/os is a base product with separate add-on features. Each feature includes a number of components, which themselves consist of the object definitions required to collect and report on a given set of data. How the Accounting Feature for z/os works The Accounting Feature for z/os of Tivoli Decision Support for z/os consists of one component with multiple subcomponents. Each subcomponent corresponds to a single subsystem data source. Some object definitions used for the Accounting Feature for z/os are included with the Tivoli Decision Support for z/os base product, while the remainder are shipped when the feature is ordered. The Accounting Feature for z/os has as a prerequisite that you have installed the other Tivoli Decision Support for z/os features on which you want to perform accounting. The Accounting Feature for z/os is installed in the same manner as other Tivoli Decision Support for z/os components and the data is collected during normal execution of a Tivoli Decision Support for z/os collect job. Each subcomponent in the Accounting component is made up of the following set of object definitions: v A log definition (some components use more than one log definition to accommodate multiple release levels). v One or more record definitions. Each log contains one or more record types. v One record procedure definition in component parts CICS and DASD and two log and record procedure definitions for IMS. v A lookup table for account translation. The NPM and NETV component parts have a second lookup table for resource name translation. The DASD, HSMBKUP, and HSMMIGR component parts have a second lookup table to prevent collect being done twice on the same day for the same system ID and DCOLLECT record type. v A data table. The BATCH, STC, and TSO component parts each have a second data table to hold intermediate data during collect. v One or more update definitions. The update definition contains the instructions for summarizing the log data in the Tivoli Decision Support for z/os data tables. Log definitions, record definitions, log procedures, and record procedures for all predefined subsystems are shipped with Tivoli Decision Support for z/os. These definitions are outlined in the Administration Guide which contains references to the detailed descriptions of the log records in the subsystem manuals. You can use the standard Tivoli Decision Support for z/os workload period table, PERIOD_PLAN, for the Accounting component, as described in Workload period and special day tables on page 12. All subsystems use the workload period table. CPU utilization figures are not normalized in data tables belonging to other Tivoli Decision Support for z/os features. The same is true for the collection tables used for individual subsystems in the Accounting component. 9

26 Preparing the Accounting Feature for z/os Setting up security Trimming the data tables CPU normalization is performed during data collection in the Accounting component and normalized CPU seconds are stored in the USE_SUMMARY_D and BILLED_DATA tables. The collect process uses the resource accounting CPU normalization lookup table, CPU_NORMAL_DATA, which you update through the Tivoli Decision Support for z/os dialog. All subsystems that support CPU normalization use this normalization table. The account translation lookup tables are maintained within Tivoli Decision Support for z/os. Before you install the Accounting Feature for z/os in Tivoli Decision Support for z/os, you must have the requisite authority to do so. The system tables in Tivoli Decision Support for z/os have a default authorization ID of DRLSYS and the other tables a default authorization ID of DRL. The system tables include information about what components are available for installation, and the other tables include all data and lookup tables. Access to these tables is controlled through the RACF user groups DRL, DRLSYS, and DRLUSER, by default. To install the Accounting Feature for z/os in Tivoli Decision Support for z/os, you should first connect the installer s user ID to the RACF groups DRLSYS and DRL. You must also grant DBADM authority at the database level. For additional information on the SQL GRANT statement, see the Administration Guide. If you want to grant access to these tables to other user groups, or to individual user IDs, you must type their values in the appropriate fields of the Tivoli Decision Support for z/os dialog parameters screen. Further details about Tivoli Decision Support for z/os authorization procedures are given in the Administration Guide. If you do not plan to use all the columns in a resource accounting data table for billing, you can trim the corresponding resource accounting data tables before installing the Accounting Feature for z/os in Tivoli Decision Support for z/os by removing column definitions. This should improve the performance of the collect process and save some space in the resource accounting data tables. If you decide to remove column definitions from the resource accounting data tables, you should be familiar with the Tivoli Decision Support for z/os log collector language, described in the Language Guide and Reference To trim the resource accounting data tables, edit the member that contains the resource accounting object definition for the subsystem that you want to trim. These members are in the Tivoli Decision Support for z/os component library, called DRL170.SDRLDEFS, by default. The members for each component and their location are shown in Table 1. Table 1. List of members and their location Component Member Name Table Translation Batch DRLTBAT RAFJPOBLOG RAFBATCH RAFABATCH CICS DRLTCICS RAFCICS RAFACICS DASD DRLTDASD RAFDASD RAFADASD 10 Tivoli Decision Support for z/os: Accounting Feature for z/os

27 Preparing the Accounting Feature for z/os Table 1. List of members and their location (continued) Component Member Name Table Translation DB2 DRLTDB2 RAFDB2 RAFADB2 HSMBKUP DRLTHSMB RAFHSMBKUP RAFAHSMBKUP HSMMIGR DRLTHSMM RAFHSMMIGR RAFAHSMMIGR IMS DRLTIMS RAFIMS RAFAIMS NPM DRLTNPM RAFNETSES20 RAFNETSES4X RAFANETSESM NETV DRTLTNETV RAFNETV RAFANETV STC DRLTSTC RAFSTC RAFADDRLOG TSO DRLTTSO RAFSESLOG RAFTSO RAFASTC RAFATSO There are also some important rules that you should be aware of: v You must ensure that columns removed from the tables are not referenced by any update definitions. v In the case of normalized CPU seconds, these rules apply: If a resource accounting data table contains a CPU usage row for a given SMF ID and a matching SMF ID exists in the lookup table CPU_NORMAL_DATA, then the CPU usage is normalized by dividing the actual CPU seconds used by the normalization value in CPU_NORMAL_DATA. If a resource accounting data table contains a CPU usage row for a given SMF ID and a matching SMF ID does not exist in the lookup table CPU_NORMAL_DATA, then normalization does not take place and the actual CPU seconds are carried through to all tables. Installing the Accounting component Maintaining the lookup tables Before you can install the Accounting component in Tivoli Decision Support for z/os, you must have installed the Accounting Feature for z/os. See "Installing a Component" in the Administration Guide. After you have installed the Accounting component in Tivoli Decision Support for z/os, you will need to maintain the lookup tables used by the component. These are: v The period and special day tables v The DFSMS_LAST_RUN table for DASD, HSMBKUP, and HSMMIGR v The network resource translation table for NPM and NETV v The account translation lookup tables for each subsystem v The billing period table v The customer table v The account table v The account proration table v The credit/debit table v The CPU normalization table v The price list table Chapter 2. Preparation 11

28 Preparing the Accounting Feature for z/os The period and special day tables are shipped as part of the Tivoli Decision Support for z/os base code. If both tables were customized during the initial product installation, then the Accounting component will use the values typed in at that time. You must install the DFSMS component of Tivoli Decision Support for z/os to enable the Accounting component to use the existing DFSMS_LAST_RUN table. You must install the network components of Tivoli Decision Support for z/os to enable the Accounting component to use the network resource translation table. Workload period and special day tables Tivoli Decision Support for z/os has tables that define workload periods (shifts). They are called PERIOD_PLAN and SPECIAL_DAY. The Tivoli Decision Support for z/os collect process will reference these tables. To edit the Tivoli Decision Support for z/os tables: 1. Select Tables from the Tivoli Decision Support for z/os Administration window. 2. Select the SPECIAL_DAY table (do not press Enter). 3. Select Edit from the menu bar and update the table with data for these columns: DATE DAY_TYPE 4. Select Tables from the Tivoli Decision Support for z/os Administration window. 5. Select the PERIOD_PLAN table (do not press Enter). 6. Select Edit from the menu bar and update the table with data for these columns: PERIOD_PLAN_ID DAY_TYPE START_TIME END_TIME PERIOD_NAME The PERIOD_PLAN_ID must be % or a more specific value that will match the SMF ID of the data collected in to the Accounting component. The DAY_TYPE must be MON, TUE, WED, THU, FRI, SAT, or SUN or a value that you typed in the SPECIAL_DAY table. If you want your workload periods to be continuous, the END_TIME of one period must equal the START_TIME of another. DCOLLECT LAST_RUN lookup table Because DASD, HSMBKUP, and HSMMIGR are snapshot subsystems, it is important that you do not collect data for the same resources twice on the same day. Tivoli Decision Support for z/os helps you control this through the use of a lookup table called DFSMS_LAST_RUN. Each time the Tivoli Decision Support for z/os collect is performed for these component parts, this table will be updated with the date of the DCOLLECT run for each OS/390 system ID and data type. This control mechanism also means that you cannot run Tivoli Decision Support for z/os collects for these component parts out of sequence. That is, you cannot collect for June 21, 1997 after you collect for June 22, Tivoli Decision Support for z/os: Accounting Feature for z/os

29 Network resource translation table If you want to use an application or subsystem ID when defining billing units for the NPM or NETV subsystem, you must maintain the network resource translation table. This table translates resource names used by the subsystem into resource synonyms or groups for accounting purposes. If you do not maintain this table, the synonym and group columns will be blank. This table is described in the Network Performance feature manuals. Preparing for collect Preparing the Accounting Feature for z/os You must have the Tivoli Decision Support for z/os Network Performance feature installed to use the resource translation table called NW_RESOURCE. You maintain this through the Tivoli Decision Support for z/os network administration dialog, as described in the Administration Guide. The Accounting component collects data for each subsystem from the Tivoli Decision Support for z/os logs listed in Table 2. Table 2. Tivoli Decision Support for z/os logs and sample collect job for each subsystem Subsystem Log name Sample collect job BATCH SMF DRLJCOLL CICS SMF DRLJCOLL DASD DCOLLECT DRLJCOLL DB2 SMF DRLJCOLL HSMBKUP DCOLLECT DRLJCOLL HSMMIGR DCOLLECT DRLJCOLL IMS IMS_V710_COLLECT DRLJCOIM NPM SMF DRLJCOLL NETV SMF DRLJCOLL STC SMF DRLJCOLL TSO SMF DRLJCOLL Except for the IMS component, to collect data into Tivoli Decision Support for z/os, you normally use the sample batch job DRLJCOLL, supplied with the Tivoli Decision Support for z/os base product in the DRL170.SDRLCNTL library and described in the Administration Guide. As supplied, DRLJCOLL is set up to collect data from the SMF log. If you are collecting for a subsystem that uses a different log, you must change the COLLECT statement to read from the correct log. You may also need to make some other changes, which are described in this section. Normally, Tivoli Decision Support for z/os will collect data for all update definitions that use the same log in one run. If you want to restrict the collect to just one resource accounting subsystem, and to exclude other subsystems and Tivoli Decision Support for z/os components that use the same log, change the COLLECT statement to include the subsystem table only. For example, to collect data for the TSO subsystem only, the COLLECT statement could INCLUDE the TSO data table name, as follows: COLLECT SMF INCLUDE &PREFIX.RAFTSO; Chapter 2. Preparation 13