performance reporter for os/390 accounting...

TME 10 IBM

Performance Reporter for OS/390Accounting Feature:Guide and ReferenceRelease 3

SH19-4495-00

Note

Before using this information and the product it supports, be sure to read the general information under “Notices”on page ix.

ISO 9001 Certification

This product was developed using an ISO 9001 certified quality system.

Certification has been awarded by the Italian quality system certification group, CSQ.

CSQ is a member of the mutually recognized organization of European assessors, ITSQ, which assesses andcertifies quality systems in the field of information technology enterprises.

First Edition (January 1998)

This edition applies to Release 3 Modification Level 0 of TME 10 Performance Reporter for OS/390, Program Number 5695-101,and to all subsequent releases and modifications until otherwise indicated in new editions. Make sure you are using the correctedition for the level of the product. This product was previously known as Enterprise Performance Data Manager/MVS (EPDM).

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at theaddress given below.

IBM welcomes your comments. A form for readers' comments is provided at the back of this publication. If the form has beenremoved, address your comments to:

Information DevelopmentRome Tivoli LaboratoryIBM Italy S.p.A.Via Sciangai, 5300144 RomeItaly

You can also send your comments by fax +39 6 5966 2077 or electronic mail:

Internet: [email protected]

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believesappropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1998. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTrademarks and service marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiWho should use this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiHow to use this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivWhere to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Performance Reporter library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Part 1. Accounting Feature Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Overview of the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Collecting usage data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Producing billing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Setting prices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4The output from the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Working with the Accounting feature—an example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Customers and accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Billing units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Prices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Preparing the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7How Performance Reporter and the Accounting feature work together . . . . . . . . . . . . . . . . . . . 7Setting up security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Trimming the data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installing the Accounting component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Maintaining the lookup tables in Performance Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Workload period and special day tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10DCOLLECT LAST_RUN lookup table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Network resource translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Preparing for collect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3. Implementing the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Understanding Accounting feature tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Summary tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Lookup tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Part 2. Accounting Feature Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4. Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Overview of Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17DFSMS Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18CICS Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Copyright IBM Corp. 1998 iii

STC, BATCH, TSO Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20DB2 Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21NPM and NetView Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22IMS data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Overhead accounts data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Billing process data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Credit debit processing data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5. Data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27RAFBATCH data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27RAFJOBLOG data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29RAFCICS data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31RAFDASD data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33RAFDB2 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34RAFHSMBKUP data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36RAFHSMMIGR data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37RAFIMS data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38RAFNETSES20 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39RAFNETSES4X data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41RAFNETV data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42RAFSTC data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43RAFADDRLOG data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44RAFTSO data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46RAFSESLOG data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47USE_SUMMARY_D data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48USE_SUMMARY_D2 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49USE_SUMMARY_D3 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50USE_SUMMARY_D4 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 6. Accounting feature lookup tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53ACCOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53ACCT_PRORATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54BILLED_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55BILLING_PERIOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57CPU_NORMAL_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58CREDIT_DEBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59CUSTOMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60PRICE_LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 7. Accounting feature translation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63RAFABATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63RAFACICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64RAFADASD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65RAFADB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66RAFAHSMBKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67RAFAHSMMIGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68RAFAIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69RAFANETSESM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70RAFANETV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71RAFASTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72RAFATSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 8. Accounting feature reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Accounting feature report definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

iv Accounting Feature Guide and Reference

Prorated account percentage validation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Charges by billing period report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Billing details report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Charges for selected billing period report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 9. Considerations for dpAM users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Contents v

vi Accounting Feature Guide and Reference

Figures

1. List of members and their location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92. Performance Reporter logs and sample collect job for each subsystem . . . . . . . . . . . . . . . 123. Partial view of an RAFBATCH summary table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134. DFSMS component data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175. DFSMS component data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186. CICS component data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197. STC, Batch, TSO component data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208. DB2 component data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219. NPM and NETV components data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

10. IMS component data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2311. Overhead accounts data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2412. Billing process data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2513. Credit debit processing data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2614. ACCOUNT table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5315. ACCOUNT_PRORATE table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5416. BILLED_DATA table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5517. BILLING_PERIOD table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5718. CPU_NORMAL_DATA table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5819. CREDIT_DEBIT table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5920. CUSTOMER table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6021. PRICE_LIST table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6122. Prorated account percentage validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7523. Charges by charge type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7624. Billing details, partial view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7725. Charges by charge type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7826. dpAM and Accounting feature comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Copyright IBM Corp. 1998 vii

viii Accounting Feature Guide and Reference

Notices

References in this publication to IBM products, programs, or services do not imply that IBM intends tomake these available in all countries in which IBM operates. Any reference to an IBM product, program,or service is not intended to state or imply that only IBM’s product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe any of IBM’s intellectual propertyrights may be used instead of the IBM product, program, or service. Evaluation and verification ofoperation in conjunction with other products, except those expressly designated by IBM, is the user’sresponsibility.

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

IBM Director of LicensingIBM Corporation500 Columbus AvenueThornwood NY 10594USA

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

IBM CorporationP.O. Box 121953039 CornwallisResearch Triangle Park, NC 27709-2195USA

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

Copyright IBM Corp. 1998 ix

Trademarks and service marks

The following terms are trademarks of Tivoli Systems, Inc.

The following terms are trademarks of the IBM Corporation in the United States or other countries or both:

Tivoli Tivoli Management EnvironmentTivoli Management Framework Tivoli Management PlatformTivoli Manager Tivoli/AdminTivoli/Enterprise Console Tivoli/SentryTME TME 10

AD/Cycle ADSTARACF/VTAM AIXAIXwindows AIX/6000AS/400 ATBookManager CBPDOCICS CICS/ESACICS/MVS Common User AccessCUA C/370Database 2 DB2DFSMS DFSMSdfpDFSMSdss DFSMShsmDFSMS/MVS DFSORTDistributed Database Connection Services/2 Distributed Relational Database ArchitectureDRDA Enterprise System/3090Enterprise System/9000 ES/9000ESA/370 ESCONExtended Services Extended Services for OS/2FFST FFST/MVSFFST/2 First Failure Support TechnologyGDDM HACMP/6000Hipersorting HiperspaceIBM IBMLinkIMS IMS/ESALoadLeveler Library ReaderMVS MVS/DFPMVS/ESA MVS/XANetView OPCOperating System/2 Operating System/400OS/2 OS/390OS/400 Presentation ManagerPrint Services Facility Processor Resource/SystemsProcessor Resource/Systems Manager PR/SMPSF QMFRACF Resource Measurement FacilityRETAIN RISC System/6000RMF RS/6000SAA SMP/ESOM SOMobjectsSP SPM/2System Object Model System/36System/390 Virtual Machine/Enterprise Systems ArchitectureVirtual Machine/Extended Architecture VisualAgeVM/ESA VM/XAVTAM Workplace Shell

x Accounting Feature Guide and Reference

UNIX is a registered trademark in the United States and other countries licensed exclusively throughX/Open Company Limited.

C-bus is a trademark of Corollary, Inc.

Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of MicrosoftCorporation.

Other company, product, and service names, which may be denoted by a double asterisk (**), may betrademarks or service marks of others.

Notices xi

xii Accounting Feature Guide and Reference

About this book

This book describes how to use Performance Reporter for OS/390 to collect and report performance datagenerated by the Accounting feature of TME 10 Performance Reporter for OS/390.

Who should use this book

The Accounting Feature Guide and Reference 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 billthe 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 Performance Reporter applications for deciding which services can be charged forand on what basis the charges should be made.

� Administrators, primarily as a guide to feature installation and as a reference to table and reportdefinitions.

� Users who are interested in analyzing the Accounting feature data.

Copyright IBM Corp. 1998 xiii

How to use this book

This book contains two parts:

� Use Part 1, “Accounting Feature Guide” for an overview of the Performance Reporter Accountingfeature and as a guide to using it.

– Chapter 1, “Overview of the Accounting feature” contains an overview of the feature and gives anexample of how you can use it.

– Chapter 2, “Preparing the Accounting feature” explains how the Accounting feature andPerformance Reporter work together. This chapter contains installation information and explainshow to work with the Accounting feature tables.

– Chapter 3, “Implementing the Accounting feature” explains the Accounting feature tables.

� Use Part 2, “Accounting Feature Reference” as a reference while you use the Accounting feature.

– Chapter 4, “Data flow” explains the data flow.

– Chapter 5, “Data tables” contains examples of the data tables.

– Chapter 6, “Accounting feature lookup tables” contains examples of the lookup tables.

– Chapter 7, “Accounting feature translation tables” contains examples of the translation tables.

– Chapter 8, “Accounting feature reports” contains examples of the Accounting feature reports.

– Chapter 9, “Considerations for dpAM users” compares the functions provided with thePerformance Reporter Accounting feature with those provided with dp Accounting Manager(dpAM).

Where to find more information

Guide to Reporting Dialog describes how to use the Performance Reporter reporting dialog to printreports. Also, Performance Reporter provides extensive online help whenever you use PerformanceReporter dialogs from the host or from a workstation; this help gives you access to the online versions ofbooks in the Performance Reporter library.

xiv Accounting Feature Guide and Reference

Performance Reporter library

The Performance Reporter books are also available online. They are distributed on CD-ROM in IBMOnline Library Omnibus Edition: OS/390 Collection, order number SK2T-6700.

While using any Performance Reporter dialog, you can use the help pull-down to start BookManager andview any of these books.

Administration

Reporting dialogs

Programming

Problem determination

Performance analysis

Administration Guide | Accounting Feature Guide and Reference

SH19-6816 | SH19-4495

AS/400 System Performance Feature Guide andReference

SH19-4019

Guide to the Reporting Dialog Capacity Planner Feature Guide and ReferenceSH19-6842 SH19-4021

Reporting Dialog/2 Feature Guide CICS Performance Feature Guide and ReferenceSH19-6843 SH19-6820

IMS Performance Feature Guide and Reference

SH19-6825

Language Guide and Reference Network Performance Feature Installation andAdministrationSH19-6817

SH19-6901

Network Performance Feature Reference

SH19-6822

Messages and Problem Determination Network Performance Feature ReportsSH19-6902 SH19-6821

System Performance Feature Guide

SH19-6818

| System Performance Feature Reference Volume I

| SH19-6819

| System Performance Feature Reference Volume II

| SH19-4494

| Workstation Performance Feature Guide and| Reference| SH19-4018

About this book xv

xvi Accounting Feature Guide and Reference

Part 1. Accounting Feature Guide

Chapter 1. Overview of the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Collecting usage data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Producing billing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Setting prices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4The output from the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Working with the Accounting feature—an example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Customers and accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Billing units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Prices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Preparing the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7How Performance Reporter and the Accounting feature work together . . . . . . . . . . . . . . . . . . . 7Setting up security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Trimming the data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installing the Accounting component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Maintaining the lookup tables in Performance Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Workload period and special day tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10DCOLLECT LAST_RUN lookup table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Network resource translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Preparing for collect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3. Implementing the Accounting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Understanding Accounting feature tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Summary tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Lookup tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Copyright IBM Corp. 1998 1

2 Accounting Feature Guide and Reference

Chapter 1. Overview of the Accounting feature

The Performance Reporter Accounting feature is designed to meet the requirements of both theindependent data processing center that offers services to external clients, and the DP department that ispart of a large organization offering services to internal departments in the same organization. TheAccounting feature helps you run your DP center either as a cost center, distributing the budgeted costsequitably among the defined customers, or as a profit center, with the focus on prices, revenue, cost, andprofit.

The complex process of distributing data processing costs often confuses the users, who find it difficult torelate the billed costs to the services provided. You can use the flexible pricing and billing options of thePerformance Reporter Accounting feature to provide the customers of your data processing center with abetter understanding of their data processing costs, thus enabling them to manage their use of DPservices more efficiently.

The billing records provided by the Accounting feature can be forwarded to your existing invoicing system,thus helping you to integrate the financial management of your DP center with your corporate financialsystems. The Accounting feature provides you with the means to successfully manage the businessaspects of DP across the entire enterprise.

The data is stored in a DB2 relational database, and QMF or an equivalent DB2 query program can beused to create standard reports. In addition, you can use QMF or another report writer to generate yourown reports, using the SQL statements supplied with the Accounting feature as a model.

Collecting usage data

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 ofday, the day of the week, and whether a day is a holiday.

� The account that should be charged. You can specify which values in the usage logs correspond toeach account.

If your DP center has more than one processor, you can specify normalization factors to account fordifferent processor speeds. The Accounting feature then records both the number of CPU seconds usedand 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 couldbe January 1998, February 1998, and so on. You have to specify a start date and an end date for eachbilling period.

For each billing period, customers are charged according to their level of system usage. You specifywhich measurement units are used. For example, you can use basic resource units such as CPUseconds, for resource billing, or functional units such as CICS transactions, for functional billing. You canuse 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 thesame as your measurement units, or more complex. For example, you can create one billing unit for CPU


Accounting feature overview

seconds during the day and another billing unit for CPU seconds at night. You can also base your billingunits 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 anddiscounts that you specify for that billing unit.

You can also supplement the usage logs by specifying recurrent charges and occasional charges andrefine your accounting records with corrections, credits, and reconciliation amounts.

Setting prices

You specify the price of each billing unit by creating price lists. You can create a single price list to usefor all customers, or create a different price list for individual customers or each category of customers.

The output from the Accounting feature

You can get both detailed reports and summaries from the Accounting feature. You can use thepredefined report definitions that are included with the Accounting feature to produce standard reports ineither QMF or an equivalent DB2 query program. You can also define your own reports from theinformation in the Accounting feature DB2 database by writing new QMF procedures or by using anequivalent product.

From the Accounting feature billing data, you can extract billing records to be used by your DP center'sinvoicing system. A billing record specifies the total charge for a customer's use of DP services during aspecified period. Each billing record has a related billing specification that contains detailed informationabout the bill.

Working with the Accounting feature—an example

Ace Inc. is a manufacturing company. As a result of rationalization and consolidation, it possesses morecomputer resources than it needs for its manufacturing process and company administration. The dataprocessing 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 aconsiderable portion of the internal budget, but there is very little control over the contribution of differentDP services. The DP manager believes that the external customers are profitable, and that investments innew applications would be worthwhile.

As a result of discussions between the financial department and the DP department, Ace Inc. decides toimplement a new DP accounting policy using the Accounting feature. The DP department will first test theAccounting 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 programadministrator decides to use the default values provided.

Each department of Ace Inc. is defined to the Accounting feature as a customer. Some departments haveseveral accounts; other departments have only one. The terminal ID and user ID for each log recorddetermine which account is charged.

The program administrator decides to use some of the default measurement units defined for the differentproducing 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 andone of the two service 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 afixed price per second.

� Alternatively, using functional billing, a price can be set for each transaction ID based on the averagenumber of CPU seconds used for that transaction.

� 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.

Considerations

The purpose of the Accounting feature is to help you bill customers for computer services. To do this, theAccounting 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 service and when

Most of this information is contained in logs that are produced by the various computer systems that acustomer uses. The computer systems that produce these logs are called producing systems. With thisinformation, 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 weeklysnapshot of the amount of DASD used by each account.

� Information that is not contained in logs or snapshots. For example, you might want to chargecustomers 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 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:

� 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 overheads to be distributed among various customers.

