Accounting Feature for the Host

Transcription

1 Tioli Decision Support for OS/390 Accounting Feature for the Host Version 1.6, December 2003 SH

2

3 Tioli Decision Support for OS/390 Accounting Feature for the Host Version 1.6, December 2003 SH

4 Note Before using this information and the product it supports, read the information in Notices on page 93. Sixth Edition (June 2003) This edition applies to ersion 1, release 6 of Tioli Decision Support for OS/390 (product number ) 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 resered. Note to U.S. Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

5 Contents Figures Preface ii Who should read this book ii What this book contains ii Publications iii Tioli Decision Support for OS/390 library.. iii Using LookAt to look up message explanations.ix Accessing publications online x Ordering Publications x Accessibility x Contacting software support x Conentions used in this book xi Typeface conentions xi Part 1. Accounting feature guide... 1 Chapter 1. Oeriew of the Accounting feature Collecting usage data Producing billing information Setting prices Output from the Accounting feature Working with the Accounting feature an example 4 Considerations Customers and accounts Billing units Prices Chapter 2. Preparing the Accounting feature How the Accounting feature works 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 Understanding Accounting feature tables Table types Data tables Summary tables Lookup tables Views Chapter 4. Prorating oerhead accounts DRLJPROR sample job Distributing oerhead accounts based on fixed percentages Distributing oerhead accounts based on relatie percentages Part 2. Accounting feature reference Chapter 5. Data flow Oeriew 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 Oerhead accounts data flow Billing process data flow Chapter 6. Data tables and iews 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 iew ACCT_PRORATEV2 iew BILLED_DATA data table Chapter 7. Lookup tables ACCOUNT ACCT_PRORATE BILLING_PERIOD CPU_NORMAL_DATA CREDIT_DEBIT CUSTOMER PRICE_LIST iii

6 Chapter 8. Accounting feature translation tables RAFABATCH RAFACICS RAFADASD RAFADB RAFAHSMBKUP RAFAHSMMIGR RAFAIMS RAFANETSESM RAFANETV RAFASTC RAFATSO Chapter 9. Accounting feature reports 83 Accounting feature report definitions Prorated account percentage alidation 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 Part 3. Appendixes Notices Trademarks List of abbreiations Glossary Index i Tioli Decision Support for OS/390: Accounting Feature for the Host

7 Figures 1. Partial iew of an RAFBATCH summary table General oeriew 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 Oerhead accounts data flow Billing process data flow Prorated account percentage alidation Charges by charge type Charges by billing period, with two currencies Billing details, partial iew Charges by charge type

8 i Tioli Decision Support for OS/390: Accounting Feature for the Host

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

10 Chapter 10, Considerations for dpam users compares the functions proided with the Tioli Decision Support for OS/390 Accounting feature with those proided with dp Accounting Manager (dpam). A list of abbreiations, glossary and index follow these chapters. Publications This section lists publications in the Tioli Decision Support for OS/390 library and any other related documents. It also describes how to access Tioli publications online and how to order Tioli publications. Tioli Decision Support for OS/390 library The following documents are aailable in the Tioli Decision Support for OS/390 library: Administration Guide, SH Proides information about initializing the Tioli Decision Support for OS/390 database and customizing and administering Tioli Decision Support for OS/390. Guide to the Reporting Dialog, SH Proides 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. Language Guide and Reference, SH Proides information for adminstrators, performance analysts, and programmers who are responsible for maintaining system log data and reports. User s Guide for the Viewer, SH Proides information about how use the graphical interface for Tioli Decision Support for OS/390. Messages and Problem Determination, SH Proides information to help operators and system programmers understand, interpret, and respond to Tioli Decision Support for OS/390 messages and codes. Accounting Feature for the Host, SH Proides information for users who want to use Tioli Decision Support for OS/390 to collect and report performance data generated by the Accounting feature. Accounting Feature for the Workstation, SH Proides information for users who want to use the Accounting Workstation Option to manage, process, and analyze financial data on a workstation. AS/400 System Performance Feature Guide and Reference, SH Proides information for administrators and users about collecting and reporting performance data generated by AS/400 systems. CICS Performance Feature Guide and Reference, SH Proides information for administrators and users about collecting and reporting performance data generated by Customer Information and Control System (CICS ). Distributed Systems Performance Feature Guide and Reference, SH iii Tioli Decision Support for OS/390: Accounting Feature for the Host