Chapter 1. Overview of the Accounting feature 5


Billing units

A billing unit is any unit that you use to bill customers. You can bill customers at a resource level or afunctional 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:

� 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 service type. For example, the number of CPU seconds during the day shift.

� A BMU combined with more than one service type. For example, the number of CPU seconds duringthe 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:

� One 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 oneservice type. You should use the DMU construct rather than the service type when you want to avoiddouble charging at both the functional and resource levels.

� A DMU combined with one or more service types. For example, the number of CICS transactionswhen 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.

Prices

You must specify the price for each billing unit in a price list. You can specify one price list that applies toall customers, or specify different price lists for different customers. You can also specify discounts basedon the volume of service that a customer uses.


Chapter 2. Preparing the Accounting feature

Performance Reporter for OS/390 is ordered as a base product with separate add-on features. Eachfeature includes a number of components, which themselves consist of the object definitions required tocollect and report on a given set of data.

How Performance Reporter and the Accounting feature work together

The Accounting feature of Performance Reporter consists of one component with multiple subcomponents.Each subcomponent corresponds to a single subsystem data source. Some object definitions used for theAccounting feature are included with the Performance Reporter base product, while the remainder areshipped when the feature is ordered. The Accounting feature has as a prerequisite that you have installedthe other Performance Reporter features on which you want to perform accounting.

The Accounting feature is installed in the same manner as other Performance Reporter components andthe data is collected during normal execution of a Performance Reporter 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 releaselevels).

� 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 recordprocedure definitions for IMS.

� A lookup table for account translation. The NPM and NETV component parts have a second lookuptable for resource name translation. The DASD, HSMBKUP, and HSMMIGR component parts have asecond lookup table to prevent collect being done twice on the same day for the same system ID andDCOLLECT record type.

� A data table. The BATCH, STC, and TSO component parts each have a second data table to holdintermediate data during collect.

� One or more update definitions. The update definition contains the instructions for summarizing thelog data in the Performance Reporter data tables.

Log definitions, record definitions, log procedures, and record procedures for all predefined subsystemsare shipped with Performance Reporter. These definitions are outlined in the Performance ReporterAdministration Guide, which contains references to the detailed descriptions of the log records in thesubsystem manuals.

You can use the standard Performance Reporter workload period table, PERIOD_PLAN, for theAccounting component, as described in “Workload period and special day tables” on page 10. Allsubsystems use the workload period table.

CPU utilization figures are not normalized in data tables belonging to other Performance Reporterfeatures. The same is true for the collection tables used for individual subsystems in the Accountingcomponent.


Setting up security

CPU normalization is performed during data collection in the Accounting component and normalized CPUseconds are stored in the USE_SUMMARY_D and BILLED_DATA tables. The collect process uses theresource accounting CPU normalization lookup table, CPU_NORMAL_DATA, which you update throughthe Performance Reporter dialog. All subsystems that support CPU normalization use this normalizationtable.

The account translation lookup tables are maintained within Performance Reporter.

Setting up security

Before you install the Accounting feature in Performance Reporter, you must have the requisite authorityto do so. The system tables in Performance Reporter have a default authorization ID of DRLSYS and theother tables a default authorization ID of DRL. The system tables include information about whatcomponents 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, bydefault. To install the Accounting feature in Performance Reporter, you should first connect the installer'suser ID to the RACF groups DRLSYS and DRL. You must also grant DBADM authority at the databaselevel. For additional information on the SQL GRANT statement, see the Performance ReporterAdministration Guide.

If you want to grant access to these tables to other user groups, or to individual user IDs, you must entertheir values in the appropriate fields of the Performance Reporter dialog parameters screen. Furtherdetails about Performance Reporter authorization procedures are given in the Performance ReporterAdministration Guide.


Trimming the data tables

Trimming the data tables

If you do not plan to use all the columns in a resource accounting data table for billing, you can trim thecorresponding resource accounting data tables before installing the Accounting feature in PerformanceReporter by removing column definitions. This should improve the performance of the collect process andsave some space in the resource accounting data tables.

If you decide to remove column definitions from the resource accounting data tables, you should befamiliar with the Performance Reporter log collector language, described in the Language Guide andReference. To trim the resource accounting data tables, edit the member that contains the resourceaccounting object definition for the subsystem that you want to trim. These members are in thePerformance Reporter component library, called DRL130.SDRLDEFS, by default. The members for eachcomponent and their location are shown in Figure 1.

There are also some important rules that you should be aware of:

� You must ensure that columns removed 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 given SMF ID and a matchingSMF ID exists in the lookup table CPU_NORMAL_DATA, then the CPU usage is normalized bydividing 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 matchingSMF ID does not exist in the lookup table CPU_NORMAL_DATA, then normalization does nottake place and the actual CPU seconds are carried through to all tables.

Figure 1. List of members and their location

Component Member Name Table Translation

Batch DRLTBAT RAFJPOBLOGRAFBATCH

RAFABATCH

CICS DRLTCICS RAFCICS RAFACICS

DASD DRLTDASD RAFDASD RAFADASD

DB2 DRLTDB2 RAFDB2 RAFADB2

HSMBKUP DRLTHSMB RAFHSMBKUP RAFAHSMBKUP

HSMMIGR DRLTHSMM RAFHSMMIGR RAFAHSMMIGR

IMS DRLTIMS RAFIMS RAFAIMS

NPM DRLTNPM RAFNETSES20RAFNETSES4X

RAFANETSESM

NETV DRTLTNETV RAFNETV RAFANETV

STC DRLTSTC RAFSTCRAFADDRLOG

RAFASTC

TSO DRLTTSO RAFSESLOGRAFTSO

RAFATSO

Chapter 2. Preparing the Accounting feature 9

Maintaining lookup tables

Installing the Accounting component

Before you can install the Accounting component in Performance Reporter, you must have installed theAccounting feature. See "Installing a Component"in the Performance Reporter Administration Guide.

Maintaining the lookup tables in Performance Reporter

After you have installed the Accounting component in Performance Reporter, you will need to maintain thelookup 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

The period and special day tables are shipped as part of the Performance Reporter base code. If bothtables were customized during the initial Performance Reporter installation, then the Accountingcomponent will use the values entered at that time.

You must install the DFSMS component of Performance Reporter to enable the Accounting component touse the existing DFSMS_LAST_RUN table.

You must install the network components of Performance Reporter to enable the Accounting component touse the network resource translation table.

Workload period and special day tables

Performance Reporter has tables that define workload periods (shifts). They are called PERIOD_PLANand SPECIAL_DAY.

The Performance Reporter collect process will reference these tables.

To edit the Performance Reporter tables:

1. Select Tables from the Performance Reporter 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

1. Select Tables from the Performance Reporter Administration window.

2. Select the PERIOD_PLAN table (do not press enter).

3. Select Edit from the menu bar and update the table with data for these columns:


Maintaining lookup tables

PERIOD_PLAN_ID END_TIME

DAY_TYPE PERIOD_NAME

START_TIME

The PERIOD_PLAN_ID must be % or a more specific value that will match the SMF ID of the datacollected in to the Accounting component.

The DAY_TYPE must be 'MON', 'TUE', 'WED', 'THU', 'FRI', 'SAT', or 'SUN' or a value that you enter in theSPECIAL_DAY table. If you want your workload periods to be continuous, the END_TIME of one periodmust 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 notcollect data for the same resources twice on the same day. Performance Reporter helps you control thisthrough the use of a lookup table called DFSMS_LAST_RUN. Each time the Performance Reportercollect is performed for these component parts, this table will be updated with the date of the DCOLLECTrun for each OS/390 system ID and data type.

This control mechanism also means that you cannot run Performance Reporter collects for thesecomponent parts out of sequence. That is, you cannot collect for June 21, 1997 after you collect for June22, 1997.

Network resource translation table

If you want to use an application or subsystem ID when defining billing units for the NPM or NETVsubsystem, you must maintain the network resource translation table. This table translates resourcenames used by the subsystem into resource synonyms or groups for accounting purposes. If you do notmaintain this table, the synonym and group columns will be blank. This table is described in the NetworkPerformance feature manuals.

You must have the Performance Reporter Network Performance feature installed to use the resourcetranslation table called NW_RESOURCE. You maintain this through the Performance Reporter networkadministration dialog, as described in the Performance Reporter Administration Guide.

Chapter 2. Preparing the Accounting feature 11

Preparing for collect

Preparing for collect

The Accounting component collects data for each subsystem from the Performance Reporter logs listed inFigure 2.

Except for the IMS component, to collect data in to Performance Reporter, you normally use the samplebatch job DRLJCOLL, supplied with the Performance Reporter base product in the DRL130.SDRLCNTLlibrary and described in the Performance Reporter Administration Guide.

As supplied, DRLJCOLL is set up to collect data from the SMF log. If you are collecting for a subsystemthat uses a different log, you must change the COLLECT statement to read from the correct log. You mayalso need to make some other changes, which are described in this section.

Normally, Performance Reporter will collect data for all update definitions that use the same log in onerun. If you want to restrict the collect to just one resource accounting subsystem, and to exclude othersubsystems and Performance Reporter components that use the same log, change the COLLECTstatement 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;

For full details of the syntax of the Performance Reporter COLLECT statement, refer to the LanguageGuide and Reference.

While most resource accounting subsystems use the DRLJCOLL job to collect data, the IMS subsystemhas a different job, called DRLJCOIM. This is supplied with the Performance Reporter base product. Thisjob is described in this section, along with other information that you must consider when preparingsubsystems for collect.

Further information about this subject is provided in the Performance Reporter feature manuals, which areavailable whether or not you have installed the Performance Reporter features themselves.

Figure 2. Performance Reporter 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_V310_COLLECTIMS_V410_COLLECTIMS_V510_COLLECTIMS_V610_COLLECT

DRLJCOIM

NPM SMF DRLJCOLL

NETV SMF DRLJCOLL

STC SMF DRLJCOLL

TSO SMF DRLJCOLL


Chapter 3. Implementing the Accounting feature

The Accounting feature uses computer-usage information from logs produced by computer systems suchas CICS, SMF or IMS. These systems can be configured so that each time the system is used, a recordis added to a log. A log usually contains information such as an account number, a time stamp, and thenumber of CPU seconds. This information is used by the Accounting feature as the basis for calculatingcharges to the consumers of these resources. The computer systems that generate these logs are calledproducing systems.

The Accounting feature collects logs from a number of producing systems, processes the information andstores 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 variablenumber of rows. The number of rows in each table varies because rows are added during data collectionand 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 acolumn 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 responsetimes, are called data columns.

Some tables also contain computed columns (virtual columns) that are computed from the values in othercolumns in the same row. Computed columns are not stored in the database.

Figure 3 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 ---------- - 93 - JAN - 15 - P1 - SYSA - ACCT1 - - 15ðð - 2ð -

Row ---------- - 93 - JAN - 15 - P1 - SYSB - ACCT2 - - 7ðð - 15 -

Row ---------- - 93 - JAN - 15 - P1 - SYSC - ACCT3 - - 9ðð - 13 -

+------------------------------------------------------------------------

--------------------- Key columns ------------------- ---- Data columns -

Figure 3. Partial view 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


Types of tables

During the data collection process, the Accounting feature first reads the log data, record by record, intoAccounting feature data tables. The Accounting feature adds installation-dependent data from lookuptables, which you, in turn, maintain through the dialog. The data collection process ends with a summaryof the data, for example, by calculating the number of jobs that were run and storing the result in summarytables.

Data tables

Data tables map the input records that are collected by the Accounting feature. Data tables usuallycontain 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 usesassembler exits to process input fields (user column computation exit) or the entire input record (recordbuild exit).

Summary tables

Summary tables summarize data contained in data tables. Data is summarized on a daily basis, and canalso 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 issummarized into the summary tables.

Views

Data from one or more summary tables can be combined. This combination of data is called a view. Usea view when you need to combine data to produce a comprehensive report.

Views, like tables, have recorded names and structures. However, unlike tables, views cannot hold storeddata and are referenced only at reporting time when the data from the tables is merged in the report.


Part 2. Accounting Feature Reference

Chapter 4. Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Overview of Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17DFSMS Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18CICS Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19STC, BATCH, TSO Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20DB2 Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21NPM and NetView Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22IMS data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Overhead accounts data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Billing process data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Credit debit processing data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 5. Data tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27RAFBATCH data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27RAFJOBLOG data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29RAFCICS data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31RAFDASD data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33RAFDB2 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34RAFHSMBKUP data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36RAFHSMMIGR data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37RAFIMS data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38RAFNETSES20 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39RAFNETSES4X data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41RAFNETV data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42RAFSTC data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43RAFADDRLOG data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44RAFTSO data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46RAFSESLOG data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47USE_SUMMARY_D data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48USE_SUMMARY_D2 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49USE_SUMMARY_D3 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50USE_SUMMARY_D4 data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 6. Accounting feature lookup tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53ACCOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53ACCT_PRORATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54BILLED_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55BILLING_PERIOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57CPU_NORMAL_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58CREDIT_DEBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59CUSTOMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60PRICE_LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 7. Accounting feature translation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63RAFABATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63RAFACICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64RAFADASD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65


RAFADB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66RAFAHSMBKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67RAFAHSMMIGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68RAFAIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69RAFANETSESM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70RAFANETV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71RAFASTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72RAFATSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 8. Accounting feature reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Accounting feature report definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Prorated account percentage validation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Charges by billing period report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Billing details report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Charges for selected billing period report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 9. Considerations for dpAM users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


Chapter 4. Data flow

Overview of Data Flow

This chapter shows a general overview of the data flow in the Performance Reporter Accounting featureand the data flow in the various components of the Accounting feature.

Figure 4 shows a general overview of the data flow.

┌────────┐

│ Log │

└───┬────┘

│

│

6

┌────────────────┐

│Detail Subsystem│

│ table │

└───────┬────────┘

│

│

│

│

│

6

┌────────────┐

│USE_SUMMARY │

│ table │

│ │

└─────┬──────┘

│

│

6

┌──────────────┐

│ BILLED_DATA │

│ table │

│ │

└──────────────┘

Figure 4. DFSMS component data flow


DFSMS data flow

DFSMS Data flow

The DFSMS component of the Accounting feature collects records from the DCOLLECT facility, whichextracts data from VTOCs and the DFHSM control data sets. The component then stores the informationin tables in the Performance Reporter Accounting feature tables. Figure 5 shows an overview of the flowof data within the DFSMS component.

┌─────┐ ┌─────┐

│VTOC ├───┐ ┌───┤DFHSM│

└─────┘ │ │ └─────┘

6 6

┌──────────┐

│DCOLLECT │

└────┬─────┘

│

┌──────────────────────┼────────────────────────────────────────────┐

│ │ Performance Reporter │

│ ┌─────────────────┼────────────────────────────────────────┐ │

│ │ │ Collect │ │

│ │ 6 │ │

│ │ ┌───────────────────────┐ │ │

│ │ │ Record │ │ │

│ │ │ Definitions │ │ │

│ │ ├───────────────────────┤ │ │

│ │ │DCOLLECT_A DCOLLECT_M │ │ │

│ │ │DCOLLECT_B DCOLLECT_T │ │ │

│ │ │DCOLLECT_C DCOLLECT_V │ │ │

│ │ │DCOLLECT_AG DCOLLECT_LB│ │ │

│ │ │DCOLLECT_BC DCOLLECT_MC│ │ │

│ │ │DCOLLECT_DC DCOLLECT_SC│ │ │

│ │ │DCOLLECT_DR DCOLLECT_SG│ │ │

│ │ │DCOLLECT_VL │ │ │

│ │ └────┬───────┬──────────┘ │ │

│ │ │ │ │ │

│ │ │ │ │ │

│ │ │ 6 │ │

│ │ │ ┌────────────────┐ │ │

│ │ │ │ Record │ │ │

│ │ │ │ Procedure │ │ │

│ │ │ ├────────────────┤ │ │

│ │ │ │ DRL2DCOL │ │ │

│ │ │ └─┬──────────────┘ │ │

│ │ │ 6 │ │

│ │ │ ┌────────────────┐ │ │

│ │ │ │ Record │ │ │

│ │ │ │ definition │ │ │

│ │ │ ├────────────────┤ │ │

│ │ │ │ DCOLLECT_DA │ │ │

│ │ │ └─┬──────────────┘ │ │

│ │ │ │ │ │

│ │ 6 6 │ │

│ │ ┌───────────────────┐ │ │

│ │ │ Data Tables │ │ │

│ │ ├───────────────────┤ ┌───────────────────┐ │ │

│ │ │ RAFDASD | | Lookup Tables | | |

│ │ │ DFSMS_LAST_RUN_D | ├───────────────────┤ | |

│ │ │ | |RAFADASD | | |

│ │ │ |%──────┤DFSMS_LAST_RUN | | |

│ │ │ | | | | |

│ │ │ | | | | |

│ │ │ | └───────────────────┘ | |

│ │ │ | | |

│ │ │ | | |

│ │ └─────────┬─────────┘ │ │

│ │ │ │ │

│ │ │ │ │

│ └────────────────┼─────────────────────────────────────────┘ │

│ 6 ┌───────────────────┐ │

│ ┌──────────────┐ │ Lookup Tables │ │

│ │Summary Table │ ├───────────────────┤ │

│ ├──────────────┤%───────────┤ BILLING_PERIOD | |

│ │USE_SUMMARY_D │ │ ACCOUNT | |

│ └──────────────┘ └───────────────────┘ │

└───────────────────────────────────────────────────────────────────┘

Figure 5. DFSMS component data flow


CICS data flow

CICS Data flow

The CICS component of the Accounting feature collects SMF log data recorded by CICS and stores thedata in the Performance Reporter database. You can use the Reporting Dialog to create reports based onthis data.

Figure 6 shows an overview of the flow of data from the CICS licensed program, through the CICScomponent of the Performance Reporter Accounting feature, and finally into usable reports.

┌───────┐

│ CICS │

└───┬───┘

│

6

┌───────────────────┐

│ SMF │

└─────────┬─────────┘

┌───────────────────┼────────────────────────────────────────────┐


│ ┌────────────────┼───────────────────────────────────────┐ │


│ │ 6 │ │

│ │ ┌─────────────┐ │ │

│ │ │ Record │ │ │


│ │ ├─────────────┤ │ │

│ │ │ SMF_CICS_T │ │ │

│ │ └──────┬──────┘ │ │

│ │ │ │ │

│ │ │ │ │

│ │ 6 │ │

│ │ ┌───────────────────┐ │ │


│ │ ├───────────────────┤ │ │

│ │ │ RAFCICS | ┌─────────────┐ │ │

│ │ │ | │Lookup Table │ │ │

│ │ │ | ├─────────────┤ │ │

│ │ │ |%──────┤RAFACICS │ │ │

│ │ │ | └─────────────┘ │ │

│ │ └─────────┬─────────┘ │ │

│ │ │ │ │

│ │ 6 ┌───────────────┐ │ │

│ │ ┌───────────────────┐ │Lookup Tables │ │ │

│ │ │ Summary Tables | ├───────────────┤ │ │

│ │ ├───────────────────| │CPU_NORMAL_DATA│ │ │

│ │ │USE_SUMMARY_D |%──────┤BILLING_PERIOD │ │ │

│ │ │ | │ACCOUNT │ │ │

│ │ │ | └───────────────┘ │ │

│ │ └───────────────────┘ │ │

│ └────────────────────────────────────────────────────────┘ │

│ │

│ │

│ │

│ │

│ │

│ │

│ │

└────────────────────────────────────────────────────────────────┘

Figure 6. CICS component data flow

Chapter 4. Data flow 19

STC, BATCH, TSO data flow

STC, BATCH, TSO Data flow

The STC, Batch, and TSO components of the Accounting feature collect records from the SMF data setand store extracted and summarized data in the Performance Reporter database.

Figure 7 shows the flow of STC, Batch, and TSO data.

┌───────────────────┐

│ STC BATCH TSO │

└─────────┬─────────┘

│

6

┌───────────────────┐

│ SMF │

└─────────┬─────────┘

┌───────────────────┼────────────────────────────────────────────┐


│ ┌────────────────┼───────────────────────────────────────┐ │


│ │ 6 │ │

│ │ ┌───────────────────┐ │ │

│ │ │Record Definitions | │ │

│ │ ├───────────────────| │ │

│ │ │ SMF_ðð6 SMF_ð26 | │ │

│ │ │ SMF_ð25 SMF_ð3ð | │ │

│ │ └─────────┬─────────┘ │ │

│ │ │ │ │

│ │ 6 │ │

│ │ ┌───────────────────┐ │ │

│ │ │Data Tables │ │ │

│ │ ├───────────────────| │ │

│ │ │RAFJOBLOG RAFSESLOG| │ │

│ │ │RAFADDRLOG │ │ │

│ │ └─────────┬─────────┘ │ │

│ │ │ │ │

│ │ 6 ┌────────────────┐ │ │

│ │ ┌───────────────────┐ │Lookup Tables │ │ │

│ │ │Data Tables │ ├────────────────┤ │ │

│ │ ├───────────────────| │ RAFASTC │ │ │

│ │ │ RAFBATCH RAFTSO |%─────┤ RAFATSO │ │ │

│ │ │ RAFSTC │ │ RAFABATCH │ │ │

│ │ └─────────┬─────────┘ └────────────────┘ │ │

│ │ 6 ┌────────────────┐ │ │

│ │ ┌───────────────────┐ │ Lookup Tables │ │ │

│ │ │ Summary Table │ ├────────────────┤ │ │

│ │ ├───────────────────| │ CPU_NORMAL_DATA│ │ │

│ │ │ USE_SUMMARY_D |%─────┤ BILLING_PERIOD │ │ │

│ │ └───────────────────┘ │ ACCOUNT │ │ │

│ │ └────────────────┘ │ │

│ └────────────────────────────────────────────────────────┘ │

│ │

│ │

│ │

│ │

│ │

│ │

│ │

└────────────────────────────────────────────────────────────────┘

Figure 7. STC, Batch, TSO component data flow


DB2 data flow

DB2 Data flow

The DB2 component of the Accounting feature collects SMF log data recorded by DB2 and stores the datain the accounting table. You can use the Reporting Dialog to create reports based on this data.

Figure 8 shows an overview of the flow of data from the DB2 licensed program, through the DB2component of the Performance Reporter Accounting feature, and finally into usable reports.

┌───────┐

│ DB2 │

└───┬───┘

│

6

┌───────────────────┐

│ SMF │

└─────────┬─────────┘

┌───────────────────┼────────────────────────────────────────────┐


│ ┌────────────────┼───────────────────────────────────────┐ │


│ │ 6 │ │

│ │ ┌─────────────┐ │ │

│ │ │ Record │ │ │


│ │ ├─────────────┤ │ │

│ │ │ SMF_1ð1 │ │ │

│ │ └──────┬──────┘ │ │

│ │ │ │ │

│ │ │ │ │

│ │ 6 │ │

│ │ ┌───────────────────┐ │ │


│ │ ├───────────────────┤ │ │

│ │ │ RAFDB2 │ │ │

│ │ │ │ ┌─────────────┐ │ │

│ │ │ │ │ Lookup Table│ │ │

│ │ │ │ ├─────────────┤ │ │

│ │ │ │%─────┤ RAFADB2 │ │ │

│ │ │ │ └─────────────┘ │ │

│ │ └─────────┬─────────┘ │ │

│ │ │ │ │

│ │ 6 │ │

│ │ ┌───────────────────┐ ┌───────────────┐ │ │

│ │ │ Summary_Tables | │Lookup Table │ │ │

│ │ ├───────────────────| ├───────────────┤ │ │

│ │ │ USE_SUMMARY_D |%─────┤CPU_NORMAL_DATA│ │ │

│ │ │ | │BILLING_PERIOD │ │ │

│ │ │ | │ACCOUNT │ │ │

│ │ └───────────────────┘ └───────────────┘ │ │

│ └────────────────────────────────────────────────────────┘ │

│ │

│ │

│ │

│ │

│ │

│ │

│ │

└────────────────────────────────────────────────────────────────┘

Figure 8. DB2 component data flow


NPM and NetView data flow

NPM and NetView Data flow

The NPM and NetView components of the Accounting feature collect records from the SMF data set andstore extracted and summarized data in the Performance Reporter database.

Figure 9 shows the flow of NPM and NETV data.

┌───────────────────┐

│ NPM NETV │

└─────────┬─────────┘

│

6

┌───────────────────┐

│ SMF │

└─────────┬─────────┘

┌───────────────────┼────────────────────────────────────────────┐


│ ┌────────────────┼───────────────────────────────────────┐ │


│ │ 6 │ │

│ │ ┌───────────────────┐ │ │

│ │ │ SMF_ð28 | │ │

│ │ │ SMF_ð39_1_Tð_1 | │ │

│ │ │ | │ │

│ │ │ | │ │

│ │ │ | │ │

│ │ └─────────┬─────────┘ │ │

│ │ │ │ │

│ │ │ │ │

│ │ 6 │ │

│ │ ┌───────────────────┐ ┌───────────────┐ │ │

│ │ │ RAFNETSES2ð | │Lookup Table │ │ │

│ │ │ RAFNETSES4X | ├───────────────┤ │ │

│ │ │ |%─────┤NW_RESOURCE │ │ │

│ │ │ | │RAFNETV │ │ │

│ │ │ | │ │ │ │

│ │ └─────────┬─────────┘ └───────────────┘ │ │

│ │ │ │ │

│ │ 6 │ │

│ │ ┌───────────────────┐ ┌───────────────┐ │ │

│ │ │ Summary Table | │Lookup Table │ │ │

│ │ ├───────────────────| ├───────────────┤ │ │

│ │ │ USE_SUMMARY_D |%─────┤ │ │ │

│ │ │ | │BILLING_PERIOD │ │ │

│ │ │ | │ACCOUNT │ │ │

│ │ └───────────────────┘ └───────────────┘ │ │

│ └────────────────────────────────────────────────────────┘ │

│ │

│ │

│ │

│ │

│ │

│ │

│ │

└────────────────────────────────────────────────────────────────┘

Figure 9. NPM and NETV components data flow


IMS data flow

IMS data flow

The IMS component of the Accounting feature collects records for the composite records created by theIMS feature of Performance Reporter and stores the data in the Performance Reporter database.

Figure 10 shows the IMS component data flow.

┌───────────────────┐

│ |

│ IMS_VXXX_R2 |

│ |

└─────────┬─────────┘

│

│

6

┌───────────────────┐ ┌───────────────┐

│ RAFIMS | │Lookup Table │

│ | ├───────────────┤

│ |%─────┤RAFAIMS │

│ | │ │

└─────────┬─────────┘ └───────────────┘

│

6

┌───────────────────┐ ┌───────────────┐

│ Summary Table │ │Lookup Table │

├───────────────────┤ ├───────────────┤

│ USE_SUMMARY_D │%─────┤CPU_NORMAL_DATA│

│ │ │BILLING_PERIOD │

└───────────────────┘ │ACCOUNT │

└───────────────┘

Figure 10. IMS component data flow

Notes:

You must install at least one of the IMS collect components before you install the IMS subcomponentof the Accounting feature. For example, if you have installed the IMS 6.2 collect component, you canproceed with the installation of the IMS subcomponent.

You may receive some error messages during the installation process if you installed the IMS collectcomponent for another version of IMS. You can ignore these error messages and work with the IMScollect component that you have installed.


Overhead Accounts data flow

Overhead accounts data flow

Figure 11 shows the overhead accounts data flow.

┌────────────────────────────────────────────────────────┐

│ │

│ │

│ ┌───────────────────┐ │

│ │ USE_SUMMARY_D | │

│ │ | │

│ └─────────┬─────────┘ │

│ │ │

│ │ │

│ 6 │

│ ┌─────────────────┐ ┌───────────────┐ │

│ │ USE_SUMMARY_D2 │ │ │ │

│ │ USE_SUMMARY_D3 │ │ PRICE_LIST │ │

│ │ USE_SUMMARY_D4 │%──────┤ │ │

│ │ BILLED_DATA │ │ │ │

│ └─────────────────┘ └───────────────┘ │

│ │

│ │

└────────────────────────────────────────────────────────┘

Figure 11. Overhead accounts data flow


Billing process data flow

Billing process data flow

Figure 12 shows the billing process data flow.

┌────────────────────────────────────────────────────────┐

│ │

│ │

│ ┌───────────────────┐ │

│ │ ACCT_PRORATE | │

│ │ | │

│ └─────────┬─────────┘ │

│ │ │

│ │ │

│ 6 │

│ ┌─────────────────┐ ┌───────────────┐ │

│ │ BILLED_DATA │%──────┤USE_SUMMARY_Dx │ │

│ │ │ │ │ │

│ └─────────────────┘ └───────────────┘ │

│ │

│ │

└────────────────────────────────────────────────────────┘

Figure 12. Billing process data flow


Credit debit processing data flow

Credit debit processing data flow

Figure 13 shows the credit debit processing data flow.

┌────────────────────────────────────────────────────────┐

│ │

│ │

│ ┌───────────────────┐ │

│ │ CREDIT_DEBIT | │

│ │ | │

│ └─────────┬─────────┘ │

│ │ │

│ │ │

│ 6 │

│ ┌─────────────────┐ ┌───────────────┐ │

│ │ BILLED_DATA │%──────┤ PRICE_LIST │ │

│ │ │ │BILLING_PERIOD │ │

│ └─────────────────┘ └───────────────┘ │

│ │

│ │

└────────────────────────────────────────────────────────┘

Figure 13. Credit debit processing data flow


Chapter 5. Data tables

RAFBATCH data table

This table contains summarized data for the BATCH producing system. It contains records created byjobs run under JES2 or JES3. The source for these is SMF record types 6, 25, 26, and 30 (subtype 5).

Column name Data type Description

ACCOUNT k CHAR(8) The account ID, obtained using the mapping rules in the tableRAFBATCH.

DATE k DATE The day the reader recognized the JOB cards, obtained fromSMF30RSD.

FUNCTION k CHAR(8) This is by default the first character of the job name. This canbe changed by the user to give any other value desired.

JOBCLASS k CHAR(8) The job class, obtained from SMF30CLS.

JOBNAME k CHAR(8) The job or session name, obtained from SMF30JBN,SMF26JBN, SMF25JBN, or SMF6JBN.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAP',SMF30RSD, SMF25RSD, SMF26RSD, or SMF6RSD andSMF30RST, SMF25RST, SMF26RST, or SMF6RST asparameters in the PERIOD function.