11 Proides information for administrators and users about collecting and reporting performance data generated byoperating systems and applications running on a workstation. IMS Performance Feature Guide and Reference, SH Proides information for administrators and users about collecting and reporting performance data generated by Information Management System (IMS ). Network Performance Feature Installation and Administration, SH Proides information for network analysts or programmers who are responsible for setting up the network reporting enironment. Network Performance Feature Reference, SH Proides information for network analysts or programmers who are responsible for setting up the network reporting enironment. Network Performance Feature Reports, SH Proides information for network analysts or programmers who use the Network Performance feature reports. System Performance Feature Guide, SH Proides information for performance analysts and system programmers who are responsible for meeting the serice-leel objecties established in your organization. System Performance Feature Reference Vol. I, SH Proides information for administrators and users with a ariety of backgrounds who want to use Tioli Decision Support for OS/390 to analyze Multiple Virtual Storage (MVS) or Virtual Machine (VM) performance data. System Performance Feature Reference Vol. II, SH Proides information for administrators and users with a ariety of backgrounds who want to use Tioli Decision Support for OS/390 to analyze Multiple Virtual Storage (MVS) or Virtual Machine (VM) performance data. IBM Online Library Omnibus Edition OS/390 Collection Kit, SK3T-4270 CD containing all OS/390 documentation. 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 conentional 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/osunix System Serices running OMVS). The LookAt Web site also features a mobile edition of LookAt for deices such as Pocket PCs, Palm OS, or Linux-based handhelds. So, if you hae a handheld deice with wireless access and an Internet browser, you can now access LookAt message information from almost anywhere. Preface ix

12 Accessing publications online IBM posts publications for this and all other Tioli products, as they become aailable and wheneer they are updated, to the Tioli Software Information Center Web site. The Tioli Software Information Center is located at the following Web address: Click the Tioli Decision Support for OS/390 link to access the product library. These publications are aailable in PDF or HTML format, or both. Translated documents are also aailable for some products. Note: If you print PDF documents on other than letter-sized paper, select the Fit to page check box in the Adobe Acrobat Print dialog. This option is aailable when you click File Print. Fit to page ensures that the full dimensions of a letter-sized page print on the paper that you are using. Ordering Publications You can order many Tioli publications online at the following Web site: cgibin/pbi.cgi You can also order by telephone by calling one of these numbers: In the United States: 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 ision, to use software products successfully. With this product, you can use assistie technologies to hear and naigate the interface.you can also use the keyboard instead of the mouse to operate all features of the graphical user interface. Contacting software support For additional information, see the Accessibility Appendix in the Administration Guide. If you hae a problem with any Tioli product, refer to the following IBM Software Support Web site: If you want to contact software support, see the IBM Software Support Guide at the following Web site: The guide proides information about how to contact IBM Software Support, depending on the seerity of your problem, and the following information: x Tioli Decision Support for OS/390: Accounting Feature for the Host

13 Registration and eligibility Telephone numbers and addresses, depending on the country in which you are located Information you must hae before contacting IBM Software Support Note: For Tioli NetView for OS/390 customers only, additional support is aailable on the NETVIEW CFORUM (Customer Forum) through the IBM Link system. This forum is monitored by NetView deelopers who answer questions and proide guidance. When a problem with the code is found, you are asked to open an official problem management record (PMR) to obtain resolution. Conentions used in this book This guide uses seeral conentions for special terms and actions, operating system-dependent commands and paths, and margin graphics. Typeface conentions This guide uses the following typeface conentions: Bold Italic Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text 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:) Column headings in a table Keywords and parameters in text Citations (titles of books, diskettes, and CDs) Words defined in text Emphasis of words (words as words) Letters as letters New terms in text (except in a definition list) Variables and alues you must proide Monospace Examples and code examples File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Preface xi