SYSID k CHAR(8) The system ID, obtained from SMF30SID.

CPUNMSEC FLOAT This is the normalized CPU time, calculated during import asCPUSEC/CP_POWER, where CP_POWER is obtained bylooking up SYSID in the CPU normalization table.

CPUSEC FLOAT This is the total time taken by the jobs in seconds, calculatedas SUM(SRBTIME + TCBTIME + IIPTIME + HCTTIME +RCTTIME), obtained from SMF30CPT, SMF30CPS, SMF30IIP,SMF30HCT, and SMF30RCT.

DISKBLKS FLOAT This is the number of blocks issued for DASD devices,obtained from SMF30BLK, where SMF30DEV = hex'20'.

DISKMNTS FLOAT This is the number of DASD mounts for the job, obtained asSUM(SMF30PDM + SMF30PRD + SMF25NDM).

EXCPS FLOAT This is the number of total blocks issued, calculated as sum ofDISKBLKS, TAPEBLKS, and OTHERBLKS, all obtained fromSMF30BLK.

GRAFBLKS FLOAT The number of blocks issued for graphic devices, obtained fromSMF30BLK, where SMF30DEV = hex'00'.

LAST_COLLECT_TIME TIMESTAMP This is the last time collect was done for this table.

LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the BATCH producingsystem.

MSSBLKS FLOAT This is the number of blocks issued for MSS devices, obtainedfrom SMF30BLK, where SMF30DEV = hex'42'.

NJOBS FLOAT This is the total number of jobs, calculated asCOUNT(CPUTIME).

NPAGES FLOAT The approximate physical page count, including duplicates andseparators, calculated as SUM(SMF6PGE).


RAFBATCH data table


OCRBLKS FLOAT This is the number of blocks issued for OCR devices, obtainedfrom SMF30BLK, where SMF30DEV = hex'04'.

OTHRBLKS k FLOAT This is the number of blocks issued for devices other thanDASD and TAPE devices, obtained from SMF30BLK.

PRTLINES FLOAT This is the number of output lines generated to spool, obtainedfrom SMF26XLN.

SRBTIME FLOAT This is the time under service request block (SRB) in seconds,obtained from SMF30CPS.

TAPEBLKS FLOAT This is the number of blocks issued for tape devices, obtainedfrom SMF30BLK, where SMF30DEV = hex'80'.

TAPEMNTS FLOAT This is the number of tape mounts for the job, obtained asSUM(SMF30PTM + SMF30TPR + SMF25NTM).

TCBTIME FLOAT This is the total number of CPU seconds under task controlblock (TCB), obtained from SMF30CPT.

WTRLINES FLOAT The number of logical records written by the writer, calculatedas SUM(SMF6NLR)


RAFJOBLOG data table


This table contains intermediate data for the BATCH producing system summarized at day level. It iscreated by jobs run under JES2 or JES3. The sources for this table are SMF record types 6, 25, 26, and30 (subtype 5).


J_TIMESTAMP k TIMESTAMP The date and time when the reader recognized the job cards,obtained from SMF30RSD and SMF30RST.

J_JOBNAME k CHAR(8) The name of the job, obtained from SMF30JBN.

J_ACCT1 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the first accounting section.

J_ACCT2 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the second accountingsection.

J_ACCT3 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the third accounting section.

J_ACCT4 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the fourth accounting section.

J_ACCT5 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the fifth accounting section.

J_FUNCTION CHAR(8) A field the value of which can be decided by the user. Defaultvalue of this column is the first character of JOBNAME.

J_HPTTIME FLOAT The time consumed to support requests for data to betransferred between a hiperspace and an address space,calculated as SMF30HCT/100.

J_IIPTIME FLOAT The time used to process I/O interrupts, calculated asSMF30IIP/100.

J_JOBCLASS CHAR(8) The job class, obtained from SMF30CLS.

J_MDISKS FLOAT The number of disk mounts for the job, calculated asSUM(SMF30PDM + SMF30PRD + SMF25NDM).

J_MTAPES FLOAT The number of tape mounts for the job calculated asSUM(SMF30PTM + SMF30TPR + SMF25NTM).

J_NDISKBLKS FLOAT The number of blocks issued for DASD for the job, obtainedfrom SMF30BLK, where SMF30DEV = hex'20'.

J_NGRAFBLKS FLOAT The number of blocks issued for graphic devices for the job,obtained from SMF30BLK, where SMF30DEV = hex'00'.

J_NLINES FLOAT The number of lines dumped by the job, obtained fromSMF26XLN.

J_NMSSBLKS FLOAT The number of blocks issued for MSS devices for the job,obtained from SMF30BLK where SMF30DEV = hex'42'.

J_NOCRBLKS FLOAT The number of blocks issued for OCR devices for the job,obtained from SMF30BLK where SMF30DEV = hex'04'.

J_NOTHRBLKS FLOAT The number of blocks issued for devices other than disk andtape devices, obtained from SMF30BLK.

J_NPAGES FLOAT The approximate physical page count, including duplicates andseparators, calculated as SUM(SMF6PGE).

Chapter 5. Data tables 29



J_NTAPEBLKS FLOAT The number of blocks issued for tape devices for the job,obtained from SMF30BLK where SMF30DEV = hex'80'.

J_PGMRNAME CHAR(8) The programmer name, obtained from SMF30USR.

J_RACFGRP CHAR(9) The RACF group, obtained from SMF30GRP.

J_RCTTIME FLOAT The time used by region control task (RCT), calculated asSMF30RCT/100.

J_SMFID CHAR(4) The system ID, obtained from SMF30SID.

J_SRBTIME FLOAT The time under service request block (SRB), in secondscalculated as SMF30CPS/100.

J_TCBTIME FLOAT The total number of CPU seconds under time control block(TCB), calculated as SMF30CPT/100.

J_USERFLD CHAR(8) A user field, obtained, by default, from the first character ofSMF30JBN, the job name.

J_USERID CHAR(8) The RACF user ID, obtained from SMF30RUD.

J_WTRLINES FLOAT The number of logical records written by the writer, calculatedas SUM(SMF6NLR).


RAFCICS data table

RAFCICS data table

This table contains summarized data for the CICS producing system.


ACCOUNT k CHAR(8) The account ID, obtained using the mapping rules specified inthe table RAFACICS.

APPLID k CHAR(8) The generic application ID, obtained from the fieldSMFMNPRN.

DATE k DATE The day on which the CICS transaction was started, obtainedfrom the field START.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAF',DATE(START), and TIME(START) as parameters in thePERIOD function.

SYSID k CHAR(8) The system ID, obtained from the field SMFMNSID.

TRANS k CHAR(8) The CICS transaction ID, obtained from TRAN.


CPUSEC FLOAT The CPU time taken for the transaction in seconds, calculatedas SUM(USRCPUT_CLOCK / 625E2).

DBCTLS FLOAT The number of DL/I requests, calculated asSUM(DBCTL_TOTC).

DLICALLS FLOAT The number of DL/I calls, calculated asSUM(DLI_CLK3_COUNT).

FCAMC FLOAT The number of file access method calls, calculated asSUM(FCAMCT).

FCIO FLOAT The number of file control I/O waits, calculated asSUM(FCIOWTT_COUNT).

JCIO FLOAT The number of journal control I/O waits, calculated asSUM(JCIOWTT_COUNT).

LAST_COLLECT_TIME TIMESTAMP This is the last time collect was done for this table.

LAST_IMPORT_TIME TIMESTAMP This is the last time import was done into for the CICSproducing system.

MAXSTOR FLOAT The peak user subpool storage, in KBYTES, used above andbelow 16MB, calculated as SUM((SCUSRHWME +SCUSRHWM)/1024).

MAXSTORB FLOAT The peak user subpool storage, in BYTES, used above andbelow 16MB, calculated as SUM(SCUSRHWME +SCUSRHWM).

NPAGEIN FLOAT The number of virtual storage page-ins calculated asSUM(PAGINCT). This value is valid for CICS Version 2 only.

NTRANS FLOAT The number of transactions, calculated as COUNT(START).

TCINPUT FLOAT The number of messages received from the primary terminal,calculated as SUM(TCMSGIN1).

TCIO FLOAT The number of terminal control I/O waits, calculated asSUM(TCIOWTT_COUNT).


RAFCICS data table


TCOUTPUT FLOAT The number of messages sent to the primary terminal,calculated as SUM(TCMSGOU1).

TDSERV FLOAT The number of transient data requests, calculated asSUM(TDTOTCT).

TSIO FLOAT The number of temporary storage I/O waits, calculated asSUM(TSIOWTT_COUNT).


RAFDASD data table

RAFDASD data table

This table contains summarized data for the DASD producing system. The data is obtained from therecord DCOLLECT_DA from the log DCOLLECT.


ACCOUNT k CHAR(8) The account ID which is obtained using the rules specified inthe table RAFADASD.

DATE k DATE The day on which the DCOLLECT was performed, obtainedfrom the field DCUDATE.

MGTCLASS k CHAR(8) The first eight characters of the management class, obtainedfrom the field DCDMCLAS.

PERIOD k CHAR(8) The name of the period obtained by using the date and timefrom the PERIOD function.

STCLASS k CHAR(8) The first eight characters of the storage class, obtained fromthe field DCDSCLAS.

STGROUP k CHAR(8) The first eight characters of the storage group, obtained fromthe field DCDSTOGP.

SYSID k CHAR(8) The system ID, obtained from the field DCUSYSID.

ALLOCSP FLOAT The total allocated space in MBYTES, calculated asSUM(DCDCALLSP/1024).

LAST_COLLECT_TIME TIMESTAMP The last time collect was done for this table.

LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the DASD producingsystem.

NDATASET FLOAT The total number of data sets, obtained asCOUNT(DCAASSOC).

UNUSEDBL FLOAT The total amount of unusable storage in MBYTES, calculatedas SUM(DCDNMBLK/1024).

UNUSEDSP FLOAT The total unused space in MBYTES, calculated asSUM((DCDCALLSP-DCDUSESP)/1024). Note that for VSAMand ISAM files this will always be zero.

USEDSP FLOAT The total used space in MBYTES, calculated asSUM(DCDUSESP/1024), except with VSAM and ISAM files,when ALLOCSP will be used instead.


RAFDB2 data table

RAFDB2 data table

This table contains summarized data for the DB2 producing system. The logs are collected from SMF logtype 101.


ACCOUNT k CHAR(8) The account ID, obtained using the mapping rules specified inthe table RAFADB2.

AUTHORIZ k CHAR(8) The authorization ID, obtained from QWHCAID.

CONNTYPE k CHAR(8) The type of system that is connected, obtained from QWHCCN.

CORRELAT k CHAR(12) The correlation ID, obtained from QWHCCV.

DATE k DATE The day on which the DB2 task was initiated, obtained from thefield SM101DTE.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAF',SM101DTE, and SM101TME as parameters in the PERIODfunction.

PLANNAME k CHAR(8) The plan name, obtained from QWHCPLAN.

SUBSYSID k CHAR(8) The DB2 subsystem ID, obtained from QWHSSSID.

SYSID k CHAR(8) The system ID, obtained from SM101SID.

ABEND FLOAT The total number of application programs which endedabnormally, calculated as SUM(ABEND) where ABEND=1when QWACRINV=20, else ABEND=0.


CPURATE FLOAT The CPU normalization factor for the given system ID.

CPUSEC FLOAT The total CPU time, calculated as SUM(TCBTIME + SRBTIME).

CRDBASE FLOAT The number of CREATE DATABASEs issued, calculated asSUM(QXCRDAB).

CRINDEX FLOAT The number of CREATE INDEXes issued, calculated asSUM(QXCRINX).

CRTABLE FLOAT The number of CREATE TABLEs issued, calculated asSUM(QXCRTAB).

CRTABSP FLOAT The number of CREATE TABLESPACEs, issued calculated asSUM(QXCTABS).

CRVIEW FLOAT The number of CREATE VIEWs issued, calculated asSUM(QXDEFVU).

DEALLOC FLOAT The total number of normal deallocations, calculated asSUM(DEALLOC) where DEALLOC=1 when QWACRINV=12,else DEALLOC=0.

DELETECALLS FLOAT The number of DELETEs issued, calculated asSUM(QXDELET).

ELAPSTIM FLOAT The total elapsed time of the application in seconds, calculatedas SUM(QWACESC-QWACBSC).

FETCHCALLS FLOAT The number of FETCHes issued, calculated asSUM(QXFETCH).


RAFDB2 data table


INSERTCALLS FLOAT The number of INSERTs issued, calculated asSUM(QXINSRT).


LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for

PGMEND FLOAT The total number of application programs terminated with workunit in doubt, calculated as SUM(PGMEND) where PGMEND=1when QWACRINV=40, else PGMEND=0. the DB2 producingsystem.

SELECTCALLS FLOAT The number of SELECTs issued, calculated asSUM(QXSELECT).

SRBTIME FLOAT The total time under service block request, calculated asSUM(QWACESRB - QWACBSRB).

TCBTIME FLOAT The total time under task control block, calculated asSUM(QWACEJST - QWACBJST).

THREADS FLOAT The number of threads processed, calculated asCOUNT(TIMESTAMP).

UPDATECALLS FLOAT The number of UPDATEs issued, calculated asSUM(QXUPDTE).


RAFHSMBKUP data table

RAFHSMBKUP data table

This table contains summarized data for the HSMBKUP producing system. The details are obtainedthrough the record DCOLLECT_B from the log DCOLLECT.


ACCOUNT k CHAR(8) The account ID, obtained by using the mapping rules specifiedin the table RAFAHSMBKUP.

DATE k DATE The day on which the collect was performed, obtained from thefield DCUDATE.

MGTCLASS k CHAR(8) The first eight characters of the management class, obtainedfrom the field UBMCLAS.

PERIOD k CHAR(8) The name of the period obtained by using the date and timefrom the PERIOD function.

STCLASS k CHAR(8) The first eight characters of the storage class, obtained fromthe field UBSCLAS.


BCKSP FLOAT The total amount of backup space in MBYTES, calculated asSUM(UBDSIZE/1024).

DBCKSP FLOAT The total amount of backup space in MBYTES on DASD,calculated as SUM(UBDSIZE * DASD/1024), where DASD=1when UBDEVCL='D', else DASD=0.


LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the HSMBKUPproducing system.

NUMDBCK FLOAT The number of DASD backup copies, obtained as SUM(DASD)where DASD=1 when UBDEVCL='D', else DASD=0.

NUMTBCK FLOAT The number of tape backup copies, obtained as SUM(TAPE)where TAPE=1 when UBDEVCL='T', else TAPE=0.

TBCKSP FLOAT The total amount of backup space in MBYTES on tape,calculated as SUM(UBDSIZE * TAPE/1024), where TAPE=1when UBDEVCL='T', else TAPE=0.


RAFHSMMIGR data table

RAFHSMMIGR data table

This table contains summarized data for the HSMMIGR producing system. The data is obtained throughthe record DCOLLECT_M from the log DCOLLECT.


ACCOUNT k CHAR(8) The account ID, obtained using the mapping rules specified inthe table RAFAHSMMIGR.

DATE k DATE The day on which the DCOLLECT was performed, obtainedfrom the field DCUDATE.

LEVEL k CHAR(8) The level of migration, obtained based on the value in the fieldUMFLAG1. When value is '01' the level is L1 and if value is'10' then the level is L2.

MGTCLASS k CHAR(8) The first eight characters of the management class, obtainedfrom the field UMMCLAS.

PERIOD k CHAR(8) The name of the period, obtained by using the date and timefrom the PERIOD function.

STCLASS k CHAR(8) The first eight characters of the storage class, obtained fromthe field UMSCLAS.


DMIGRSP FLOAT The size of DASD migration copies in MBYTES, calculated asSUM(DASD * UMDSIZE/1024), where DASD=1 whenUMDEVCL='D', else DASD=0.


LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the HSMMIGRproducing system.

MIGRSP FLOAT The total size in MBYTES of migration copies, calculated as thesum of space migrated onto TAPE and space migrated ontoDASD.

NUMDMIGR FLOAT The number of migrated data sets on DASD, calculated asSUM(DASD), where DASD=1 when UMDEVCL='D', elseDASD=0.

NUMTMIGR FLOAT The number of migrated data sets on tape, calculated asSUM(TAPE), where TAPE=1 when UMDEVCL='T', elseTAPE=0.

TMIGRSP FLOAT The size of TAPE migration copies in MBYTES, calculated asSUM(TAPE * UMDSIZE/1024), where TAPE=1 whenUMDEVCL='T', else TAPE=0.


RAFIMS data table

RAFIMS data table

This table contains summarized data for the IMS producing system. The data for this table is collectedfrom the records IMS_310_R2, IMS_410_R2, IMS_510_R2, and IMS_610_R2. in the logsIMS_310_COLLECT, IMS_410_COLLECT, IMS_510_COLLECT, and IMS_610_COLLECT, respectively.


ACCOUNT k CHAR(8) The account ID, obtained based on the mapping rules specifiedin the table RAFAIMS.

DATE k DATE The first date found for the transaction, obtained fromDRL_DATE.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAF',DRL_DATE, and DRL_TIME as parameters in the PERIODfunction.

SYSID k CHAR(8) The system ID, obtained from the collect parameterMVS_SYSTEM_ID.

TRANCLAS k CHAR(8) The transaction class, obtained from DRL_TXCLS orDRL_TRANT1. If DRL_TRANT1 = 'T' then value is '$I', ifDRL_TRANT1 = 'S' then value is '$M', else if DRL_TXCLS ='6F' or '40' then value is '$U', else value is the value ofDRL_TXCLS.

TRANS k CHAR(8) The transaction ID, obtained depending on the value of the firstcharacter in the fields DRL_TRANT and DRL_SMBNM.

TRANTYPE k CHAR(8) The transaction type, obtained from DRL_TRANT.


CPUSEC FLOAT The total time taken for the transactions, obtained asSUM(DRL_IQTM + DRL_PRTM + DRL_SQ6TM + DRL_OQTM+ DRL_TRNTM + DRL_NETTM).

DBCALLS FLOAT The total number of database calls for the transaction,calculated as SUM(DRLCLCNT).

DCCALLS FLOAT The total number of calls to message queue, calculated asSUM(DRLGNMES + DRLGUMES + DRLISMES +DRLPUMES).


LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the IMS producingsystem.

NMSGS FLOAT The total number of output messages issued to the outputqueue, calculated as SUM(DRL_OUTMSG).

NOUTCHAR FLOAT The total number of bytes of text data inserted into themessage queue, calculated as SUM(DRL_LMSGB +DRL_SMSGB).

NTRANS FLOAT The total number of transactions processed in the system.

NTRANSD FLOAT The same as NTRANS for compatibility with SLR.


RAFNETSES20 data table


This table contains summarized data for the NETSESM producing system. The logs are collected fromSMF record type 28 (subtype X'20').


ACCOUNT k CHAR(8) The account ID, obtained by using the mapping rules specifiedin the table RAFANETSESM.

ANUM k CHAR(8) The account number supplied by the session manager,obtained from LSCDANUM.

APPL k CHAR(8) Synonym of the resource, obtained from LOOKUP tableNW_RESOURCE. user.

APPLGRUP k CHAR(8) Group name of the resource, obtained from LOOKUP tableDPAMNW_RESOURCE or NW_RESOURCE if the NetworkPerformance component is installed in EPDM and the updatedefinition is modified by the user.

DATE k DATE The date on which the log record was recorded, obtained fromthe field LSAACBSK.

GROUPID k CHAR(8) The group ID supplied by the session manager, obtained fromthe field LSCDGRUP.

PCID k CHAR(8) The unique session ID, obtained from LSCDPCID.

PERIOD k CHAR(8) The name of the period, obtained from values 'RAF',SMF28DTE, and SMF28TME as parameters in the PERIODfunction. This is the date and time when the record was movedto the external log buffer.

PRIORITY k INTEGER Transmission priority, obtaind from LSCDTPF.

RESOURCE k CHAR(8) Application name. The primary logical unit (PLU) name fromACDEB. Obtained from LSCDPNAM.

SMFID k CHAR(4) SMF identifier.

SMID k CHAR(8) The name that the session manager passed to NPM in thesession manager identifier MS subvector, obtained fromLSCDSMID.

USERID k CHAR(8) The operator ID supplied by the session manager, obtainedfrom the field LSCDUSER.

XNET k CHAR(1) Cross-domain session indicator, Y/N, obtained fromLSCDXNET.

CTLSESS INTEGER Control session indicator, 0/1, obtained from LSCDFLAG.

EXTSESS INTEGER Extended session indicator, 0/1, obtained from LSCDFLAG.


LAST_IMPORT_TIME TIMESTAMP The last time import was done for the NETSESM producingsystem.

SCTLKBR FLOAT This is the sum of control kilobytes, secondary to primary(inbound control data). Obtained from LSAASCCC.

SCTLKBS FLOAT This is the sum of control kilobytes, primary to secondary(outbound control data). Obtained from LSAAPCCC.

SCTLPIUR FLOAT This is the sum of control PIUs, secondary to primary (inboundcontrol data). Obtained from LSAASCBC.




SCTLPIUS FLOAT This is the sum of control PIUs, primary to secondary(outbound control data). Obtained from LSAAPCBC.

SMSGKBR FLOAT This is the sum of message kilobytes, secondary to primary(inbound operator messages). Obtained from LSAASMCC.

SMSGKBS FLOAT This is the sum of message kilobytes, primary to secondary(outbound operator messages). Obtained from LSAAPMCC.

SMSGR FLOAT This is the sum of messages, secondary to primary (inboundoperator messages). Obtained from LSAASMBC.

SMSGS FLOAT This is the sum of messages, primary to secondary (outboundoperator messages). Obtained from LSAAPMBC.

STXTKBR FLOAT This is the sum of text kilobytes, secondary to primary (inboundoperator data). Obtained from LSAASTCC.

STXTKBS FLOAT This is the sum of text kilobytes, primary to secondary(outbound operator data). Obtained from LSAAPTCC.

STXTPIUR FLOAT This is the sum of text PIUs, secondary to primary (inboundoperator data). Obtained from LSAASTBC.

STXTPIUS FLOAT This is the sum of text PIUs, primary to secondary (outboundoperator data). Obtained from LSAAPTBC.


RAFNETSES4X data table

RAFNETSES4X data table

This table contains session time data for the NETSESM producing system. The logs are collected fromSMF record type 28 (subtypes X'48' and X'49').


DATE k DATE The date on which the log record was recorded, obtained fromthe field SMF28DTE.

PCID k CHAR(8) The unique session ID, obtained from SMAPCID.

SESSCNTE INTEGER This is the number of session ends. Obtained by countingrecords subtype X'49'.

SESSCNTS INTEGER This is the number of session starts. Obtained by countingrecords subtype X'48'.

SESSTSE TIMESTAMP The time stamp for session end. Obtained from SMATIME inrecord subtype X'49'.

SESSTSS TIMESTAMP The time stamp for session start. Obtained from SMATIME inrecord subtype X'48'.


RAFNETV data table

RAFNETV data table

This table contains summarized data for the NETV producing system. It is obtained from recordSMF_039_1_TO_7 in the SMF log.


ACCOUNT k CHAR(8) The account ID, obtained based on the mapping rules specifiedin RAFANETV.

APPLID k CHAR(8) The synonym of the VTAM resource, obtained from themapping specified in the table NW_RESOURCE.

DATE k DATE The day when the record was moved to external log buffer,obtained from LOGRDATE.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAF',LOGRDATE, and LOGRTIME as parameters in the PERIODfunction. This is the date and time when the record was movedto the external log buffer.

SYSID k CHAR(8) The system ID, obtained from LOGRSYID.

CTLBUFFX FLOAT The total number of control PIUs sent between primary andsecondary, calculated as SUM(LACCPCBC + LACCSCBC).

CTLCHARX FLOAT The total number of control bytes sent between primary andsecondary, calculated as SUM(LACCPCCC + LACCSCCC).

ELAPSTIM FLOAT The session elapsed time in hours, calculated asSUM((LACCENDT2 - LACCBEGT2)/3600) where LACCENDT2is the collection end time and LACCBEGT2 is the collectionbegin time.


LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the NETV producingsystem.

NSESS FLOAT The number of sessions calculated as SUM(NSESS) whereNSESS=1 when LOGRSUBT=2 or 5, else NSESS=0.

TXTBUFFX FLOAT The total number of text PIUs sent between primary andsecondary, calculated as SUM(LACCPTBC + LACCSTBC).

TXTCHARX FLOAT The total number of text bytes sent between primary andsecondary, calculated as SUM(LACCPTCC + LACCSTCC).


RAFSTC data table

RAFSTC data table

This table contains summarized data for the STC producing system. The logs are collected from SMF logtype 30 (subtype 4).


ACCOUNT k CHAR(8) The account ID, obtained by using the mapping rules specifiedin the table RAFASTC.

DATE k DATE The date on which the log was recorded, obtained from thefield SMF30RSD.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAF',SMF30RSD, and SMF30RST as parameters in the PERIODfunction.

STCNAME k CHAR(8) The started task name obtained from the field SMF30JBN.

SYSID k CHAR(8) The system ID, obtained from the field SMF30SID.


CPUSEC FLOAT The total time taken by the task, calculated as TCBTIME +SRBTIME + RCTTIME + HPTTIME + IIPTIME.

DISKBLKS FLOAT The number of blocks allocated for DASD devices, calculatedas SUM(SMF30BLKS) where SMF30DEV = hex'20'.

EXCPS FLOAT The number of executed channel programs, calculated asSUM(SMF30TEP).

GRAFBLKS FLOAT The number of blocks allocated for graphic devices, calculatedas SUM(SMF30BLKS) where SMF30DEV = hex'00'.


LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the STC producingsystem.

MSSBLKS FLOAT The number of blocks allocated for MSS devices, calculated asSUM(SMF30BLKS) where SMF30DEV = hex'42'.

NSTCS FLOAT The number of started task steps obtained asCOUNT(CPUTIME).

OCRBLKS FLOAT The number of blocks allocated for OCR devices, calculated asSUM(SMF30BLKS) where SMF30DEV = hex'04'.

OTHRBLKS FLOAT The number of blocks allocated for devices other than DASDand tape devices, calculated as SUM(SMF30BLKS) whereSMF30DEV <> hex'20' or hex'80'.

SRBTIME FLOAT The total time under service request block, calculated asSUM(SMF30CPS).

TAPEBLKS FLOAT The number of blocks allocated for tape devices, calculated asSUM(SMF30BLKS) where SMF30DEV = hex'80'.

TCBTIME FLOAT The total time under task control block, calculated asSUM(SMF30CPT).


RAFADDRLOG data table


This table contains intermediate data for the STC producing system summarized at day level. The sourcefor this table is SMF record type 30 (subtype 4).


A_TIMESTAMP k TIMESTAMP The date and time when the reader recognized the job cards,obtained from SMF30RSD and SMF30RST.

A_STCNAME k CHAR(8) The name of the job specified, obtained from SMF30JBN.

A_STEPNO k INTEGER The number of the step that created this record, obtained fromSMF30STN.

A_ACCT1 CHAR(8) Obtained from the first eight characters of SMF30ACT,obtained from the first accounting section.

A_ACCT2 CHAR(8) Obtained from the first eight characters of SMF30ACT,obtained from the second accounting section.

A_ACCT3 CHAR(8) Obtained from the first eight characters of SMF30ACT,obtained from the third accounting section.

A_ACCT4 CHAR(8) Obtained from the first eight characters of SMF30ACT,obtained from the fourth accounting section.

A_ACCT5 CHAR(8) Obtained from the first eight characters of SMF30ACT,obtained from the fifth accounting section.

A_HPTTIME FLOAT The time consumed to support requests for data to betransferred between a hiperspace and an address space,obtained as SMF30HCT/100.

A_IIPTIME FLOAT The time used to process I/O interrupts, calculated asSMF30IIP/100.

A_NDISKBLKS FLOAT The number of blocks issued for DASD for the job, obtainedfrom SMF30BLK where SMF30DEV = hex'20'.

A_NEXCPS FLOAT The number of executed channel programs calculated asSUM(SMF30TEP).

A_NGRAFBLKS FLOAT The number of blocks issued for graphic devices for the job,obtained from SMF30BLK where SMF30DEV = hex'00'.

A_NMSSBLKS FLOAT The number of blocks issued for MSS devices for the job,obtained from SMF30BLK where SMF30DEV = hex'42'.

A_NOCRBLKS FLOAT The number of blocks issued for OCR devices for the job,obtained from SMF30BLK where SMFDEV = hex'04'.

A_NOTHRBLKS FLOAT The number of blocks issued for devices other than disk andtape devices, obtained from SMF30BLK.

A_NTAPEBLKS FLOAT The number of blocks issued for tape devices for the job,obtained from SMF30BLK where SMF30DEV = hex'80'.

A_PGMNAME CHAR(8) The program name, obtained from SMF30PGM.

A_RACFGRP CHAR(9) The RACFGRP, obtained from SMF30GRP.

A_RCTTIME FLOAT The time used by region control task (RCT), calculated asSMF30RCT/100.

A_SMFID CHAR(4) The system ID, obtained from SMF30SID.

A_SRBTIME FLOAT The time under service request block (SRB), calculated asSMF30CPS/100 .




A_TCBTIME FLOAT The total number of CPU second under time control block(TCB), calculated as SMF30CPT/100.

A_USERFLD CHAR(8) A user field, obtained, by default, from the first character ofSMF30JBN, the job name.

A_USERID CHAR(8) The RACF user ID, obtained from SMF30RUD.


RAFTSO data table

RAFTSO data table

This table contains summarized data for the TSO producing system. The logs are collected from SMF logtype 30 (subtype 5).


ACCOUNT k CHAR(8) The account, obtained using the mapping specified in theRAFATSO table.

DATE k DATE The date on which the TSO session was started, obtained fromSMF30RSD.

PERIOD k CHAR(8) The name of the period, obtained from the values 'RAF',SMF30RSD, and SMF30RST as parameters in the PERIODfunction.

SYSID k CHAR(8) The system ID, obtained from SMF30SID.


CPUSEC FLOAT The total CPU time, calculated as SUM(SMF30IIP +SMF30RCT + SMF30HCT + SMF30TCB + SMF30SRB).

EXCPS FLOAT The total number of executed channel programs during thesession, calculated as SUM(SMF30TEP).