14 xii Tioli Decision Support for OS/390: Accounting Feature for the Host

15 Part 1. Accounting feature guide Chapter 1. Oeriew of the Accounting feature.. 3 Collecting usage data Producing billing information Setting prices Output from the Accounting feature Working with the Accounting feature an example 4 Considerations Customers and accounts Billing units Prices Chapter 2. Preparing the Accounting feature... 9 How the Accounting feature works 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 15 Understanding Accounting feature tables Table types Data tables Summary tables Lookup tables Views Chapter 4. Prorating oerhead accounts DRLJPROR sample job Distributing oerhead accounts based on fixed percentages Distributing oerhead accounts based on relatie percentages

16 2 Tioli Decision Support for OS/390: Accounting Feature for the Host

17 Chapter 1. Oeriew of the Accounting feature Collecting usage data Producing billing information The Tioli Decision Support for OS/390 Accounting feature is designed to meet the requirements of both the independent data processing center that offers serices to external clients, and the DP department that is part of a large organization offering serices to internal departments in the same organization. The Accounting feature 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, reenue, 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 serices proided. You can use the flexible pricing and billing options of the Tioli Decision Support for OS/390 Accounting feature to proide 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 serices more efficiently. The billing records proided by the Accounting feature can be forwarded to your existing inoicing system, thus helping you to integrate the financial management of your DP center with your corporate financial systems. The Accounting feature proides 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 equialent 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 as a model. With the Accounting feature you can collect and summarize the usage data from each of your subsystems. For all usage data, the Accounting feature determines: 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. The account that should be charged. You can specify which alues 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 then records both the number of CPU seconds used and the number of normalized CPU seconds. 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 hae to specify a start date and an end date for each billing period. For each billing period, customers are charged according to their leel of system usage. You specify which measurement units are used. For example, you can use 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. 3

18 Oeriew of the Accounting feature When you hae 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. Setting 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 indiidual customers or each category of customers. Output from the Accounting feature You can get both detailed reports and summaries from the Accounting feature. You can use the predefined report definitions that are included with the Accounting feature to produce standard reports in either QMF or an equialent DB2 query program. You can also define your own reports from the information in the Accounting feature DB2 database by writing new QMF procedures or by using an equialent product. From the Accounting feature billing data, you can extract billing records to be used by your DP center s inoicing system. A billing record specifies the total charge for a customer s use of DP serices during a specified period. Each billing record has a related billing specification that contains detailed information about the bill. Working with the Accounting feature 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 proided computer serices 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 ery little control oer the contribution of different DP serices. The DP manager beliees that the external customers are profitable, and that inestments 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 Accounting feature. The DP department will first test the Accounting feature 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. The program administrator decides to use the default alues proided. 4 Tioli Decision Support for OS/390: Accounting Feature for the Host

19 Oeriew of the Accounting feature Considerations Each department of Ace Inc. is defined to the Accounting feature as a customer. Some departments hae seeral accounts; other departments hae 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 serice and night serice. Two serice types (DAY and NIGHT) are defined. Each billing unit consists of a measurement unit and one of the two serice types. The DP manager decides to try three different price lists: If Ace Inc. decides to practice resource billing, CPU seconds can be defined as a unit for billing with a fixed price per second. Alternatiely, using functional billing, a price can be set for each transaction ID based on the aerage number of CPU seconds used for that transaction. By using serice billing, prices can also be set for a combination of billing units and serice types. The different price lists are tested on this log data. The purpose of the Accounting feature is to help you bill customers for computer serices. To do this, the Accounting feature needs to know: Whom you want to bill (your customers and accounts) What you want to bill for (your billing units) How much you want to charge for each billing unit (your prices) How to find out which customer used which serice and when Most of this information is contained in logs that are produced by the arious computer systems that a customer uses. The computer systems that produce these logs are called producing systems. With this information, the Accounting feature can produce billing records for each customer. The Accounting feature can work with three types of computer-usage information: 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. 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. 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 directly. The basic function of the Accounting feature can thus be summarized as follows: Input Output Processing Producing system summary tables Billing records Using the information that you proide (such as customers, billing units, and prices), transform the producing system summary tables into billing records Chapter 1. Oeriew 5