LAST_COLLECT_TIME TIMESTAMP The last time the collect was done for this table.

LAST_IMPORT_TIME TIMESTAMP This is the last time import was done for the TSO producingsystem.

NSESS FLOAT Number of TSO logon sessions, calculated as the count ofaccounting records.


RAFSESLOG data table

RAFSESLOG data table

This table contains intermediate data for the TSO producing system summarized at day level.


S_JOBNAME k CHAR(8) The name of the job, obtained from SMF30JBN.

S_TIMESTAMP k TIMESTAMP The date and time when the reader recognized the JOB cardsand is obtained from SMF30RSD and SMF30RST.

S_ACCT1 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the first accounting section.

S_ACCT2 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the second accountingsection.

S_ACCT3 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the third accounting section.

S_ACCT4 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the fourth accounting section.

S_ACCT5 CHAR(8) The details obtained from the ACCT parameter of the job card,obtained from the SMF30ACT of the fifth accounting section.

S_HPTTIME FLOAT The time consumed to support requests for data to betransferred between a hiperspace and an address space,calculated as SMF30HPT/100.

S_IIPTIME FLOAT The time used to process I/O interrupts, calculated asSMF30IIP/100.

S_NEXCPS FLOAT The number of executed channel programs, calculated asSUM(SMF30TEP).

S_RACFGRP CHAR(9) The RACF group, obtained from SMF30GRP.

S_RCTTIME FLOAT The time used by region control task (RCT), calculated asSMF30RCT/100.

S_SMFID CHAR(8) The system ID, obtained from SMF30SID.

S_SRBTIME FLOAT The time under service request block (SRB), calculated asSMF30CPS/100.

S_TCBTIME FLOAT The total number of CPU time under time control block (TCB),calculated as SMF30CPT/100.

S_TERMID CHAR(8) The RACF terminal ID, obtained from SMF30TID.

S_USERFLD CHAR(8) A user field, obtained, by default, from the first character ofSMF30RUD, the RACF user ID.

S_USERID CHAR(8) The RACF user ID obtained from SMF30RUD.


USE_SUMMARY_D data table

USE_SUMMARY_D data table

This table provides daily usage data for all producing systems.


ACCOUNT_ID1 k CHAR(12) Account name from usage record and/or LOOKUP.





BILLING_PERIOD k CHAR(8) Billing period from LOOKUP.

CUSTOMER_ID k CHAR(15) Customer name from LOOKUP.

DATE k DATE Date when the usage was recorded.

OU_FLAG k CHAR(1) Flag for overhead accounts.

PERIOD_NAME k CHAR(8) Time period. This is the name that you define in thePERIOD_PLAN table. Use it to group time intervals accordingto operator shifts or to separate peak and other periods.

SMF_ID k CHAR(4) MVS system ID. This is the SMF system ID. FromSMFMVSID.

SUBSYSTEM_ID k CHAR(8) Subsystem name.

CPU_SECONDS FLOAT Number of CPU seconds.

DASD_MBYTES FLOAT Number of DASD Mbytes.

DISK_EXCPS FLOAT Number of disk exceptions.

PAGES_PRINTED FLOAT Number of pages printed.

PRINT_LINES FLOAT Number of lines printed.

SESSION_KBYTES FLOAT Number of session Kbytes.

TAPE_MOUNTS FLOAT Number of tape mounts.

TAPE_EXCPS FLOAT Number of tape exceptions.


USE_SUMMARY_D2 data table


This table provides alternate grouping for USE_SUMMARY table.


BILLING_PERIOD k CHAR(8) Billing period ID from LOOKUP.












This table provides alternate grouping for USE_SUMMARY_table.


BILLING_PERIOD k CHAR(8) Billing period ID from lookup.

CUSTOMER_ID k CHAR(15) Customer ID












This table provides daily usage data for all producing systems.







BILLING_PERIOD k CHAR(8) Billing period from LOOKUP.










Chapter 6. Accounting feature lookup tables

This chapter describes the new lookup tables that are part of the Performance Reporter Accountingfeature.

ACCOUNT

This table provides account details including the customer ID that owns the table or a flag to indicate anoverhead account to be prorated.

Figure 14. ACCOUNT table


AC_AC1 k CHAR(12) First account qualifier.

AC_AC2 k CHAR(12) Second account qualifier.

AC_AC3 k CHAR(12) Third account qualifier.

AC_AC4 k CHAR(12) Fourth account qualifier.

AC_AC5 k CHAR(12) Fifth account qualifier.

AC_CUST_ID CHAR(15) Customer ID that owns this account

AC_NAME CHAR(30) Descriptive name to print on invoices

OK_FLAG CHAR(2) Y indicates that this is an overhead account that is prorated tomultiple customers in the account proration table.


ACCOUNT_PRORATE lookup table

ACCT_PRORATE

This Accounting feature table defines what account proration logic will be used, if any, for thisenvironment. This table is called ACCT_PRORATE and is referenced by the RECALCULATE functionwhen account proration is in use.

The Accounting component provides for fixed percentage proration and variable proration. Both forms ofproration are controlled through the use of the proration lookup table. The lookup table provides either thefixed percentage amount of the account to be allocated to a particular customer or it provides the variablethat will be used to prorate the charges to the customer on a relative usage basis. The default for variableproration is CPU usage. The actual account usage will be prorated to each customer based on thatcustomer's percentage of overall CPU usage during the billing period. The update definition,RAF_ACCT_PRORATE in member DRLUACCP of dataset DRL130.SDRLDEFS, can be modified toprorate account usage on any other usage variable that is collected and stored in the USE_SUMMARY_Dtable.

Note: If fixed percentage proration is used, the total of all percentages entered should equal 100.

Figure 15. ACCOUNT_PRORATE table


CUSTOMER_ID k CHAR(15) Customer name to allocate a percentage.

ACCOUNT_ID1 k CHAR(12) Account name to be prorated.





PERCENTAGE FLOAT Fixed percentage. Must add 100% for account.

PRORATE_TYPE CHAR(8) Character fixed or the variable to be used.


BILLED_DATA lookup table

BILLED_DATA

The BILLED_DATA table is shown in Figure 16.

Figure 16 (Page 1 of 2). BILLED_DATA table


SMF_ID k CHAR(4) CRDB

BP_ID k CHAR(8) Billing period.

CU_ID k CHAR(15) Customer ID.

AC1 k CHAR(12) Account ID1.





DATE k DATE Date.

PERIOD_NAME k CHAR(8) Shift associated.

CHARGE_TYPE k CHAR(1) Type of charge. The char R indicates a one-time charge.

SUBSYSTEM_ID k CHAR(8) Subsystem associated.

CPU_SECONDS_V FLOAT Sum of CPU seconds.

CPU_SECONDS_P FLOAT Price of CPU seconds.

CPU_SECONDS_A FLOAT Total amount for CPU seconds.

TAPE_EXCPS_V FLOAT Sum of tape exceptions.

TAPE_EXCPS_P FLOAT Price of tape exceptions.

TAPE_EXCPS_A FLOAT Total amount of tape exceptions.

DISK_EXCPS_V FLOAT Sum of disk exceptions.

DISK_EXCPS_P FLOAT Sum of disk exceptions.

DISK_EXCPS_A FLOAT Total amount of disk exceptions.

PRINT_LINES_V FLOAT Sum of print lines.

PRINT_LINES_P FLOAT Price of print lines.

PRINT_LINES_A FLOAT Total amount of print lines.

TAPE_MOUNTS_V FLOAT Sum of tape mounts.

TAPE_MOUNTS_P FLOAT Price of tape mounts.

TAPE_MOUNTS_A FLOAT Total amount of tape mounts.

PAGES_PRINTED_V FLOAT Sum of pages printed.

PAGES_PRINTED_P FLOAT Price of pages printed.

PAGES_PRINTED_A FLOAT Total amount of pages printed.

DASD_MBYTES_V FLOAT Sum of DASD megabytes.

DASD_MBYTES_P FLOAT Price of DASD megabytes.

DASD_MBYTES_A FLOAT Total amount of DASD megabytes.

SESSION_KBYTES_V FLOAT Sum of session kilobytes.

SESSION_KBYTES_P FLOAT Price of session kilobytes.

Chapter 6. Accounting feature lookup tables 55

BILLED_DATA lookup table

Figure 16 (Page 2 of 2). BILLED_DATA table


SESSION_KBYTES_A FLOAT Total amount of session kilobytes.

MISC_A FLOAT Total of dollar amount.


BILLING_PERIOD lookup table

BILLING_PERIOD

This table defines billing periods. It stores billing periods for all producing systems and is referencedduring the collect process.

Figure 17. BILLING_PERIOD table


BP_ID k CHAR(8) Billing Period Name

BP_EFF_DT k DATE Billing Period Start Date.

BP_END_DT k DATE Billing Period End Date.

BP_EOY_FLAG k CHAR(1) Billing Period End of the Accounting Year.


CPU_NORMAL_DATA lookup table

CPU_NORMAL_DATA

This table controls normalization of CPU seconds.

Figure 18. CPU_NORMAL_DATA table


CP_SMF_ID k CHAR(4) SMF ID the normalization factor applies to.

CP_START_DATE k DATE Start date for the SMF ID.

CP_POWER FLOAT Native CPU seconds are divided by this value to calculate thenormalized equivalent.

CP_END_DATE DATE End date for the SMF ID.

CP_DESC VARCHAR(30) Description of the SMF ID normalized.


CREDIT_DEBIT lookup table

CREDIT_DEBIT

This table is called CREDIT_DEBIT and is referenced by the RECALCULATE function when credits anddebits are processed for accounts. The table defines what credits and debits will be used, if any, for thisenvironment.

Debits and credits can be one time or recurring. One time debits and credits will be removed from thecredit/table lookup table after processing. A negative amount indicates a credit and a positive amountindicates a debit. Credits and debits may be entered in dollar or resource usage amounts.

Figure 19. CREDIT_DEBIT table


CUSTOMER_ID k CHAR(15) Customer name to receive credit or debit.

ACCOUNT_ID1 k CHAR(12) Account ID1 to be associated with credit or debit.





DATE k DATE Date for debit or credit.

PERIOD_NAME k CHAR(8) Shift associated with the credit or debit.

SUBSYSTEM_ID k CHAR(8) Subsystem associated with the credit or debit.

TYPE k CHAR(1) Type of charge. The character R indicates a one time chargeother values will be purged monthly.

DESCRIPTION CHAR(30) Description to be printed on the invoice.

AMOUNT FLOAT Dollar amount of credit or debit.

CPU_SECONDS FLOAT CPU seconds for credit or debit.

TAPE_EXCPS FLOAT Number of tapes exceptions for credit or debit.

DISK_EXCPS FLOAT Number of disks exceptions for credit or debit.

PRINT_LINES FLOAT Print lines for credit or debit.

TAPE_MOUNTS FLOAT Tape mounts for credit or debit.

PAGES_PRINTED FLOAT Pages printed for credit or debit.

DASD_MBYTES FLOAT DASD megabytes for credit or debit.

SESSION_KBYTES FLOAT DASD kilobytes for credit or debit.


CUSTOMER lookup table

CUSTOMER

This table provides customer information for invoice printing.

The Accounting component has a table that defines customers, which is called CUSTOMER and isreferenced during the collect process.

Figure 20. CUSTOMER table


CU_ID k CHAR(15) Customer ID. This must be unique.

CU_NAME CHAR(30) Customer name.

CU_EFF&US.DT DATE Effective start date of customer

CU_END_DT DATE End date after which no charges should accrue.

CU_LEDGER_AC_ID CHAR(30) Ledger Account Field.

CU_TYPE CHAR(1) The type of the customer. I for Internal E for External.

CU_CHARGEABLE_IND CHAR(1) Y or N if the customer is chargeable.

CU_CONTACT_NAME VARCHAR(30) Name of contact person.

CU_CONTACT_NUMBER CHAR(16) Phone number of contact person.

CU_ADDR1 VARCHAR(40) Line one of the address for the customer.

CU_ADDR2 VARCHAR(40) Line two of the address for the customer.

CU_ADDR3 VARCHAR(40) Line three of the address for the customer.


PRICE_LIST lookup table

PRICE_LIST

This table stores pricing for all producing systems.

Figure 21. PRICE_LIST table


CUS k CHAR(15) Customer ID.






SSID k CHAR(8) Subsystem ID.

PER k CHAR(8) Time Period.

EFF_DT k DATE Effective Date.

END_DT k DATE End Date.

CPU_SEC_P FLOAT Price of CPU seconds.

TAKE_E_P FLOAT Price of tape exception.

DISK_E_P FLOAT Price of disk exception.

PRINT_P FLOAT Price of print lines.

TAPE_M_P FLOAT Price of type mount.

PAGES_P FLOAT Price of page print.

DASD_M_P FLOAT Price of DASD megabytes.

SES_K_P FLOAT Price of session kilobytes.


Chapter 7. Accounting feature translation tables

RAFABATCH

This table contains the rules for translating account translation elements in SMF log records to accountIDs in the RAFBATCH table.


ACCT1 k CHAR(8) The value to be matched with the first eight characters,obtained from SMF30ACT of the first accounting section.

ACCT2 k CHAR(8) The value to be matched with the first eight characters,obtained from SMF30ACT of the second accounting section.

ACCT3 k CHAR(8) The value to be matched with the first eight characters,obtained from SMF30ACT of the third accounting section.

ACCT4 k CHAR(8) The value to be matched with the first eight characters,obtained from SMF30ACT of the fourth accounting section.

ACCT5 k CHAR(8) The value to be matched with the first eight characters,obtained from SMF30ACT of the fifth accounting section.

RACFGRP k CHAR(9) The value to be matched with the RACF group of the job,obtained from SMF30GRP.

USERID k CHAR(8) The value to be matched with the RACF user ID of the job,obtained from SMF30RUD.

JOBNAME k CHAR(8) The value to be matched with the job name of the job obtainedfrom SMF30JBN, SMF26JBN, or SMF25JBN.

SYSID k CHAR(8) The value to be compared with the system identificationobtained from SMF30SID.

PGMRNAME k CHAR(8) The value to be compared with the programmer name obtainedfrom SMF30USR.

JOBCLASS k CHAR(8) The value to be compared with the jobclass of the job obtainedfrom SMF30CLS.

USERFLD k CHAR(8) The value to be compared with J_USERFLD in RAFJOBLOG,whose default value is the first character of the job name. Theuser can modify this default calculation.

ACCTID CHAR(8) The account ID, obtained when the key columns match thecorresponding log fields.


RAFACICS translation table

RAFACICS

This table contains the rules for translating account translation elements in CICS log records to accountIDs in the RAFACICS table.


TERMID k CHAR(4) The value to be compared with the terminal ID, obtained fromthe field TERM.

USERID k CHAR(8) The value to be compared with the user ID, obtained from thefield USER.

OPERID k CHAR(3) The value to be compared with the operator ID, obtained fromthe field OPER.

APPLID k CHAR(8) The value to be compared with the generic application ID,obtained from the field SMFMNPRN.

SYSID k CHAR(8) The value to be compared with the system ID, obtained fromthe field SMFMNSID.

TRANTYPE k CHAR(8) The value to be compared with the transaction type, obtainedfrom field PGMNAME. If PGMNAME=DFHMIR or DFHMIRSthen the obtained value is 'FS', if PGMNAME=DFHCRP orDFHRTE then the obtained value is 'TERM', else the obtainedvalue is 'APPL'.

TRANSID k CHAR(4) The value to be compared with the transaction ID, obtainedfrom the field TRAN.

USERFLD k CHAR(8) The value to be compared with the value calculated forUSERFLD. The value is by default the first character of thefield USERID. This can be altered by the user.



RAFADASD translation table

RAFADASD

This table contains the rules for translating account translation elements in DCOLLECT log records toaccount IDs in the RAFADASD table.


DSNQUAL1 k CHAR(8) The value to be compared with the first qualifier of the data setin the field DCAASSOC.

DSNQUAL2 k CHAR(8) The value to be compared with the second qualifier of the dataset in the field DCAASSOC.

DSNQUAL3 k CHAR(8) The value to be compared with the third qualifier of the data setin the field DCAASSOC.

DSNQUALL k CHAR(8) The value to be compared with the last qualifier of the data setin the field DCAASSOC.

SYSID k CHAR(8) The value to be compared with the system identification in thefield DCUSYSID.


Chapter 7. Accounting feature translation tables 65

RAFADB2 translation table

RAFADB2

This table contains the rules for translating account translation elements in DB2 log records to account IDsin the RAFADB2 table.


CORRELAT k CHAR(12) The value to be compared with the correlation ID, obtainedfrom field QWHCCV.

CONNTYPE k CHAR(8) The value to be compared with the type of system that isconnected, obtained from QWHCCN.

AUTHORIZ k CHAR(8) The value to be compared with the authorization ID, obtainedfrom QWHCAID.

SUBSYSID k CHAR(8) The value to be compared with the subsystem ID, obtainedfrom QWHSSSID.

SYSID k CHAR(8) The value to be compared with the system ID, obtained fromSM101SID.



RAFAHSMBKUP translation table

RAFAHSMBKUP

This table contains the rules for translating account translation elements in the DCOLLECT log to accountIDs in the RAFHSMBKUP table.


DSNQUAL1 k CHAR(8) The value to be compared with the first qualifier of the data setin the field UBDSNAM.

DSNQUAL2 k CHAR(8) The value to be compared with the second qualifier of the dataset in the field UBDSNAM.

DSNQUAL3 k CHAR(8) The value to be compared with the third qualifier of the data setin the field UBDSNAM.

DSNQUALL k CHAR(8) The value to be compared with the last qualifier of the data setin the field UBDSNAM.

SYSID k CHAR(8) The value to be compared with the system ID in the fieldDCUSYSID.



RAFAHSMMIGR translation table

RAFAHSMMIGR

This table contains the rules for translating account translation elements in the DCOLLECT log to accountIDs in the RAFHSMMIGR table.


DSNQUAL1 k CHAR(8) The value to be compared with the first qualifier of the data setin the field UMDSNAM.

DSNQUAL2 k CHAR(8) The value to be compared with the second qualifier of the dataset in the field UMDSNAM.

DSNQUAL3 k CHAR(8) The value to be compared with the third qualifier of the data setin the field UMDSNAM.

DSNQUALL k CHAR(8) The value to be compared with the last qualifier of the data setin the field UMDSNAM.

SYSID k CHAR(8) The value to be compared with the system ID in the fieldDCUSYSID.



RAFAIMS translation table

RAFAIMS

This table contains the rules for translating account translation elements in IMS log records to account IDsin the RAFIMS table.


TERMID k CHAR(8) The values of logical terminal IDs which will be compared withthe value in the field DRL_OLTERM.

USERID k CHAR(8) The values of USERIDs which will be compared with the valuein the field DRL_OUSER.

SYSID k CHAR(8) The values of the system identifications which will be comparedwith the value in the collect parameter MVS_SYSTEM_ID.

TRANTYPE k CHAR(8) The values of transaction types which will be compared withthe value in the field DRL_TRANT.

TRANSID k CHAR(8) The value of transaction ID which will be compared with thevalue depending on the first character of the fieldsDRL_TRANT and DRL_SMBNM.



RAFANETSESM translation table

RAFANETSESM

This table contains the rules for translating account translation elements in SMF log records to accountIDs in the RAFNETSES20 table.


ANUM k CHAR(8) This is to be matched with the account number of the sessionobtained from LSCDANUM.

USERID k CHAR(8) This is to be matched with the operator ID of the sessionobtained from LSCDUSER.

GROUPID k CHAR(8) This is to be matched with the group ID of the session obtainedfrom LSCDGRUP.



RAFANETV translation table

RAFANETV

This table contains the rules for translating account translation elements in SMF log records to accountIDs in the RAFNETV table.


SLUGROUP k CHAR(8) The value to be compared with the first four characters ofSLUNAME plus blanks, obtained from LSESSNAM.

SLUNAME k CHAR(8) The value to be compared with the Secondary Logical Unit(SLU) name, obtained from LSESSNAM.

PLUGROUP k CHAR(8) The value to be compared with the first four characters ofPLUNAME plus blanks, obtained from LSESPNAM.

PLUNAME k CHAR(8) The value to be compared with the Primary Logical Unit (PLU)name, obtained from LSESPNAM.

SUBSYSID k CHAR(8) The value to be compared with the subsystem ID, obtainedfrom LOGRSUBS.

SYSID k CHAR(8) The value to be compared with the system ID.



RAFASTC translation table

RAFASTC

This table contains the rules for translating account translation elements in SMF log records to accountIDs in the RAFSTC table.


ACCT1 k CHAR(8) This is to be matched with the first eight characters ofSMF30ACT, obtained from the first accounting section.

ACCT2 k CHAR(8) This is to be matched with the first eight characters ofSMF30ACT, obtained from the second accounting section.

ACCT3 k CHAR(8) This is to be matched with the first eight characters ofSMF30ACT, obtained from the third accounting section.

ACCT4 k CHAR(8) This is to be matched with the first eight characters ofSMF30ACT, obtained from the fourth accounting section.

ACCT5 k CHAR(8) This is to be matched with the first eight characters ofSMF30ACT, obtained from the fifth accounting section.

RACFGRP k CHAR(9) This is to be matched with the RACF group of the JOBobtained from SMF30GRP.

USERID k CHAR(8) This is to be matched with the RACF user ID of the jobobtained from SMF30RUD.

JOBNAME k CHAR(8) This is to be matched with the JOBNAME of the job obtainedfrom SMF30JBN, SMF26JBN, or SMF25JBN.

SYSID k CHAR(8) This is to be compared with the system ID, obtained fromSMF30SID.

PGMNAME k CHAR(8) This is to be compared with the program name, obtained fromSMF30PGM.

USERFLD k CHAR(8) This is to be compared with A_USERFLD in RAFADDRLOG,whose default value is the first character of the job name. Theuser can modify this default calculation.



RAFATSO translation table

RAFATSO

This table contains the rules for translating account translation elements in SMF log records to accountIDs in the RAFTSO table.


ACCT1 k CHAR(8) This is to be matched with the first eight characters, obtainedfrom SMF30ACT of the first accounting section.

ACCT2 k CHAR(8) This is to be matched with the first eight characters, obtainedfrom SMF30ACT of the second accounting section.

ACCT3 k CHAR(8) This is to be matched with the first eight characters, obtainedfrom SMF30ACT of the third accounting section.

ACCT4 k CHAR(8) This is to be matched with the first eight characters, obtainedfrom SMF30ACT of the fourth accounting section.

ACCT5 k CHAR(8) This is to be matched with the first eight characters, obtainedfrom SMF30ACT of the fifth accounting section.

RACFGRP k CHAR(9) This is to be matched with the RACF group of the job, obtainedfrom SMF30GRP.

USERID k CHAR(8) This is to be matched with the RACF user ID of the job,obtained from SMF30RUD.

TERMID k CHAR(8) This is to be compared with the terminal ID, obtained fromSMF30TID.

SYSID k CHAR(8) This is to be compared with the system ID, obtained fromSMF30SID.

USERFLD k CHAR(8) This is to be compared with S_USERFLD in RAFSESLOG,whose default value is the first character of the RACF user ID.The user can modify this default calculation.



Chapter 8. Accounting feature reports

This chapter describes the reports that are provided with the Performance Reporter Accounting feature.

Accounting feature report definitions

This section describes the report definitions:

Prorated account percentage validation report

The following information identifies the report:

Report ID RAFA001

Report Group Resource Accounting Reports

Source ACCT_PRORATE

Attributes ACCOUNT, PRORATION, PERCENTAGE, VALIDATION

Figure 22 shows an example of this report:

Prorated Account Percentages Validation

FIX ANY ACCOUNT WITH PERCENTAGE OTHER THAN %1ðð

ACCOUNT ACCOUNT ACCOUNT ACCOUNT ACCOUNT CUSTOMER

ID1 ID2 ID3 ID4 ID5 ID PERCENTAGE

------------ ------------ ------------ ------------ ------------ ----------- ----------

ACCNð1 MARELLA-1 9.7ððE+ð1

Figure 22. Prorated account percentage validation

The report contains the following information:

ACCOUNT_ID1 Account name 1.





CUSTOMER_ID Customer name.

PERCENTAGE Percent used.


Charges by billing period report

Charges by billing period report


Report ID RAFA004


Source BILLED_DATA_CREDIT_DEBIT

Attributes BILLING, SUMMARY


CHARGES BY CHARGE TYPE

BP CPU TAPE DISK PRINT TAPE PAGES DASD SESSION

ID SECONDS EXCPS EXCPS LINES MOUNTS PRINTED MBYTES KBYTES MISC

-------- ---------- --------- --------- ---------- ---------- ---------- ---------- ---------- ----------

NULLBP ð.ðððE+ðð - - - - - - - ð.ðððE+ðð

PUTV 4.943E+ð1 - - - - - - - ð.ðððE+ðð

Figure 23. Charges by charge type


BP_ID Billing period.

CPU_SECONDS Number of CPU seconds used.

TAPE_EXCPS Number of tape exceptions.

DISK_EXCPS Number of disk exceptions.

PRINT_LINES Number of lines printed.

TAPE_MOUNTS Number of tape mounts.

PAGES_PRINTED Number of pages printed.

DASD_MBYTES Number of DASD Mbytes.

SESSION_KBYTES Number of session Kbytes.

MISC Miscellaneous.


Billing details report

Billing details report


Report ID RAFA002


Source BILLED_DATA

Attributes BILLING, DETAILS, BILLED_DATA


BILLING DETAILS REPORT

BILLING CHARGE PERIOD

PERIOD CUSTOMER TYPE ACCOUNT AC2 AC3 AC4 AC5 NAME DESCRIPTION QUANTITY PRICE AMOUNT

-------- --------------- ------ ---------- ----- ----- ----- ----- ------- ------------ --------- ---------- ---------

PUTV MARELLA-1 N ACCNð1 NIGHT CPU SECONDS 3.316E+ð1 1.ðððE+ðð 8.289E+ðð


PUTV MARELLA-3 N ACCNð3 NIGHT CPU SECONDS 3.3ð5E+ð1 1.ðððE+ðð 8.262E+ðð


PUTV MARELLA-5 N ACCNð5 NIGHT CPU SECONDS 3.3ð1E+ð1 1.ðððE+ðð 8.253E+ðð


Figure 24. Billing details, partial view


BILLING_PERIOD Billing period.

CUSTOMER Customer name.

CHARGE_TYPE

ACCOUNT

AC2

AC3

AC4

AC5

PERIOD_NAME

DESCRIPTION

QUANTITY

PRICE

AMOUNT

Chapter 8. Accounting feature reports 77

Charges for selected billing period report

Charges for selected billing period report


Report ID RAFA003


Source BILLED_DATA

Attributes BILLING, SUMMARY

Variables BP_ID


CHARGES BY CHARGE TYPE

BP CPU TAPE DISK PRINT TAPE PAGES DASD SESSION

ID SECONDS EXCPS EXCPS LINES MOUNTS PRINTED MBYTES KBYTES MISC

-------- ---------- --------- --------- ---------- ---------- ---------- ---------- ---------- ----------

PUTV 4.943E+ð1 - - - - - - - ð.ðððE+ðð

Figure 25. Charges by charge type


BP_ID Billing period.

CPU_SECONDS Number of CPU seconds used.

TAPE_EXCPS Number of tape exceptions.

DISK_EXCPS Number of disk exceptions.

PRINT_LINES Number of lines printed.

TAPE_MOUNTS Number of tape mounts.

PAGES_PRINTED Number of pages printed.

DASD_MBYTES Number of DASD Mbytes.

SESSION_KBYTES Number of session Kbytes.

MISC Miscellaneous.


Chapter 9. Considerations for dpAM users

This chapter compares the functions of the Performance Reporter for OS/390 Accounting feature withthose of dp Accounting Manager (dpAM).

The Performance Reporter for OS/390 Accounting feature provides basic accounting and chargebackfeatures. If you are moving from dpAM to Accounting feature, refer to the following table about thefunctional equivalents of the two products. In the case of functionality that is in dpAM but not in the basesupport in Accounting feature, suggestions are provided to help you achieve similar functionality.

Figure 26. dpAM and Accounting feature comparison

Function dpAM Performance Reporter for OS/390 Accountingfeature

User Interface yes yes (Performance Reporter user interface.)

Overhead accounts yes yes (Fixed and variable proration.)

Batch accounting yes yes

CICS accounting yes yes

IMS accounting yes yes

DB2 accounting yes yes

DASD accounting yes yes

Network accounting yes yes

Credit/Debits yes yes (Enhanced to allow dollar value in addition toquantity.)

Flexible pricing yes yes

Price list versions yes no (Price list is a lookup table. Prior versions can becopied to a file for historical reference.)

Cost lists yes no (Product can be customized to include a cost-listtable. Additional customization could enable thiscost-list table to be used in creating updates to theprice list lookup table.)

Forecasting yes no (Data could be exported to spreadsheet or otherthird-party product that provides forecastingcapabilities.)

Budgeting yes no (Accounting feature can be customized to includebudget tables and queries.)


List of abbreviations

These abbreviations appear in this book:

BMU base measurement unit

CD-ROM compact disk—read-only memory

CICS Customer Information and ControlSystem

CMF CICS monitoring facility

CPU central processing unit

DB2 DATABASE 2

DL/I Data Language/I

DMU derived measurement unit

DP data processing

Hiperspace high-performance dataspace

IMS Information Management System

I/O input/output

IS information system

ISPF Interactive System Productivity Facility

NPM NetView Performance Monitor

P.R. Acronym for Performance Reporter forOS/390 (only for specific cases).

RMF Resource Management Facility

SMF system management facilities

SMP/E System Modification Program/Extended

SQL Structured Query Language

SRB service control block

TCB task control block

TCP/IP Transmission Control Protocol/InternetProtocol

TSO time-sharing option


Glossary

Aaccount . Based on the information in usage logs, allusage is allocated to an account. For example, you canuse fields such as user ID and terminal ID to determinethe account. Each account belongs to a customer, whowill be charged for its system usage.

ad hoc billing . Ordinarily, billing is performed after theend of a billing period. If you need to bill certaincustomers for some charges before the end of thebilling period, you can produce an ad hoc bill.

administration . A Performance Reporter task thatincludes maintaining the database, updatingenvironment information, and ensuring the accuracy ofdata collected.