20 Oeriew of the Accounting feature Customers and accounts You must proide the following information to the Accounting feature: Which customers you want to bill Which accounts correspond to each customer Which column or combination of columns in each producing system log identifies the account You can also define certain expenses as oerheads to be distributed among arious customers. Billing units A billing unit is any unit that you use to bill customers. You can bill customers at a resource leel or a functional leel. Billing customers at a functional leel is called functional billing. If you bill customers at a resource leel, each billing unit will fall into one of these categories: A column in a producing system summary table (a base measurement unit, or BMU). For example, the number of CPU seconds. A BMU combined with a serice type. For example, the number of CPU seconds during the day shift. A BMU combined with more than one serice type. For example, the number of CPU seconds during the day shift for jobs with priority 1. If you bill customers at a functional leel, you can also define the following types of billing units: A column combined with a specific alue in another column (a deried 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 serice type. You should use the DMU construct rather than the serice type when you want to aoid double charging at both the functional and resource leels. A DMU combined with one or more serice types. For example, the number of CICS transactions when TRANS is TXN1 during the day shift. If you decide to use serice 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 Tioli Decision Support for OS/390: Accounting Feature for the Host

21 Oeriew of the Accounting feature 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 olume of serice that a customer uses. Chapter 1. Oeriew 7

22 8 Tioli Decision Support for OS/390: Accounting Feature for the Host

23 Chapter 2. Preparing the Accounting feature Tioli Decision Support for OS/390 is a base product with separate add-on features. Each feature includes a number of components, which themseles consist of the object definitions required to collect and report on a gien set of data. How the Accounting feature works The Accounting feature of Tioli Decision Support for OS/390 consists of one component with multiple subcomponents. Each subcomponent corresponds to a single subsystem data source. Some object definitions used for the Accounting feature are included with the Tioli Decision Support for OS/390 base product, while the remainder are shipped when the feature is ordered. The Accounting feature has as a prerequisite that you hae installed the other Tioli Decision Support for OS/390 features on which you want to perform accounting. The Accounting feature is installed in the same manner as other Tioli Decision Support for OS/390 components and the data is collected during normal execution of a Tioli Decision Support for OS/390 collect job. Each subcomponent in the Accounting component is made up of the following set of object definitions: A log definition (some components use more than one log definition to accommodate multiple release leels). One or more record definitions. Each log contains one or more record types. One record procedure definition in component parts CICS and DASD and two log and record procedure definitions for IMS. A lookup table for account translation. The NPM and NETV component parts hae a second lookup table for resource name translation. The DASD, HSMBKUP, and HSMMIGR component parts hae a second lookup table to preent collect being done twice on the same day for the same system ID and DCOLLECT record type. A data table. The BATCH, STC, and TSO component parts each hae a second data table to hold intermediate data during collect. One or more update definitions. The update definition contains the instructions for summarizing the log data in the Tioli Decision Support for OS/390 data tables. Log definitions, record definitions, log procedures, and record procedures for all predefined subsystems are shipped with Tioli Decision Support for OS/390. 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 Tioli Decision Support for OS/390 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 Tioli Decision Support for OS/390 features. The same is true for the collection tables used for indiidual subsystems in the Accounting component. 9

24 Preparing the Accounting feature 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 Tioli Decision Support for OS/390 dialog. All subsystems that support CPU normalization use this normalization table. The account translation lookup tables are maintained within Tioli Decision Support for OS/390. Before you install the Accounting feature in Tioli Decision Support for OS/390, you must hae the requisite authority to do so. The system tables in Tioli Decision Support for OS/390 hae 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 aailable 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 in Tioli Decision Support for OS/390, 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 leel. 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 indiidual user IDs, you must type their alues in the appropriate fields of the Tioli Decision Support for OS/390 dialog parameters screen. Further details about Tioli Decision Support for OS/390 authorization procedures are gien 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 in Tioli Decision Support for OS/390 by remoing column definitions. This should improe the performance of the collect process and sae some space in the resource accounting data tables. If you decide to remoe column definitions from the resource accounting data tables, you should be familiar with the Tioli Decision Support for OS/390 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 Tioli Decision Support for OS/390 component library, called DRL160.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 Tioli Decision Support for OS/390: Accounting Feature for the Host

25 Preparing the Accounting feature 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: You must ensure that columns remoed from the tables are not referenced by any update definitions. In the case of normalized CPU seconds, these rules apply: If a resource accounting data table contains a CPU usage row for a gien SMF ID and a matching SMF ID exists in the lookup table CPU_NORMAL_DATA, then the CPU usage is normalized by diiding the actual CPU seconds used by the normalization alue in CPU_NORMAL_DATA. If a resource accounting data table contains a CPU usage row for a gien 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 Tioli Decision Support for OS/390, you must hae installed the Accounting feature. See "Installing a Component" in the Administration Guide. After you hae installed the Accounting component in Tioli Decision Support for OS/390, you will need to maintain the lookup tables used by the component. These are: The period and special day tables The DFSMS_LAST_RUN table for DASD, HSMBKUP, and HSMMIGR The network resource translation table for NPM and NETV The account translation lookup tables for each subsystem The billing period table The customer table The account table The account proration table The credit/debit table The CPU normalization table The price list table Chapter 2. Preparation 11

26 Preparing the Accounting feature The period and special day tables are shipped as part of the Tioli Decision Support for OS/390 base code. If both tables were customized during the initial product installation, then the Accounting component will use the alues typed in at that time. You must install the DFSMS component of Tioli Decision Support for OS/390 to enable the Accounting component to use the existing DFSMS_LAST_RUN table. You must install the network components of Tioli Decision Support for OS/390 to enable the Accounting component to use the network resource translation table. Workload period and special day tables Tioli Decision Support for OS/390 has tables that define workload periods (shifts). They are called PERIOD_PLAN and SPECIAL_DAY. The Tioli Decision Support for OS/390 collect process will reference these tables. To edit the Tioli Decision Support for OS/390 tables: 1. Select Tables from the Tioli Decision Support for OS/390 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 Tioli Decision Support for OS/390 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 alue 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 alue 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. Tioli Decision Support for OS/390 helps you control this through the use of a lookup table called DFSMS_LAST_RUN. Each time the Tioli Decision Support for OS/390 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 Tioli Decision Support for OS/390 collects for these component parts out of sequence. That is, you cannot collect for June 21, 1997 after you collect for June 22, Tioli Decision Support for OS/390: Accounting Feature for the Host

27 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 You must hae the Tioli Decision Support for OS/390 Network Performance feature installed to use the resource translation table called NW_RESOURCE. You maintain this through the Tioli Decision Support for OS/390 network administration dialog, as described in the Administration Guide. The Accounting component collects data for each subsystem from the Tioli Decision Support for OS/390 logs listed in Table 2. Table 2. Tioli Decision Support for OS/390 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_V510_COLLECT IMS_V610_COLLECT IMS_V710_COLLECT DRLJCOIM NPM SMF DRLJCOLL NETV SMF DRLJCOLL STC SMF DRLJCOLL TSO SMF DRLJCOLL Preparing the Accounting feature Except for the IMS component, to collect data into Tioli Decision Support for OS/390, you normally use the sample batch job DRLJCOLL, supplied with the Tioli Decision Support for OS/390 base product in the DRL160.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, Tioli Decision Support for OS/390 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 Tioli Decision Support for OS/390 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: Chapter 2. Preparation 13

28 Preparing the Accounting feature COLLECT SMF INCLUDE &PREFIX.RAFTSO; For full details of the syntax of the Tioli Decision Support for OS/390 COLLECT statement, refer to the Language Guide and Reference. While most resource accounting subsystems use the DRLJCOLL job to collect data, the IMS subsystem has a different job, called DRLJCOIM. This is supplied with the Tioli Decision Support for OS/390 base product. This job is described in this section, along with other information that you must consider when preparing subsystems for collect. Further information about this subject is proided in the Tioli Decision Support for OS/390 feature manuals, which are aailable whether or not you hae installed the Tioli Decision Support for OS/390 features themseles. 14 Tioli Decision Support for OS/390: Accounting Feature for the Host

29 Chapter 3. Implementing the Accounting feature The Accounting feature uses computer-usage information from logs produced by computer systems such as CICS, SMF or IMS. These systems can be configured so that each time the system is used, a record is added to a log. A log usually contains information such as an account number, a time stamp, and the number of CPU seconds. This information is used by the Accounting feature as the basis for calculating charges to the consumers of these resources. The computer systems that generate these logs are called producing systems. The Accounting feature collects logs from a number of producing systems, processes the information and stores it as summary tables in its own database. Understanding Accounting feature tables Tables in the Accounting feature database contain a fixed number of predefined columns and a ariable number of rows. The number of rows in each table aries because rows are added during data collection and deleted during database maintenance. If a table is compared to a sequential file, a row in the table corresponds to a record in the file, and a column corresponds to a field in the record. The columns that contain identification data, such as time stamp and system ID, are called key columns. Key columns uniquely identify a row in a table. The columns that contain measurement data, such as processor time, number of jobs, and response times, are called data columns. Some tables also contain computed columns (irtual columns) that are computed from the alues in other columns in the same row. Computed columns are not stored in the database. Figure 1 shows the arrangement of rows and columns in part of a collect feature summary table Column name -- - YEAR - MONTH - DAY - PERIOD - SYSID - ACCOUNT NJOBS - CPUSEC Row JAN P1 - SYSA - ACCT Row JAN P1 - SYSB - ACCT Row JAN P1 - SYSC - ACCT Key columns Data columns - Figure 1. Partial iew of an RAFBATCH summary table Table types The Accounting feature database consists of the following types of tables: Data tables Summary tables Lookup tables System tables Views 15

30 Implementing the Accounting feature During the data collection process, the Accounting feature first reads the log data, record by record, into Accounting feature data tables. The Accounting feature adds installation-dependent data from lookup tables, which you, in turn, maintain through the dialog. The data collection process ends with a summary of the data, for example, by calculating the number of jobs that were run and storing the result in summary tables. Data tables Data tables map the input records that are collected by the Accounting feature. Data tables usually contain one row for each selected record from the input log data. During collection, the Accounting feature checks to see whether any lookup tables apply to the input logs. If any do, it merges information from these lookup tables with the log data. Some collect processing uses assembler exits to process input fields (user column computation exit) or the entire input record (record build exit). Summary tables Summary tables summarize data contained in data tables. Data is summarized on a daily basis, and can also be summarized by groups, such as account ID, period, or transaction ID. Lookup tables Lookup tables hold user-entered data used for translating specific data from the input logs before it is summarized into the summary tables. Views Data from one or more summary tables can be combined. This combination of data is called a iew. Use a iew when you need to combine data to produce a comprehensie report. Views, like tables, hae recorded names and structures. Howeer, unlike tables, iews cannot hold stored data and are referenced only at reporting time when the data from the tables is merged in the report. 16 Tioli Decision Support for OS/390: Accounting Feature for the Host

31 Chapter 4. Prorating oerhead accounts Prorating is the allocation of oerhead accounts to some or all customers. You can allocate costs based on fixed percentages or as ariable percentages based on a resource such as CPU usage. For example, when you calculate the charge rate for CPU usage, diide the total cost that you want to recoer by the amount of CPU used only by the customers that will be charged. By excluding the oerhead use of CPU in this rate calculation, you distribute the oerhead CPU usage to all other users of the CPU. 17

32 DRLJPROR sample job DRLJPROR sample job The DRLJPROR sample job prorates oerhead accounts. To obtain an accurate iew of the costs by customer for the current billing date, run this job eery day after the last collect. //DRLJPROR JOB (ACCT ), ACC PROR JOB //*************************************************************** //* * //* LICENSED MATERIALS - PROPERTY OF IBM * //* * //* (C) COPYRIGHT IBM CORPORATION 2003 * //* SEE COPYRIGHT INSTRUCTIONS. * //* * //*************************************************************** //* * //* NAME: DRLJPROR * //* * //* STATUS: TIVOLI DECISION SUPPORT FOR OS/ * //* * //* FUNCTION: * //* ACCOUNT PRORATION JOB. * //* * //* * //* * //* * //* NOTES: * //* BEFORE YOU SUBMIT THE JOB MODIFY WITH CORRECT VALUES: * //* - THE TIVOLI DECISION SUPPORT FOR OS/390 * //* DS NAMES (DEFAULT=DRL160) * //* - THE DB2 DATA SET NAMES (DEFAULT=DSN610) * //* - THE DB2 SUBSYSTEM NAME (DEFAULT IS DSN) * //* AND SYSTEM TABLE PREFIX (DEFAULT IS DRLSYS). * //* - THE DB2 PR TABLE PREFIX (DEFAULT IS DRL) * //* - INSERT THE CORRECT BILLING PERIOD VALUE IN THE SET * //* CLAUSE (DEFAULT IS 1999_12) * //* * //*************************************************************** //COLLECT EXEC PGM=DRLPLC,PARM=( SYSTEM=DSN SYSPREFIX=DRLSYS ) //STEPLIB DD DISP=SHR,DSN=DRL160.SDRLLOAD // DD DISP=SHR,DSN=DSN610.SDSNLOAD //DRLIN DD * SET BILLING_PERIOD = 2000_12 ; RECALCULATE DRL.USE_SUMMARY_D, DRL.BILLED_DATA FROM DRL.ACCT_PRORATEV2; //DRLLOG //DRLOUT //DRLOUT //DRLDUMP DD DUMMY DD SYSOUT=*,DCB=(RECFM=F,LRECL=80) DD SYSOUT=*,DCB=(RECFM=F,LRECL=80) DD SYSOUT=*,DCB=(RECFM=VB,LRECL=32756) 18 Tioli Decision Support for OS/390: Accounting Feature for the Host

33 Distributing oerhead accounts based on fixed percentages Distributing oerhead accounts based on fixed percentages To distribute the cost of oerhead accounts based on fixed percentages: 1. In the ACCOUNT lookup table, type Y in the OV_FLAG column for each account that is an oerhead account. This flag preents the oerhead accounts from flowing to the BILLED_DATA table until the account distribution job is run. 2. In the ACCT_PRORATE lookup table for each customer: a. Type FIXED in the PRORATE_TYPE column of ACCOUNT_ID1. b. Type the percentage in the PERCENTAGE column of ACCOUNT_ID1. Percentages should total 100% for each oerhead account that is to be prorated. 3. If you want to confirm that the percentages for each account total 100%, run the RAFA001 resource accounting report. For more information about the report, see Prorated account percentage alidation report on page Customize the DRLJPROR sample job for your organization: a. Change the Tioli Decision Support for OS/390 data set names. b. Change the DB2 data set names. c. Change the DB2 subsystem name and system table prefix. d. Change the DB2 Tioli Decision Support for OS/390 table prefix. e. Change the ariable BILLING_PERIOD in the SET statement to the alue of the correct billing period. 5. Run the customized DRLJPROR job. Chapter 4. Prorating oerheads 19