administration dialog . The set of host windows usedto administer Performance Reporter.

agent . In UNIX Performance feature, a set ofprograms running on a network node that gather dataabout the node and write the data to log files. Agentscan gather data by issuing UNIX commands, and byreading files such as UNIX accounting files.

Bbilling period . Accounting Feature can generate billingperiods every week, every two weeks, twice per month,once per month, or once per quarter. You can alsospecify the start date and end date of each billingperiod manually.

billing unit . Customers are charged according to thenumber of billing units that they consume. A billing unitcan consist of only a measurement unit (such as CPUseconds) or a measurement unit and one or moreservice types (such as CPU seconds, during first shift,with jobclass A).

BMU. Base measurement unit.

Ccollect . A process used by Performance Reporter toread data from input log data sets, interpret records inthe data set, and store the data in DB2 tables in thePerformance Reporter database.

component . An optionally installable part of anPerformance Reporter feature.

control table . A predefined Performance Reportertable that controls results returned by some log collectorfunctions.

credit . If you discover an error in a previous bill, youcan specify a positive or negative credit. The credit canbe either a number of billing units or an amount ofmoney.

customer . A customer is a person or organization thatuses the services provided by your DP center. Eachcustomer has one or more accounts.

DData Language/I (DL/I) . An IBMdatabase-management facility.

data table . A Performance Reporter table thatcontains performance data used to create reports.

DMU. Derived measurement unit.

discounts . You can give customers discounts basedon their level of system usage. You can define one setof discounts for all customers, or different discounts fordifferent customers.

distributed transaction processing . The distributionof processing among transactions that communicatesynchronously with each other over intersystem orinterregion links.

Eenvironment information . All of the information that isadded to the log data to create reports. Thisinformation can include data such as performancegroups, shift periods, installation definitions, and so on.

Ffinal billing . At the end of a billing period, you canproduce a preliminary bill, check the preliminary bill, andthen produce a final bill. You then export the billinginformation to your invoicing system.

functional billing . In functional billing, customers arecharged in terms of billing units that are meaningful tothem, such as CICS transactions, rather than in termsof the basic resources of the computing system.(Contrast with Resource billing.)


Ggather . A process performed by agents in whichperformance data is entered into log files. The log filesare located on the same nodes as the agents.

Hhelp topics . An online table of contents for thePerformance Reporter online help information.

Kkey columns . The columns of a DB2 table thattogether constitute the key.

key value . Value used to sort records into groups.

Llog . Any sequential data set used as input toPerformance Reporter.

log collector . A Performance Reporter program thatprocesses log data sets and provides other services.

log collector language . Performance Reporterstatements used to supply definitions to and invokeservices of the log collector.

log data set . Any sequential data set used as input toPerformance Reporter.

log definition . The description of a log data setprocessed by the log collector.

log procedure . A program module that is used toprocess all record types in certain log data sets.

logical unit (LU) . A port through which a user gainsaccess to the services of a network.

lookup expression . An expression that specifies howa value is obtained from a lookup table.

lookup table . A Performance Reporter DB2 table thatcontains grouping, translation, or substitutioninformation.

Mmeasurement units . You can measure system usageat a basic resource level (such as CPU seconds) or at afunctional level (such as CICS transactions).Measurement units serve as the basis for billing units.

Oobject . An integral part of a feature componentneeded for data collection (for example, recorddefinitions, record procedures, and update definitions).

occasional charges . You can specify charges foroccasional services such as consultancy, education, orprogramming effort. These charges can be recordedeither as a volume of billing units or as an amount ofmoney.

PPerformance Reporter database . A set of DB2 tablesthat includes data tables, lookup tables, system tables,and control tables.

preliminary billing . Before you produce your final bill,you can produce a preliminary bill. You can check thepreliminary bill and make any necessary changesbefore producing the final bill.

You can also produce preliminary bills before the end ofa billing period, if you want up-to-date usageinformation.

producing system . Any product or service whoseusage is recorded is called a producing system inAccounting Feature. The most common producingsystems, such as TSO and CICS, are predefined in theAccounting feature.

purge condition . Instruction for purging unneededdata from the Performance Reporter database.

Rrecord definition . The description of a record typecontained in the log data sets used by PerformanceReporter, including detailed record layout and dataformats.

record procedure . A program module that is called toprocess some types of log records.

record type . The classification of records in a log dataset.

recurrent charges . You can charge customers foritems that occur regularly but do not appear in anyusage log. For example, you might define a recurrentcharge for terminal rental.

region . A section of the dynamic area that is allocatedto a job step or system task.

report definition language . Performance Reporterstatements used to define reports and report groups.


report group . A collection of Performance Reporterreports that can be referred to by a single name.

reporting dialog . A set of host or workstation windowsused to request reports.

reports . Various QMF procedures are supplied withAccounting Feature for producing reports. You canmodify these reports or define your own reports usingQMF or equivalent product.

resource . Any facility of the computing system oroperating system required by a job or task, includingcentral storage, input/output devices, the processingunit, data sets, and control or processing programs.

resource billing . In resource billing, customers arecharged in terms of billing units that relate directly to thebasic resources of the computing system, such as CPUseconds. (Contrast with Functional billing.)

resource group . A collection of resources identified asbelonging to a particular department or division.Resources are organized into groups to reflect thestructure of an organization.

resource information . Environment information thatdescribes the elements in a system (for example, anetwork).

Ssection . A structure within a record that contains oneor more fields and may contain other sections.

service billing . A method of charging that reflects thedifferent costs of running a DP center under differentconditions.

source . In an update definition, the record or DB2table that contains the data used to update anPerformance Reporter DB2 table.

subcomponent . An optionally installable part of anPerformance Reporter feature component.

system table . A DB2 table that stores information forcontrolling log collector processing, PerformanceReporter dialogs, and reporting.

Ttarget . In an update definition, the DB2 table in whichPerformance Reporter stores data from the sourcerecord or table.

threshold . The maximum or minimum acceptable levelof usage. Usage measurements are compared withthreshold levels.

Transmission Control Protocol/Internet Protocol(TCP/IP). A non-proprietary communications protocolfor linking workstations to host computers and to otherhardware.

Uupdate definition . Instructions for entering data intoDB2 tables from records of different types or from otherDB2 tables.

updates . Instructions in Performance Reporter on howto process data from log data sets to DB2 tables.

usage data . Producing systems generate logs thatcontain usage information. The Accounting featurecollects this usage data.

Vview . An alternative representation of data from one ormore tables. A view can include all or some of thecolumns contained in the table on which it is defined.

Wworkload periods . You can define workload periods,in order to charge different prices for system usage atdifferent times. For example, by charging more forsystem work during the day on workdays, youencourage customers to run low-priority work at night,or on weekdays or holidays.

Glossary 85

Index

Aabbreviations used in this book, list of 81ACCOUNT lookup table 53account proration table

how to use with Performance Reporter 54Accounting feature

collecting usage data 3comparison with dpAM functions 79customizing for the Accounting feature 7data flow 17implementing 13installing 10output 4overview 3preparing 7preparing for collect 12producing billing information 3reports 75setting up security 8tables 27trimming data tables 9working with, an example 4

ACCT_PRORATE lookup table 54audience for this book, intended xiii

BBATCH producing system

RAFABATCH translation table 63RAFBATCH data table 27RAFJOBLOG data table 29

BILLED_DATA lookup table 55billing period table

how to use with Performance Reporter 57billing units 6BILLING_PERIOD lookup table 57

CCICS producing system

RAFACICS translation table 64RAFCICS data table 31

collecting usage data 3CPU normalization

with trimmed collector tables 9CPU_NORMAL_DATA lookup table 58CREDIT_DEBIT lookup table 59credit/debit table

how to use with Performance Reporter 59CUSTOMER lookup table 60customer table

how to use with Performance Reporter 60

customers and accounts 5

DDASD producing system

RAFADASD translation table 65RAFDASD data table 33

DASD subsystemDCOLLECT LAST_RUN lookup table 11

data flowbilling process 25CICS 19credit debit processing 26DB2 21DFSMS 18general flow 17IMS 23NPM and NetView 22overhead account 24STC, BATCH, TSO 20

data table in Performance Reporterintroduction 7

data table in resource accountingtrimming 9

data tablesRAFADDRLOG 44RAFBATCH 27RAFCICS 31RAFDASD 33RAFDB2 34RAFHSMBKUP 36RAFHSMMIGR 37RAFIMS. 38RAFJOBLOG 29RAFNETSES20 39RAFNETSES4x 41RAFNETV 42RAFSESLOG 47RAFSTC 43RAFTSO 46USE_SUMMARY_D 48USE_SUMMARY_D2 49USE_SUMMARY_D3 50USE_SUMMARY_D4 51

DB2 producing systemRAFADB2 translation table 66RAFDB2 data table 34

DFSMS_LAST_RUN lookup table 11dpAM, comparison with Accounting feature

functions 79DRLJCOLL batch job 12


Gglossary 83

Hhow to use this book xivHSMBKUP producing system

RAFAHSMBKUP translation table 67RAFHSMBKUP data table 36

HSMBKUP subsystemDCOLLECT LAST_RUN lookup table 11

HSMMIGR producing systemRAFHSMMIGR translation table 68RAFHSSSIGR data table 37

HSMMIGR subsystemDCOLLECT LAST_RUN lookup table 11

Iimplementing the Accounting feature 13IMS producing system

RAFIMS data table 38RAFIMS translation table 69

installing the Accounting feature 10intended audience for this book xiii

Llibrary, Performance Reporter xvlist of abbreviations used in this book 81list of terms used in this book 83log in Performance Reporter

introduction 7lookup table in Performance Reporter

introduction 7maintaining 10

lookup tablesACCOUNT 53ACCT_PRORATE 54BILLED_DATA 55BILLING_PERIOD 57CPU_NORMAL_DATA 58CREDIT_DEBIT 59CUSTOMER 60PRICE_LIST 61

Mmaintaining lookup tables 10

NNETSESM producing system

RAFANETSESM translation table 70RAFNETSES20 data table 39RAFNETSES4X data table 41

NETV producing systemRAFNETV data table 42

NETV subsystemPerformance Reporter resource translation table 11

NLDM producing systemRAFANETV translation table 71

NPM subsystemPerformance Reporter resource translation table 11

NW_RESOURCE lookup table 11

Ooutput from the Accounting feature 4overview of the Accounting feature 3

PPerformance Reporter

distribution of objects 7preparing for collect 12setting up security 8user groups 8

Preparing for collect 12Preparing the Accounting feature 7PRICE_LIST lookup table 61pricing 4producing billing information 3product library, Performance Reporter xv

RRAFADDRLOG data table 44RAFJOBLOG data table 29RAFMSESLOG data table 47record definition in Performance Reporter

introduction 7report formatreports

billing period details 77charges by billing period 76charges for selected billing period 78prorated account percentage validation 75

resource accountingtrimming the data tables 9

Ssecurity 8setting prices 4special day table

how to use with Performance Reporter 10STC producing system

RAFADDRLOG data table 44RAFASTC translation table 72RAFSTC data table 43


Ttables

dataRAFADDRLOG 44RAFBATCH 27RAFCICS 31RAFDASD 33RAFDB2 34RAFHSMBKUP 36RAFHSMMIGR 37RAFIMS. 38RAFJOBLOG 29RAFNETSES20 39RAFNETSES4x 41RAFNETV 42RAFSESLOG 47RAFSTC 43RAFTSO 46USE_SUMMARY_D 48USE_SUMMARY_D2 49USE_SUMMARY_D3 50USE_SUMMARY_D4 51

lookupACCOUNT 53ACCT_PRORATE 54BILLED_DATA 55BILLING_PERIOD 57CPU_NORMAL_DATA 58CREDIT_DEBIT 59CUSTOMER 60PRICE_LIST 61

translationRAFABATCH 63RAFACICS 64RAFADASD 65RAFADB2 66RAFAHSMBKUP 67RAFAHSMMIGR 68RAFAIMS. 69RAFANETSESM 70RAFANETV 71RAFASTC 72RAFATSO 73

tables, described 10, 14terms used in this book 83translation tables

RAFABATCH 63RAFACICS 64RAFADASD 65RAFADB2 66RAFAHSMBKUP 67RAFAHSMMIGR 68RAFAIMS. 69RAFANETSESM 70RAFANETV 71

translation tables (continued)RAFASTC 72RAFATSO 73

trimming data tables 9TSO producing system

RAFATSO translation table 73RAFSESLOG data table 47RAFTSO data table 46

Uupdate definition in Performance Reporter

introduction 7use of this book, intended xivuser groups

in Performance Reporter 8

Vviews, described 14

Wwho should use this book xiiiworking with the Accounting feature, an example 4workload period table

how to use with Performance Reporter 10

Index 89

Communicating Your Comments to IBM

TME 10Performance Reporter for OS/390Accounting Feature:Guide and ReferenceRelease 3

Publication No. SH19-4495-00

If you especially like or dislike anything about this book, please use one of the methods listed below to send yourcomments to IBM. Whichever method you choose, make sure you send your name, address, and telephone numberif you would like a reply.

Feel free to comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of thisbook. However, the comments you send should pertain to only the information in this manual and the way in whichthe information is presented. To request additional publications, or to ask questions or make comments about thefunctions of IBM products or systems, you should talk to your IBM representative or to your IBM authorizedremarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any wayit believes appropriate without incurring any obligation to you.

If you prefer to send comments by mail, use the reader's comment form (RCF) at the back of this book. If you wish,you can give the RCF to the local branch office or IBM representative for postage-paid mailing.

If you prefer to send comments by FAX, use this number, which is in Italy:

(39.6) 5966.2077

If you prefer to send comments electronically, use this network ID:

ROMERCF at VNET.IBM.COM

Make sure to include the following in your note:

� Title and publication number of this book� Page number or topic to which your comment applies

Help us help you!

TME 10Performance Reporter for OS/390Accounting Feature:Guide and ReferenceRelease 3

Publication No. SH19-4495-00

We hope you find this publication useful, readable and technically accurate, but only you can tell us! Yourcomments and suggestions will help us improve our technical publications. Please take a few minutes tolet us know what you think by completing this form.

Specific Comments or Problems:

Please tell us how we can improve this book:

Thank you for your response. When you send information to IBM, you grant IBM the right to use ordistribute the information without incurring any obligation to you. You of course retain the right to use theinformation in any way you choose.

Name Address

Company or Organization

Phone No.

Overall, how satisfied are you with the information in this book? Satisfied Dissatisfied

Ø Ø

How satisfied are you that the information in this book is: Satisfied Dissatisfied

Accurate Ø ØComplete Ø ØEasy to find Ø ØEasy to understand Ø ØWell organized Ø ØApplicable to your task Ø Ø

Cut or FoldAlong Line

Cut or FoldAlong Line

Help us help you !SH19-4495-00 IBM

Fold and Tape Please do not staple Fold and Tape

PLACEPOSTAGESTAMPHERE

Information DevelopmentRome Tivoli LaboratoryIBM Italy S.p.A.Via Sciangai, 5300144 RomeItaly

Fold and Tape Please do not staple Fold and Tape

SH19-4495-00

IBM

File Number: S370/30xx/4300-34Program Number: 5695-101

Printed in Denmark by IBM Danmark A/S

SH19-4495-ðð

performance reporter for os/390 accounting...

Documents