SLR To Tivoli Performance Reporter For OS-390 Migration Cookbook Sg245128

SLR to Tivoli Performance Reporter for OS/390 Migration Cookbook
Mike Foster, Mauro Basile, Malcolm Pearse
International Technical Support Organization http://www.redbooks.ibm.com
SG24-5128-00
SG24-5128-00
International Technical Support Organization SLR to Tivoli Performance Reporter for OS/390 Migration Cookbook February 1999
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, Special Notices on page 193.
First Edition (February 1999)
This edition applies to Version 1, Release Number 4 of Tivoli Performance Reporter for OS/390, Program Number 5695-101 for use with OS/390, MVS/ESA or MVS/SP as it relates to migration of information from Version 3, Release 3 of the IBM Service Level Reporter, Program Number 5665-397.
Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. OSJB Building 045 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Copyright International Business Machines Corporation 1999. All rights reserved Note to U.S Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Part 1. Migration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Why Upgrade to Performance Reporter? . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 Overview of Performance Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Introducing the Log Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3.1 Log Collector Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4 Comparison between PR and SLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.1 Summarize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.2 Join/Merge Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.4.3 Directly Modify Log Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.4.4 Purging Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.4.5 Table Lookup During Collect. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.4.6 Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.4.7 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.4.8 PR Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.4.9 SLR Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.5 How to Use This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Chapter 2. Migration Approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.1 Introduction to Performance Reporter Migration . . . . . . . . . . . . . . . . . 17 2.2 The Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.3 Developing a Migration Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.3.1 Analysis of What to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.3.2 Elements of a Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.3.3 Assessment of the Importance of Data . . . . . . . . . . . . . . . . . . . . 22 2.3.4 Assessment of Possible Migration Approaches. . . . . . . . . . . . . . 23 2.3.5 Other Plan Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Part 2. Migration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Chapter 3. Migrating Data from Predefined SLR Tables. . . . . . . . . . . . 31 3.1 Example of Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Copyright IBM Corp. 1999
iii
3.2 Deviation from Default Data Migration . . . . . . . . . . . . . . . . . . . . . . . . 45 3.3 Other Modifications to the Standard Migration . . . . . . . . . . . . . . . . . . 52 3.3.1 Addition or Modification of Computed Columns. . . . . . . . . . . . . . 53 3.3.2 Addition or Modification of Data Columns . . . . . . . . . . . . . . . . . . 53 3.3.3 Migrating User-Defined Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Chapter 4. Migrating User-Defined A.L.L Based Tables and Data . . 4.1 The A.L.L. Table Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Component Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Populating Your New Tables with Migrated Data . . . . . . . . . . . . . . Chapter 5. Migrating Parameter Table Data . . . . . . . . . . . . . . 5.1 Reenter Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 DB2 Load Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 IXF Unload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Populate the Lookup Table Defined by the New Component Chapter 6. Migrating SLR Reports . . . . . . . 6.1 SLR Report Description . . . . . . . . . . . . . . 6.2 Setting Migration Parameters for Reports . 6.3 Example of Report Migration . . . . . . . . . . .. .. .. .. .. .. .. .. .. . . . . . .. .. .. .. .. . . . . . . . . . . 57 . 57 . 67 . 81 . 85 . 86 . 87 . 93 . 96
. . . . . . . . . . . . . . . . . . . 99 . . . . . . . . . . . . . . . . . . 100 . . . . . . . . . . . . . . . . . . 103 . . . . . . . . . . . . . . . . . . 106
Chapter 7. Miscellaneous Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 7.1 Setting Purge Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 7.2 Executing Purge Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.2.1 Online Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.2.2 Batch Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 7.3 Parallel Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Appendix A. The Key to Predefined Migration - DLRMIGRATION . . . 137 A.1 Viewing DLRMIGRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 A.2 DRLMIGRATION Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 A.2.1 MVS_SYSTEM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 A.2.2 MVS_ADDRSPACE_M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 A.2.3 MVS_ADDRDISTR_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 A.2.4 MVS_PROGRAM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 A.2.5 MVS_COMPCODE_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 A.2.6 MVS_WORKLOAD_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 A.2.7 MVS_PRINTER_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 A.2.8 MVS_TAPE_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 A.2.9 MVS_IPL_T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 A.2.10 AVAILABILITY_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 A.2.11 DFSMS_DATASET_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 A.2.12 DFSMS_VOLUME_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
iv
SLR to Tivoli Performance Reporter for OS/390
A.2.13 A.2.14 A.2.15 A.2.16 A.2.17 A.2.18 A.2.19 A.2.20 A.2.21 A.2.22 A.2.23 A.2.24 A.2.25 A.2.26 A.2.27 A.2.28 A.2.29 A.2.30 A.2.31 A.2.32 A.2.33 A.2.34 A.2.35 A.2.36 A.2.37 A.2.38 A.2.39 A.2.40 A.2.41 A.2.42 A.2.43 A.2.44 A.2.45 A.2.46 A.2.47 A.2.48 A.2.49 A.2.50 A.2.51 A.2.52 A.2.53 A.2.54 A.2.55
DFSMS_BACKUP_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 DFSMS_MIGRATION_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 DFSMS_DASD_CAP_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 DFSMS_TAPE_CAP_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 DFSMS_ACTIVITY_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 DFSMS_LAST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 DFSMS_MIGRATE_DAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 DFSMS_DS_OWNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 DB2_TRANSACTION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 DB2_USER_TRAN_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 DB2_APPL_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 DB2_USER_AP_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 DB2_TRAN_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 DB2_USER_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 DB2_APPLICATION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 DB2_USER_APPL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 EREP_DASD_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 EREP_VTAM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 EREP_CPU_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 EREP_DASD_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 VMACCT_SESSION_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 VMPRF_SYSTEM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 VMPRF_PROCESSOR_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 VMPRF_USER_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 VMPRF_DASD_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 CICS_TRANSACTION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 CICS_M_GLOBAL_D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 MSG_SYSLOG_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 MSG_SYSLOG_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 AVAILABILITY_W/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 NW_NPM_UTIL_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 NW_ALERT_BASIC_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 NW_ALERT_GENERIC_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 NW_SESSION_FAIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 NW_RTM_RESONSE_W/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 NW_SM_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 NW_NCP_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 NW_PU_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 NW_LINE_UTIL_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 NW_NPM_TRANSIT_W/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 NW_X25LN_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 NW_X25PU_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 NW_X25NI_UTIL_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
A.2.56 A.2.57 A.2.58 A.2.59 A.2.60 A.2.61 A.2.62 A.2.63 A.2.64
NW_NTRIP_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 NW_NTRIL_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 NW_NEO_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 IMS_TRANSACTION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 OPC_AUTO_EVENT_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 OPC_MCP_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 OPC_MISSED_FB_M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 OPC_OPER_EVENT_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 OPC_OPER_EVENT_T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Appendix B. Predefined SLR Tables to PR Tables Cross Reference . 181 B.1 SLR to PR Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 B.2 PR to SLR Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Appendix C. Parameter Table to Lookup Table Cross Reference . . . 189 Appendix D. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Appendix E. Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 E.1 International Technical Support Organization Publications . . . . . . . . . . 197 E.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 E.3 Other Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 How to Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 How IBM Employees Can Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . 199 How Customers Can Get ITSO Redbooks. . . . . . . . . . . . . . . . . . . . . . . . . . . 200 IBM Redbook Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 List of Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
vi
Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. Performance Reporter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Overview of Performance Reporter Data Collection Flow . . . . . . . . . . . . . 11 Overview of Service Level Reporter Data Collection Flow . . . . . . . . . . . . 13 Administrator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Migration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 SLR Parameter for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Cross Reference of Predefined SLR vs PR Tables . . . . . . . . . . . . . . . . . . 33 SLR Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Migration Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Migration Table List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Migration Sample Job (Part 1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Migration Sample Job (Part 2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Migration Sample Job (Part 3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 DRLW07A0 Member in hlq.SDRLDEFS (Part 1 of 2) . . . . . . . . . . . . . . . . 41 DRLW07A0 Member in hlq.SDRLDEFS (Part 2 of 2) . . . . . . . . . . . . . . . . 42 DRLWMVWO Member of hlq.SDRLDEFS (Part 1 of 2) . . . . . . . . . . . . . . 43 DRLWMVWO Member of hlq.SDRLDEFS (Part 2 of 2) . . . . . . . . . . . . . . 44 Modified Migration Sample Job (Part 1 of 3) . . . . . . . . . . . . . . . . . . . . . . . 46 Modified Migration Sample Job (Part 2 of 3) . . . . . . . . . . . . . . . . . . . . . . . 47 Modified Migration Sample Job (Part 3 of 3) . . . . . . . . . . . . . . . . . . . . . . . 48 Modified DRLW07A0 Member in hlq.LOCAL.DEFS (Part 1 of 2) . . . . . . . 49 Modified DRLW07A0 Member in hlq.LOCAL.DEFS (Part 2 of 2) . . . . . . . 50 Modified DRLWMVWO Member in hlq.LOCAL.DEFS (Part 1 of 2) . . . . . . 51 Modified DRLWMVWO Member in hlq.LOCAL.DEFS (Part 2 of 2) . . . . . . 52 Providing COMPCOL Function within a PR Report . . . . . . . . . . . . . . . . . . 53 Extract from Modified DRLW0500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Extract from Modified DRLWC101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 The System Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 The Migration Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Migration Parameters for Table Migration . . . . . . . . . . . . . . . . . . . . . . . . . 60 SLR V3 Table Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 A.L.L. Migration Sample Job (Part 1 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . 61 A.L.L. Migration Sample Job (Part 2 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . 62 A.L.L. Migration Sample Job (Part 3 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . 63 A.L.L. Migration Sample Job (Part 4 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . 64 A.L.L. Migration Sample Job (Part 5 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . 65 A.L.L. Migration Sample Job (Part 6 of 6) . . . . . . . . . . . . . . . . . . . . . . . . . 66 Drop Log, Record, and Update Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 PR Statements for Log Definition - DRLLS001 . . . . . . . . . . . . . . . . . . . . . 68 PR Statements for Record Definition - DRLRS001 . . . . . . . . . . . . . . . . . . 68
vii
41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83.
PR Statements for Tablespace Definition - DRLSS001. . . . . . . . . . . . . . . 69 PR Table, Index, Lookup & Update Definition - DRLTS001 (Part 1 of 4) . 69 PR Table, Index, Lookup & Update Definition - DRLTS001 (Part 2 of 4) . 70 PR Table, Index, Lookup & Update Definition - DRLTS001 (Part 3 of 4) . 71 PR Table, Index, Lookup & Update Definition - DRLTS001 (Part 4 of 4) . 72 Component Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 New Component Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Add Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Created Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Component Creation DRLIMS2P in hlq.LOCAL.DEFS (Part 1 of 2) . . . . . 79 Component Creation DRLIMS2P in hlq.LOCAL.DEFS (Part 2 of 2) . . . . . 80 Process Performance Reporter Statements . . . . . . . . . . . . . . . . . . . . . . . 81 Process Performance Reporter Statements . . . . . . . . . . . . . . . . . . . . . . . 82 Drop Migrated Temporary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Utility Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Recalculate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Selecting SAMPARM from Table List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 QMF ADD SAMPARM Data Entry Window . . . . . . . . . . . . . . . . . . . . . . . . 87 Parameter Table Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 SAMPARM Report Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 SAMPARM Report after Correcting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 TABPROC DB2 Load Utility (Part 1 of 2). . . . . . . . . . . . . . . . . . . . . . . . . . 92 TABPROC DB2 Load Utility (Part 2 of 2). . . . . . . . . . . . . . . . . . . . . . . . . . 93 Unload and Load Using IXF File and QMF (Part 1 of 2) . . . . . . . . . . . . . . 94 Unload and Load Using IXF File and QMF (Part 2 of 2) . . . . . . . . . . . . . . 95 Load SQL Statement (MIGPARM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Member to Populate Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Drop SAMPRM Temporary Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . . 97 SLR Group and Report Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 SLR Command View for Report Generation . . . . . . . . . . . . . . . . . . . . . . 102 SLR Report Output (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 SLR Report Output (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Migration Parameters for Report Migration Window . . . . . . . . . . . . . . . . 104 Migration Parameters for Reports Window (Part 1 of 2) . . . . . . . . . . . . . 105 Migration Parameters for Reports Window (Part 2 of 2) . . . . . . . . . . . . . 105 PR Report Migration Window (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . 107 PR Report Migration Window (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . 108 PR Job Created by ERMT Tool (Part 1 of 6) . . . . . . . . . . . . . . . . . . . . . . 110 PR Job Created by ERMT Tool (Part 2 of 6) . . . . . . . . . . . . . . . . . . . . . . 111 PR Job Created by ERMT Tool (Part 3 of 6) . . . . . . . . . . . . . . . . . . . . . . 112 PR Job Created by ERMT Tool (Part 4 of 6) . . . . . . . . . . . . . . . . . . . . . . 113 PR Job Created by ERMT Tool (Part 5 of 6) . . . . . . . . . . . . . . . . . . . . . . 114 PR Job Created by ERMT Tool (Part 6 of 6) . . . . . . . . . . . . . . . . . . . . . . 115
viii
84. Element Created in Local.DEFS after the Migration Job . . . . . . . . . . . . . 116 85. Contents of Member TESTSUMR before Modification . . . . . . . . . . . . . . 117 86. Contents of Member TESTSUMR after Modification . . . . . . . . . . . . . . . . 117 87. Contents of Member TXTQA001 before Modification . . . . . . . . . . . . . . . 118 88. Contents of Member TXTQA001 after Modification . . . . . . . . . . . . . . . . . 119 89. Other Pull-down from Main Administration Panel . . . . . . . . . . . . . . . . . . 120 90. Process PR Statements Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 91. Report Installation Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 92. Reports Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 93. Report View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 94. Form Panel (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 95. Form Panel (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 96. Report Output (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 97. Report Output (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 98. Component Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 99. Add Objects to a Component (Part 1 of 2). . . . . . . . . . . . . . . . . . . . . . . . 126 100.Add Objects to a Component (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . 128 101.Append to Member DRLIMS2P in hlq.LOCAL.DEFS . . . . . . . . . . . . . . . 128 102.Component List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 103.PR Tables Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 104.Retention Period Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 105.Purge Condition Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 106.Purge Condition Window Showing Conditional Purge Conditions . . . . . 134 107.Online Purge Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 108.Non-comment Cards from DRLJPURG Job . . . . . . . . . . . . . . . . . . . . . . 136 109.DRLMIGRATION Table Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
ix
Tables
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. Significant Differences in Key Functions.. . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Where to Find Data in SLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Some Critical Data to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Comparison between SLR Tables and PR Definitions . . . . . . . . . . . . . . . 56 Comparison of SLR and PR Reporting Functions . . . . . . . . . . . . . . . . . . . 99 DRLJPURG Parameters to Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 DRLMIGRATION Table Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 MVS_ADDRSPACE_H Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 MVS_SYSTEM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 MVS_ADDRSPACE_H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 MVS_ADDRDISTR_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 MVS_PROGRAM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 MVS_COMPCODE_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 MVS_WORKLOAD_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 MVS_PRINTER_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 MVS_TAPE_M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 MVS_IPL_T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 AVAILABILITY_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 DFSMS_DATASET_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 DFSMS_VOLUME_D/M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 DFSMS_BACKUP_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 DFSMS_MIGRATION_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 DFSMS_DASD_CAP_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 DFSMS_TAPE_CAP_D/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 DFSMS_ACTIBVITY_M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 DFSMS_LAST_RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 DFSMS_MIGRATE_DAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 DFSMS_DS_OWNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 DB2_TRANSACTION_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 DB2_USER_TRAN_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 DB2_APPL_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 DB2_USER_AP_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 DB2_TRAN_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 DB2_USER_DIST_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 DB2_APPLICATION_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 DB2_USER_APPL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 EREP_DASD_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 EREP_VTAM_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 EREP_CPU_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 EREP_DASD_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
xi
41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75.
VMACCT_SESSION_M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 VMPRF_SYSTEM_M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 VMPRF_PROCESSOR_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 VMPRF_USER_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 VMPRF_DASD_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 CICS_TRANSACTION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 CICS_M_GLOBAL_D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 MSG_SYSLOG_TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 MSG_SYSLOG_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 AVAILABILITY_W/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 NW_NPM_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 NW_ALERT_BASIC_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 NW_ALERT_GENERIC_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 NW_SESSION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 NW_RTM_RESONSE_W/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 NW_SM_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 NW_NCP_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 NW_PU_UTIL_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 NW_LINE_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 NW_NPM_TRANSIT_W/M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 NW_X25LN_UTIL_W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 NW_X25PU_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 NW_X25NI_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 NW_NTRIP_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 NW_NTRIL_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 NW_NEO_UTIL_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 IMS_TRANSACTION_W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 OPC_AUTO_EVENT_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 OPC_MCP_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 OPC_MISSED_FB_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 OPC_OPER_EVENT_M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 OPC_OPER_EVENT_T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Predefined SLR Table to PR Table Cross Reference . . . . . . . . . . . . . . . 181 PR to Predefined SLR Table Cross Reference . . . . . . . . . . . . . . . . . . . . 185 SLR Parameter Table to PR Lookup Table Cross Reference . . . . . . . . . 189
xii
Preface
This redbook will help you plan and perform the migration from Service Level Reporter to Tivoli Performance Reporter for OS/390. Information presented in this redbook about the migration process and the different approaches for performing a migration can assist you in preparing for your migration and selecting the best approach for performing your migration. This redbook is intended to help the enterprise performance administrator migrate Service Level Reporter information to Tivoli Performance Reporter for OS/390 by providing detailed guidance on performing the migration steps with knowledge gained by the authors while performing an actual migration. The migration steps presented in this redbook are described using examples that you can duplicate to perform your own migration. A working knowledge of Service Level Reporter and Performance Reporter is assumed.
The Team That Wrote This Redbook

This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, Austin Center. Mike Foster is a senior programmer at the ITSO, Austin Center and holds a bachelor of science degree in electrical engineering from the University of Kansas. He writes extensively and teaches classes world wide on a variety of topics including Tivoli products. Before joining the ITSO in 1995, he held both management and technical position in IBM marketing and development divisions supporting MVS, CICS and DB2 products world wide for over 25 years. Mauro Basile is a system engineer at Rome Tivoli Laboratory in Italy. He has over 30 years experience in both hardware and software with IBM and Tivoli. He holds a diploma of Perito Elettrotenico Industriale in Italy. Before joining IBM he was a electronic technician in the Italian Navy. For the past 15 years he has been focusing on software including working with several large accounts running TPF in Italy. For the past three years he has been a member of the Tivoli development team working extensively with both Service Level Reporter and Performance Reporter. Malcolm Pearse is a senior IT specialist with IBM Global Services in South Africa. He joined IBM Global Services in 1997 where he has worked exclusively with Performance Reporter 1.2 and 1.3. Before joining IBM he worked for a large mining company for 13 years in areas of operations, helpdesk, systems programming/analysis, performance/capacity
xiii
management and chargeback, combining these roles with extensive use of reporting and reporting tools. Thanks to the following people for their invaluable contributions to this project: Marcus Brewer International Technical Support Organization, Austin Center Robert Haimowitz International Technical Support Organization, Poughkeepsie Center Nick Riches IBM United Kindom Judit Csapo IBM Sweden Bruce Cullen IBM Sweden Juliette Meinstein Tivoli Systems, Performance Reporter Evangelist Van Collins Tivoli Systems Customer Support Sharon Brower IBM Software Migration Project Office, Tivoli Performance Team Richard Orr IBM Advanced Technical Support, Tivoli Systems Management Al Hanna IBM Software Migration Project Office, Tivoli Migration Team Butch Rambish IBM Software Migration Project Office, Tivoli Performance
Comments Welcome
Your comments are important to us! We want our redbooks to be as helpful as possible. Please send us your comments about this or other redbooks in one of the following ways:
xiv
Fax the evaluation form found in ITSO Redbook Evaluation on page 211 to the fax number shown on the form. Use the electronic evaluation form found on the Redbooks Web sites: For Internet users For IBM Intranet users http://www.redbooks.ibm.com http://w3.itso.ibm.com
Send us a note at the following address: redbook@us.ibm.com
xv
xvi
Part 1. Migration Overview
Chapter 1. Introduction
This chapter introduces the advantages of using Performance Reporter and provides a brief introduction to Performance Reporter and an overview of the Service Level Reporter (SLR) to Performance Reporter (PR) migration.
1.1 Why Upgrade to Performance Reporter?

Performance Reporter has many characteristics and functions that most customers find as improvements over Service Level Reporter. In most, if not all cases, customers find that their collect process is considerably faster with Service Level Reporter. Some of the other benefits of converting to Performance Reporter are: Improvements and enhancements to Performance Reporter are ongoing, whereas, there is no development being done to Service Level Reporter. Performance Reporter is easier to use than Service Level Reporter. Performance Reporter is based on DB2, meaning you do not have to learn a proprietary data management system or query language as in Service Level Reporter. Incorporation of new report requirements is facilitated. Performance Reporter utilizes the DB2 capability allowing for columns to be added dynamically to the database. This allows for the adding of new columns to the database without having to export, delete, redefine, and reload the database as would have to be done with Service Level Reporter. Computations can be altered dynamically in Performance Reporter without any cumbersome redefinition as with Service Level Reporter. Performance Reporter takes advantage of improvements in DB2 technology. For example, when Distributed Relational Database Architecture (DRDA) was implemented in DB2 V2.3, Performance Reporter users gained the ability to access performance data from remote systems. With the introduction of DB2 V3, Performance Reporter databases were eligible for compression, greatly reducing the amount of DASD resource consumption. The latest releases of DB2 provide Open Database Connectivity (ODBC) and TCP/IP capabilities. Performance Reporter provides supported features for data collection and reporting of information from Unix, Windows NT, and AS/400 systems. With version 1.4 of Performance Reporter, a JAVA viewer interface is provided that allows graphical and tabular representations of Performance
Reporter data from any desktop environment. Service Level Reporter reports and graphs are only displayed on the mainframe. Performance Reporter boasts a new feature specifically developed for the accounting and chargeback analyst called The Accounting Workstation Option. This option is a graphical user interface (GUI) based feature designed to assist Information Technologist (IT) financial analyst functions. The Performance Reporter table definitions are stored directly in DB2 in contrast with Service Level Reporter, where the table definitions have to be compiled and stored as load modules in a load library. With the QMF facility, the user can easily create ad hoc reports. The accounting feature in Performance Reporter has been enhanced and expanded over the accounting feature in Service Level Reporter. In addition with the data stored in DB2, the accounting feature in Performance Reporter is easier to use and the data easier to handle compared to Service Level Reporter where the accounting data is a separate database.
1.2 Overview of Performance Reporter

Performance Reporter performs two basic functions: Collecting systems management data into a DB2 database. Reporting on the data stored in the database. Performance Reporter consists of a base product and several optional features: System Performance feature Network Performance feature CICS Performance feature IMS Performance feature AS/400 System Performance feature Workstation Performance feature Capacity Planner Accounting feature Accounting Workstation Option (AWO)
The Performance Reporter base can generate graphic and tabular reports based on the information it has stored in its DB2 database based on the systems management data it has collected. The base product includes the administration dialog, the reporting dialog, and the log collector, all of which interact with a standard DB2 database as shown in Figure 1 on page 5.
Input Datasets
Administration Dialogs Reports
DB2 Log Collector Database Reporting

Reports
Optional Features
COLLECT
SUMMARIZE
REPORT
Figure 1. Performance Reporter Overview
Performance Reporter features provide DB2 table definitions and table update instructions for collecting required systems management data. They also provide predefined queries, forms, and reports for presenting that data. The Performance Reporter features allow you to collect and report on systems management data, such as systems management facilities (SMF) data or IMS log data. Each Performance Reporter performance feature has components that are groups of related Performance Reporter definitions. For example, the MVS Performance Management component consists of everything Performance Reporter needs to collect log data and create reports showing MVS performance characteristics.
Introduction
In addition, the Capacity Planner feature lets you download summarized data from the Performance Reporter database to a workstation and analyze and plan the usage of key MVS/ESA and MVS/XA resources.
1.3 Introducing the Log Collector

The central part of Performance Reporter is the log collector program that reads performance data and processes it. Log collector tasks are controlled by various definitions. These definitions are listed in Section 1.3.1 of this chapter. The log collectors main function is to read data and store it in data tables in the Performance Reporter database. The log collector groups the data by time period, and computes sums, averages, minimums, maximums, and calculates resource availability.
1.3.1 Log Collector Functions

Log Definitions: To collect log data, Performance Reporter needs log descriptions. Performance Reporter gathers performance data about systems from sequential datasets, such as those written by systems management facilities (SMF) under MVS. These datasets are referred to as log datasets or logs. The log collector stores descriptions of logs as log definitions in the Performance Reporter database. All log definitions used by Performance Reporter features are provided with the Performance Reporter base. If, however, you are migrating user defined table definitions, then you will have to create the appropriate log definitions. Record Definitions: Each record in a log belongs to a unique record type. Examples of record types include SMF type 30, generated by MVS, and SMF record type 110 generated by CICS. For Performance Reporter to process a record, the record type must be defined. Detailed record layouts, field formats and offsets within a record are described in Performance Reporter record definitions. All record definitions used by Performance Reporter features are provided with the Performance Reporter base, but again, the appropriate record definitions for user defined tables will have to be created when migrating from Service Level Reporter. Update Definitions: Instructions for processing data and inserting it into tables of the Performance Reporter database are provided in update definitions. Each update definition describes how data from a source (either a specific record type or a row of a table) is manipulated and inserted into a
row of the target table. All update definitions used by Performance Reporter feature are provided with Performance Reporter. Any update definition for user defined tables will have to be created when migrating from Service Level Reporter. Table Definitions: Performance Reporter stores data collected from log data sets in database tables. A table definition identifies the database and table space in which a table resides, as well as the columns that make up the table. The table definitions used by the components in the Performance Reporter features are provided with the feature. For user defined tables in Service Level Reporter, the table definitions will have to be created when migrating to Performance Reporter. Log and Record Procedures: Log procedures and record procedures are user-exit programs for specific data collection situations. They are similar to record build exits provided with Service Level Reporter. Record procedures work on specific record types. Log procedures work on an entire log. The log and record procedures used by Performance Reporter features are provided with the Performance Reporter base. The Collect Process: When definitions for a log, its records, its update instructions for record data, and target tables exist in Performance Reporter, you can collect data from the log. The Performance Reporter log collector retrieves these stored definitions and performs the data collection they define.
1.4 Comparison between PR and SLR

In order to understand the need for migration, rather than a wholesale copy of everything that existed in Service Level Reporter, you should look at the similarities and differences between the two products. Table 1 on page 7 shows the major differences from a task perspective.
Table 1. Significant Differences in Key Functions.
TASK Summarize Data
SLR > Summary Table > Total Pattern > SLR Log Table > View (Summary tables only)
PR > Update Definition > DB2 View > Report > Update (2 + Records to one table) > DB2 View > Report
Join/Merge data from several input records
Introduction
TASK Directly modify Log Record Delete data based on age Table Lookup during Collect Calculations (excluding Summarizations)
SLR Collect Exit (Record Build Exit) Purge Command Parameter Table > Tables (COMPCOL) > Views (DATACOL)
PR Record Procedures Purge Definition > Update Definition > Lookup Table > Update Definition > DB2 View > Report
1.4.1 Summarize Data

Summarized Data is the major reason for using a product such as Service Level Reporter or Performance Reporter. Service Level Reporter is biased towards Collect time summarization based on total patterns. This means that reporting requirements have to be anticipated early in the implementation cycle with the appropriate total patterns (TOTPATS) verified or included. In Performance Reporter a hierarchy of tables provides time level summarization. A naming convention is used in many of the Performance Reporter components to identify the level of data within a table. The addition of a suffix to the table name identifies the level of the data in each table. For example, the table MVS_SYSTEM_M contains information on the monthly statistics of processor activity, paging and swapping activities, IPLs, and lost SMF data. The naming convention suffixes used in Performance Reporter are: _T _H _D _W _M Timestamp level. It provides the same level of summarization as the SLR log table. It is not present in all cases. Hourly summary Daily summary Weekly summary Monthly summary
Summarization for non-time key columns (e.g. MVS System ID) can be done by SQL Select in a View or query. The choice is normally dependent on the number of different values expected for a key column. For example, the column containing MVS System ID would probably have a few distinct values, therefore report time summarization would be OK, but a column, such as CICS user ID, may have many distinct values, and so collect-time
summarization is used to avoid the risk of Performance Reporter reading tens or hundreds of thousands of rows to make a one-page report.
1.4.2 Join/Merge Data

Some Service Level Reporter tables (like JOBLOG) are based on input from several record types. This joining was accomplished using special Service Level Reporter code. In Performance Reporter, the ability to use multiple update definitions against tables circumvents this problem. This fact must be borne in mind however, as tables such as MVS_ADDRSPACE_H contain batch, started tasks, and TSO information, while in Service Level Reporter, this would all have been held in separate tables. With summary tables, it is possible to merge data with a Service Level Reporter view. In addition, Service Level Reporter views are often used to provide additional information about the data using calculations. A similar function is provided within DB2 with the VIEW function, but with DB2 the calculations can be done either in a view or through SQL in a Performance Reporter report. In many cases, it is better to move calculations from a Service Level Reporter view to a Performance Reporter report.
1.4.3 Directly Modify Log Records

Both products use similar techniques. Performance Reporters capabilities in this area are a super-set of those in Service Level Reporter. In most cases, where the function from a Record Build Exit is needed in Performance Reporter, it will be possible to use the same logic as before in the Performance Reporter record procedure. All Service Level Reporter exits should be checked before implementation in Performance Reporter because, in many cases where exits were previously required with Service Level Reporter, the more powerful capabilities of Performance Reporter can provide the desired results. For example, the function provided by Record Build Exit DREEXOPC in Service Level Reporter is no longer required with Performance Reporter.
1.4.4 Purging Data

Both Performance Reporter and Service Level Reporter allow the deletion of data based on age. With Service Level Reporter, this can be a complicated process because of the large data structure (Total Patterns). The purge conditions from Service Level Reporter can not be readily migrated to Performance Reporter, but they can be implemented quickly and easily at a later stage. See Chapter 7.1, Setting Purge Conditions on page 131 for a description of the setting of purge conditions.
Introduction
1.4.5 Table Lookup During Collect

The ability to enhance the information stored in Service Level Reporter by using parameter tables is an important function. It allows for the substitution of data and grouping of related data, such as applications and users. The same capability is provided with Performance Reporter. Lookups are carried out within an update definition, and it is therefore possible to provide additional information to lower level summaries. For example, you may use a Lookup to group transactions to applications in one table and then do another Lookup to find the response time objective for that application from another table. This process is used within the Performance Reporter IMS feature.
1.4.6 Calculations
In order to perform any calculation with Service Level Reporter, either COMPCOLS had to be coded within the table definition or a Service Level Reporter view created. Performance Reporter is much more flexible in this area. Calculations can be carried out in update definitions if required, but more commonly the SQL query used for reporting will contain most calculation logic. This is an important point for migration, as Performance Reporter does not have any equivalent function to COMPCOL. All columns in DB2 tables must be "real". Because of this, the table migration tools provided with Performance Reporter do not attempt to resolve COMPCOL macros. They must be dealt with manually.
1.4.7 Reporting
Although the principles are the same in both products (the using data from the database and presenting it to an end-user as information), Performance Reporter has far superior facilities for selecting and formatting the data. Calculations can be carried out within the SQL query, eliminating some of the need for table modifications. In addition, Performance Reporter reports can be based on more than one table without resorting to a view, and reports can have meaningful column headings by using QMF forms.
1.4.8 PR Data Flow

A summarization of the Performance Reporter data collection process is shown in Figure 2 on page 11 and is explained following the figure.
10
Input
3 2
Log Definition
4
Record Definitions
1
Logs
5
Record Procedure
Update Definitions
Lookup Tables
8 9
Data Tables
Reports
11
Update Definitions
10
11
Data Tables
Reports
Figure 2. Overview of Performance Reporter Data Collection Flow
Performance Reporter processes data as follows: 1. The operating system, or other programs, write data to a log data set.
Note
Input log data set can be a sequential file or a member of a PDS. Also the input data can be a group of concatenated data sets. 2. You initiate the collect either through the dialog or by using a Performance Reporter language statement in a job. When you submit the collection, you identify the log definition to be used in the collection. 3. Performance Reporter initiates log collection for the log specified. 4. Performance Reporter looks for record definitions associated with the log definition in its system tables. It applies those record definitions to specific record types from the log or log procedure. 5. Optionally, a record definition might require processing through a user-exit program, a record procedure. If a record definition requires processing by a record procedure:
Introduction
11
The record procedure receives only a specific record type and is not called for other record types. Output from a record procedure varies in format and is usually a record mapped by a Performance Reporter record definition. 6. Performance Reporter applies a specific update definition to each known record type and performs the data manipulations and database updates as specified. 7. Performance Reporter often selects data from Lookup tables to fulfill the data manipulations that the update definitions require. 8. Performance Reporter writes unsummarized and first-level summarized data to data tables specified by the update definitions. 9. Performance Reporter uses updated tables as input for updating other, similar tables that are for higher summary levels. If update definitions specify data summarization, then Performance Reporter selects data from a table as required by the update definitions and performs required data summarization. (Performance Reporter might select data from Lookup tables during this process, but this step is not shown in Figure 2 on page 11). 10.Performance Reporter updates other data tables as required by update definitions.
Notes
Normal summarization of updates from table to table is time related, such as hourly, daily, weekly, monthly, and yearly. Data tables that are updated from other data tables, such as a monthly table, will contain time to date values in the fields. Thus, the current monthly table, if you report on its contents, will report summary values to date for the month. 11.Reports are generated from the data in the tables.
1.4.9 SLR Data Flow

A summarization of the Service Level Reporter data collection process is shown in Figure 3 on page 13 and is described following the figure.
12
Log data 1
SLR Collect SLR selection exit 2 4a SLR computation exit 4b SLR log tables 5 6 SLR parameter tables
SLR record build exit 3
SLR summary tables 7
SLR report language 8
SLR parameter tables
SLR reports 10
Figure 3. Overview of Service Level Reporter Data Collection Flow
Service Level Reporter processes data as follows:
Introduction
13
1. The operating system or other programs write data to a sequential log data set. These data sets are input to Service Level Reporter. Data collection is initiated by using the SLR COLLECT statement in a batch job, identifying a specific LOGSOURCE. 2. Each input record is passed to the Service Level Reporter record selection exit where certain records can be spun off to other files, or the number of records to be processed can be restricted. 3. Optionally, the log source might specify the use of a record build exit to build a new record from the input record with additional or amended information from the original input record. 4. Optionally, the log source might specify the use of a computation exit, such as DRESXT1. If the log source requires the use of a computation exit: a. The computation exit receives each record in the log as input. b. Output from the computation exit will be added to the input record and written into the SCxUSER and SNxUSER columns in Service Level Reporter log tables. 5. The built record is then used to create the rows in the appropriate Service Level Reporter log tables. 6. Service Level Reporter can use data selected from parameter tables to provide additional information in log tables. 7. Service Level Reporter uses the log table information to update the appropriate summary tables. Summary table rows with totals are created as the last stage of collect. 8. Once Service Level Reporter stores the data from a collect, reports can be run against the data. Service Level Reporter uses a unique language to select data for the report. 9. Optionally, Service Level Reporter might select data from parameter tables specified in the query. 10.Service Level Reporter creates the report, displaying, printing, or saving it as you requested.
1.5 How to Use This Redbook

This redbook is divided into two parts. Part 1, Migration Overview on page 1 contains Chapter 1, Introduction on page 3, and Chapter 2, Migration Approaches on page 17 that give an overview of both Performance Reporter and Service Level Reporter and the migration process for moving information
14
from Service Level Reporter to Performance Reporter. Part 2, Migration Examples on page 29 gives detailed examples of actual migration steps performed by the writers of this redbook showing how to migrate Service Level Reporter information into Performance Reporter. Depending on the migration approach you decide to perform from those described in Chapter 2, Migration Approaches on page 17, you can use the information in Chapters 3 though 7 to show you how to perform the specific steps and actions required to complete the movement of information from Service Level Reporter to Performance Reporter. Since not all readers will select the same approach for migrating between Service Level Reporter and Performance Reporter, you only need to focus on the information in the chapters associated with the migration activity you need to perform. The migration activities described in Chapters 3 through 7 are: Chapter 3, Migrating Data from Predefined SLR Tables on page 31 covers the migration of Service Level Reporter data from predefined Service Level Reporter tables into Performance Reporter tables for one or more Performance Reporter components using the Performance Reporter migration utility. Chapter 4, Migrating User-Defined A.L.L Based Tables and Data on page 57 covers the migration of Service Level Reporter data, log and table definitions from user-defined summary tables, and log tables into Performance Reporter. Chapter 5, Migrating Parameter Table Data on page 85 covers the migration of data from Service Level Reporter parameter tables into Performance Reporter Lookup tables. Chapter 6, Migrating SLR Reports on page 99 covers the migration of Service Level Reporter reports to Performance Reporter reports using the Performance Reporter migration utility. Chapter 7, Miscellaneous Items on page 131 covers others items that the administrator needs to perform associated with the migration from Service Level Reporter to Performance Reporter that fall outside the actual movement of information between the two reporting systems. Appendix A, The Key to Predefined Migration - DLRMIGRATION on page 137 contains a complete cross reference of information from the DLRMIGRATION table which the migration utility uses to guide and direct the migration of predefined Service Level Reporter table data into Performance Reporter tables. Appendix B, Predefined SLR Tables to PR Tables Cross Reference on page 181 provides both a cross reference of predefined Service Level 15
Introduction
Reporter tables to Performance Reporter tables and Performance Reporter tables to predefined Service Level Reporter tables that show where the migration utility will get data from and where it will place the data when migrating predefined Service Level Reporter tables. Appendix C, Parameter Table to Lookup Table Cross Reference on page 189 lists the predefined Service Level Reporter parameter tables and which Performance Reporter Lookup table holds similar information.
16
Chapter 2. Migration Approaches

This chapter reviews the options available to you for migrating from a Service Level Reporter to a Performance Reporter environment. The details on how to perform the activities for each of the approaches discussed in this chapter will be presented in Part 2, Migration Examples on page 29.
2.1 Introduction to Performance Reporter Migration

The elements you are wanting to protect your investment in by migrating them to Performance Reporter are comprised of: Data in the database that is needed for historical information, trend analysis, and capacity planning. Customized tables you have developed to support new data sources or amend supplied code. Views you have developed that add function to tables and reports. Reports you have written. Service Level Reporter and Performance Reporter perform essentially the same tasks, although in slightly different manner. The task of migration should therefore be to protect the investment that has been made in Service Level Reporter data and provide the same or better information to end users following the migration. The differences in the products and their data structure means that tasks have to be accomplished differently between Service Level Reporter and Performance Reporter. This means that the operational procedures that support the reporting process will need to be altered to accommodate these differences following the migration. Tools are provided with the Performance Reporter base product to assist you in performing the migration from Service Level Reporter to Performance Reporter. These tools automate the moving of data and tables between Service Level Reporter and Performance Reporter. In order to get the most benefit from using the Performance Reporter migration utilities, you will want to develop a migration plan.
17
2.2 The Migration Tool

The migration tool is made up of several REXX execs located in hlq.SDRLEXEC (DRLEMIGQ, DRLEMIGR,DRLEMIG0 and DRLEMIRX) and many definitions members located in hlq.SDRLDEFS (DRLWxxxx). The migration tool is accessed using the administration dialogs and supports the following functions for migrating data from Service Level Reporter to Performance Reporter: Migrate DATA from Service Level Reporter predefined set of tables to Performance Reporter DB2 tables. Migrate user defined Service Level Reporter tables to Performance Reporter definitions and DB2 tables and copy the data. Migrate user defined Service Level Reporter reports to Performance Reporter. There are three different functions provided by the migration tool, and you will use some, or all, of these functions depending on what and how you to choose to migrate. The migration of data from the Service Level Reporter predefined table occurs in two steps: 1. Performance Reporter unloads data from Service Level Reporter data base to IXF data set. 2. Performance Reporter imports the unloaded data into a temporary Performance Reporter DB2 table (using QMF or not using QMF) and then Performance Reporter selects a subset of data from the temporary DB2 table to be stored in the appropriate Performance Reporter DB2 table. All this process is controlled by the information in a Performance Reporter system table called DRLMIGRATION that is able to guide the tool in choosing the right definition members to perform the Unload (through Service Level Reporter Report statements to an IXF file) and Load operation (through SQL statements to populate the related Performance Reporter table). Refer to Figure 109 on page 141 for the lay-out of DRLMIGRATION table. In order to migrate user defined Service Level Reporter tables, the standard process builds only a single summary table at the most detailed time key available, so additional work will have to be undertaken to define any summarization beyond this level.
18
Not all the Service Level Reporter keywords can be translated in table columns in the DB2 Performance Reporter database. For example, COMPCOL is one of the most important that is not translated. In the standard Performance Reporter tables, this function is either part of the update structure or is coded within the supplied reports. It is, therefore, very easy to carry out the same modifications for any COMPCOL that have been added or amended by the customer as will be covered in Chapter 6, Migrating SLR Reports on page 99. In order to help the migration of the reports, a tool has been developed, called ERMT, to provide a conversion of Service Level Reporter Report language statements to SQL queries. The reports are migrated from Service Level Reporter ISPF tables (SLRTABL) or from Service Level Reporter report command source data sets. During the migration, QMF queries and forms are created, as well as Performance Reporter report definitions. These are used to create Performance Reporter report groups and reports.
2.3 Developing a Migration Plan

The need for planning your migration cannot be emphasized strongly enough. There are many factors that have to be considered before undertaking what could be a lengthy and complex process. The purpose of this cookbook is to provide you with an understanding of the migration process and the factors involved in performing a migration so that you will be able to better plan your Service Level Reporter to Performance Reporter migration. There may be skills that you can call upon within your own enterprise for help in this area. Most customers have undertaken application migrations or migrated from one release of software to another. Service Level Reporter to Performance Reporter migration is not very different from these processes. The migration should be treated as a project with the establishment of objectives and timescales. Any migration plan should consider and include the following areas: Identification of critical data Assessment of the importance of that data Assessment of possible migration approaches Skill requirements Priority
Migration Approaches
19
Operational requirements New procedures Expect to spend some time planning your migration before carrying out any tasks, as migration from Service Level Reporter to Performance Reporter should be taken as an opportunity to re-assess the reporting requirements of the enterprise. The skills of the personnel involved in the migration will have a bearing on the kind of tasks you are able or willing to undertake during the migration. Some customers have found that when they study the various reports currently being produced in Service Level Reporter, that in some cases, modifications have been made in the past to fulfill requirements that no longer are needed or required in todays environment. With good analysis and planning, you may find that you can save time and effort in the migration process by not migrating items that are no longer required.
2.3.1 Analysis of What to Migrate

Regardless of the approach you choose, you will need to determine what data should be migrated and what data is not worthy of migration since there is always some cost and effort associated with migration. Some considerations in this regard are: Audit Requirements There could, for instance, be a legal need (contractual obligations) to keep data for certain periods of time so that past usage and accounting reports produced and sent out to customers could be audited and results verified.
Need for Trend Data for Capacity Planning Capacity planning is essential in any organization. To this end, trend analysis to determine peaks and troughs is vital.
Retention Periods for Tables The retention periods for tables should only be used as a reference for the setting of purge parameters in Performance Reporter and would not be migrated as such. Profiles could be extremely important for trend analysis.
Total Patterns
20
User-Defined Tables
Service Level Reporter may not have had a pre-defined table for certain data types, and you may have defined your own A.L.L table to collect this data. Before migrating these table definitions, check to see whether or not Performance Reporter has a suitable equivalent.
2.3.2 Elements of a Plan

The key elements of a good migration plan and suggestions as to what to look for in each element are discussed below. 2.3.2.1 Identification of Critical Data Deciding what Service Level Reporter data is critical to an enterprise is the first stage in a successful migration. To begin with, this should be a top down approach. For example: 1. Identify the important sub-systems in the enterprise (eg. CICS, IMS, Batch, TSO) 2. Identify measurement requirements (eg. CPU, DASD) 3. Identify the types of measurement required (eg. CPU busy, transaction response, DASD utilization) 4. Identify the current uses of the data (eg. performance measurement, capacity planning, service level reporting) 5. Document any known future requirements Once the critical data has been identified, the next task is to map the appropriate Service Level Reporter table to that data. Table 2 gives some examples of Service Level Reporter tables and the kind of data they contain.
Table 2. Where to Find Data in SLR
Table Name ADDRSTAT AVAILSTAT CPULOAD CICSTRANSUM DB2ACCTSUM1/2 IMSTRANS JOBSTAT
Data Captured Address Space Data Resource Availability CPU Measurements CICS Transaction Data DB/2 Accounting Data IMS Transaction Data Batch Job Data
21
Table Name NR_NPMRESPS NR_NVRESPS PAGESUM TSOSTAT WORKLOAD
Data Captured NPM Response Time Data NetView RTM Data Paging Data TSO Session Data Data from RMF 72
There may be other tables beyond the predefined Service Level Reporter tables that contain data critical to your enterprise. Tables that may not be in the Service Level Reporter starter set but are user-defined. The number of tables identified may also be surprisingly small. In many cases, a large proportion of critical Service Level Reporter data can be found in 5 or 6 tables.
2.3.3 Assessment of the Importance of Data

The picture of what data to migrate to Performance Reporter is now beginning to develop, but you still need to assess the importance of the data at total pattern level. In addition to the detail information contained within Service Level Reporter summary tables, there is also a wealth of information held in total patterns, for example, Daily summaries. When considering what data to migrate to Performance Reporter, you need to assess its value. For example, normally there is no value in migrating hourly detail measurements of CICS transactions to Performance Reporter. The prime purpose of migrating data from Service Level Reporter to Performance Reporter is to preserve the historical information that has been built up over a number of months or years. Moving very detailed information does not meet this goal. In addition, the resources required to move large amounts of detail information can be expensive. As a guideline, monthly summary level data is probably the most granular that should be considered for migration. You should also be aware of other total patterns that may be important to migrate, for example, profiles. These are the totals that allow you to report on the hourly data, averaged by each day, across a month, or daily data, averaged by each month, across a year. This kind of data allows you to identify peak periods, such as month end processing or the peak hour for capacity planning purposes.
22
Table 3 shows the level of information that should be considered for migration.
Table 3. Some Critical Data to Migrate
Table Name ADDRSTAT AVAILSTAT CPULOAD CICSTRANSUM DB2ACCTSUM1/2 IMSTRANS JOBSTAT TSOSTAT WORKLOAD
Total Pattern Monthly level, Project detail Monthly level, Resource detail Monthly level Monthly level, Transaction detail Monthly level, Plan detail Monthly level, Transaction detail Monthly level, Project or Jobname detail Monthly level, Project detail Monthly level, Workload type detail
The data that you choose to migrate should be important and provide indicators to the "health" of the Information Systems (IS) business in the enterprise. Some examples of this are: Adequate availability and response time Adherence to schedules Sufficient capacity Cost effectiveness
2.3.4 Assessment of Possible Migration Approaches

The next stage in migration planning is to choose an approach. It is important that the critical Service Level Reporter data be identified before this stage so that an informed decision on how best to approach the migration of the Service Level Reporter data can be made. 2.3.4.1 Do not perform migration If the current Service Level Reporter system was largely unmodified and the value of the data regarded as low, then a possible approach would be to not migrate any data to Performance Reporter. It would be possible to collect new data into Performance Reporter and 'run-down' the Service Level Reporter database using the normal purge routines.
23
If this approach is adopted, then there are some disadvantages that must be considered: Additional disk space requirements of Service Level Reporter database and Performance Reporter Additional CPU time to perform purging of Service Level Reporter data Historical information would only be held in Service Level Reporter until such time as the Performance Reporter database had collected enough data. Two sets of reports would need to be produced. One from Performance Reporter showing the current data, and the second from Service Level Reporter showing historical information. This would complicate trend analysis. If, on the other hand, you decide not to keep Service Level Reporter data at all, and you merely start collecting data into Performance Reporter, then trend analysis could not be performed until such time as sufficient data had been collected in Performance Reporter. You would also have an exposure, if at a future date, somebody required a historical report for accounting or audit purposes. Because of these disadvantages, it is expected that some migration activity will take place in all Service Level Reporter installations that are moving to Performance Reporter. 2.3.4.2 Migrate Everything If a planning exercise were not being undertaken, then most Service Level Reporter sites would adopt this approach. The cost of this approach will be very high, and the value gained from migrating "just that little bit more" very small. When assessing critical data and where it can be found within Service Level Reporter, the number of tables identified should have been small, and the appropriate total patterns should have reduced the amount of data further still. Because of the architectural differences between Service Level Reporter and Performance Reporter, there will have to be a considerable amount of manipulation in order to achieve a total migration. This approach negates any value that might have been gained by re-assessing the reporting requirements of the enterprise. 2.3.4.3 Selective Migration By effective planning and assessment of critical Service Level Reporter data, the natural conclusion is to perform a selective migration. To perform a
24
selective migration you need to categorize each table to be migrated into one of the following classes: Standard log table, no modifications Standard summary table, no modifications Modified table Customer defined table You can further classify the modified or customer defined tables, according to the nature of the modifications: Addition or modificationof computed columns Information on how to perform this type of migration can be found in Chapter 3.3.1, Addition or Modification of Computed Columns on page 53 Addition or modification of data columns Information on how to perform this type of migration can be found in Chapter 3.3.2, Addition or Modification of Data Columns on page 53 Addition or modification of key columns Information on how to perform this type of migration can be found in Chapter 3.3.3, Migrating User-Defined Tables on page 55. Tables for new log sources Information on how to perform this type of migration can be found in Chapter 4, Migrating User-Defined A.L.L Based Tables and Data on page 57. In each of these scenarios, see the referenced chapter for details on how to perform the migration. You should, however, investigate the reason for each modification or addition because the support may now be provided in Performance Reporter or easily obtained through a report, as in the case of COMPCOLs.
2.3.5 Other Plan Items

There are many operational procedures that will change as a result of migrating from Service Level Reporter to Performance Reporter. These should be considered and documented in the plan. New procedures for data collection and purging need to be set up. The amount of DASD space required for the Performance Reporter database, how often to run a DB/2 reorg, are all items that need addressing before going into production.
25
2.3.5.1 Operational Requirements and Considerations Several items need to be planned for when making the migration from Service Level Reporter to Performance Reporter. Included in the list of items to consider are: DASD Space and Reorg Current estimates are that, for any given set of Service Level Reporter tables, the Performance Reporter equivalents will require about 75% of the DASD space. The use of DB2 partitioned tablespaces could reduce the DASD requirement still further, and the use of compression would reduce DASD usage by even further. Data Collection The data collection routines will be generated as part of the Performance Reporter tailoring process, but consideration should be given to DB2 commit points and buffer sizes. Each Performance Reporter table has a built-in data purge condition. It is activated by use of the Performance Reporter PURGE command. The purge conditions should be reviewed and amended if necessary.
Purging
Note
It is easier to fix the problem of too much data than it is to re-create older data that has been purged. Education Users that have been familiar with creating Service Level Reporter reports now have a new set of skills to acquire (SQL and QMF) to achieve the same results. The migration plan must, therefore, include provision for training of end users.
2.3.5.2 New Procedures You will have new collection jobs and JCLs, new reporting procedures, new means of purging old data, and new securities. It is, therefore, essential that all persons and departments involved in the process (e.g. Operations) be appraised of the new procedures and given the relevant documentation. Many reports will have changed in format. Recipients of these reports should be made aware of the changes.
26
2.3.5.3 Retention Periods You can basically decide on any retention period you like, keeping in mind, of course, the amount of space required for low level summaries. See Chapter 7.1, Setting Purge Conditions on page 131 or "Displaying and editing the purge condition of a table" in the Performance Reporter for OS/390 Administration Guide, SH19-6816. 2.3.5.4 When to Switch Over Most installations will differ in this regard. The migration approach selected by you will have a bearing, as will the length of time taken to install and customize Performance Reporter. You can basically switch as soon as youre comfortable with what you get from Performance Reporter.
27
28
Part 2. Migration Examples
29
30
Chapter 3. Migrating Data from Predefined SLR Tables

The example in this chapter looks at the steps necessary to migrate data from predefined Service Level Reporter tables to Performance Reporter tables. The tools necessary to migrate data from Service Level Reporter to Performance Reporter are provided with the Performance Reporter base product. This chapter will show you how to use these tools to assist in the migration of data from the Service Level Reporter predefined tables into Performance Reporter tables. The Migration dialog shown in Figure 5 on page 32 provides the interface to the Performance Reporter tools to assist you in your migration of data from Service Level Reporter starter set (predefined) tables to Performance Reporter. You can access the Migration dialog by selecting 4. Migration from the System window, as shown in Figure 4. You can access the System window by entering system on any Performance Reporter dialog command line and pressing Enter.
Figure 4. Administrator Window
31
Note
Some of the Performance Reporter dialog screens shown in this redbook display the ISPF panel identification. For example, the panel shown in Figure 4 on page 31 displays in the upper left hand corners the names DRLDAADM and DRLDASYS. If you wish to show these panel ids on your screen, enter PANELID on the command line of any Performance Reporter dialog. Provide the library names that describe the Service Level Reporter environment that you wish to migrate from. This information is entered on the Migration Parameters for Table Migration window as shown in Figure 6 on page 33. You can access the Migration Parameters for Table Migration window by selecting 1. Migration parameters for table migration from the Migration window as shown in Figure 5.
Figure 5. Migration Window
Performance Reporter will display the Migration Parameters for Table Migration window where you can specify the Service Level Reporter set-up values for the migration process as shown in Figure 6.
32
Figure 6. SLR Parameter for Migration
When you have entered the information in the fields of the Migration Parameters for Table Migration window for the Service Level Reporter system being migrated, then press Enter. You will return to the Migration window shown in Figure 5. Select 2. Copy SLR V3 data to predefined tables from the Migration window shown in Figure 5 on page 32 and press Enter. A list of Service Level Reporter tables, and the associated Performance Reporter tables as shown in Figure 7, is displayed. Appendix B, Predefined SLR Tables to PR Tables Cross Reference on page 181 gives a complete list of the Service Level Reporter predefined tables and Performance Reporter tables where the data will be migrated.
Figure 7. Cross Reference of Predefined SLR vs PR Tables
Migrating Data from Predefined SLR Tables
33
The list of tables, as shown in Figure 7, is generated from the Performance Reporter system table DRLMIGRATION (Figure 109 on page 141). This table contains all the information necessary for the migration: Service Level Reporter Summary table(s) for each Performance Reporter data table SDRLDEFS member(s) to be used to unload the data from Service Level Reporter table(s) SDRLDEFS member(s) used to SELECT and INSERT data in the Performance Reporter data table.
Note
The list of Performance Reporter tables shown on the Predefined Tables window is not dependent on which components have been installed or what data is available to migrate in Service Level Reporter. This means that the Performance Reporter component that contains the target tables has to be installed before starting the migration process. Appendix B.1, SLR to PR Cross Reference on page 181 contains a cross reference of Service Level Reporter to Performance Reporter tables and components that you can use to see what components you need to have installed before performing your migration. Appendix A, The Key to Predefined Migration - DLRMIGRATION on page 137 contains a detailed listing of the information contained in the DRLMIGRATION system table. Select a table or tables for migration from the list provided in the Predefined Tables window shown in Figure 7 on page 33. When you have selected the predefined tables to be migrated by placing a character to the left of each table name, then press Enter. The Performance Reporter dialog will generate a JCL stream to perform the migration for you. The stages (or job steps) involved in the migration of predefined Service Level Reporter data to Performance Reporter are shown in Figure 8. These steps are: Unload the data from appropriate SLR table(s) in an IXF format file. Import the unloaded data into temporary tables within Performance Reporter (using, or not using, QMF). Select a subset of data from the temporary table and insert into appropriate Performance Reporter table.
34
Temporary Table SELECT AND INSERT
SLR Summary Table
IXF unloaded File
QMF Import
PR Table
Figure 8. SLR Data Migration
Note
In some cases, monthly Service Level Reporter data is copied to weekly Performance Reporter tables, or weekly data is summarized in monthly tables. Both these cases give incorrect data but allow you to see the long trends. Sometimes the Service Level Reporter key columns or total patterns are unavailable to the Performance Reporter tables. Performance Reporter inserts an asterisk (*) in the Performance Reporter column to indicate this situation. If a key column has a missing value in Service Level Reporter (usually an error situation), Performance Reporter replaces it with a hyphen (-). Rows where timekeys are missing are skipped.
3.1 Example of Data Migration

As an example of performing a migration of predefined Service Level Reporter data to Performance Reporter, the Service Level Reporter table WORKLOAD to the Performance Reporter table MVS_WORKLOAD_M will be described in this section using the QMF facility.
35
Note
In this example, the QMF facility is used. It is not a requirement to use QMF, and if your installation does not have QMF available, then Performance Reporter creates a similar job for the migration. The only difference is that there is no reference to the QMF libraries, and the migration process is done by DRLEMIGQ EXEC instead of DRLEMIGR EXEC used with QMF facility. The Performance Reporter migration utility that creates the job stream checks the value of the keyword qmfuse= in DRLEINI1 to determine if QMF is being used. If qmfuse ="YES", then the job stream will use QMF. If qmfuse="NO", then the non QMF job stream will be gererated. 1. Verify and set the Service Level Reporter libraries for the migration utility as described in Figure 6 on page 33. 2. From the Migration window select 2. Copy SLRV3 data to predefined tables as showed in Figure 9 and press Enter.
Figure 9. Migration Panel
3. From the list of Service Level Reporter tables shown on the Predefined Tables window shown in Figure 10 on page 37 select the table you wish to migrate. Scroll down the list until the Service Level Reporter WORKLOAD table is displayed and enter a non-blank character (in this example, a slash) next to the table name, as shown in Figure 10, to select the table for migration. When the table has been selected, press Enter.
36
Figure 10. Migration Table List
4. The Performance Reporter migration dialog will generate the migration JCL stream. The JCL shown in Figure 11 on page 38 was generated for the Service Level Reporter WORKLOAD table in this example:
37
//TI235REG JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //********************************************************************* //* //* MIGRATE TABLES: //* //* FROM: WORKLOAD //* TO: MVS_WORKLOAD_M //* //********************************************************************* //DRERUN PROC //* //********************************************************************* //* DELETE WORK TABLE //********************************************************************* //DELETE EXEC PGM=IDCAMS,REGION=2M //SYSPRINT DD SYSOUT=* //* //********************************************************************* //* UNLOAD SLR V3R3 TABLE IN IXF FORMAT //********************************************************************* //DRERUN EXEC PGM=&PGMCALL,REGION=6500K //STEPLIB DD DISP=SHR,DSN=TI3101.LINKLIB // DD DISP=SHR,DSN=SLR.V3R3M1.LINKLIB //LOAD DD DISP=SHR,DSN=TI3101.SLRSAMP // DD DISP=SHR,DSN=SLR.V3R3M1.SLRSAMP //SORTLIB DD DISP=SHR,DSN=SYS1.SORTLIB //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(10,5),,CONTIG) //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(10,5),,CONTIG) //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(10,5),,CONTIG) //IXFILE DD DISP=(NEW,CATLG,DELETE), // DSN=&UNLOAD.TABLE, // DCB=(RECFM=VB,LRECL=6000,BLKSIZE=12004), // SPACE=(CYL,(20,5)),UNIT=SYSDA //MAINFILE DD DISP=SHR,DSN=SLR.V3R3M0.SYSTEMDB //SYSOUT DD DUMMY //SYSTSPRT DD SYSOUT=* //OUT DD SYSOUT=* //DUMP DD SYSOUT=* // PEND //* //********************************************************************* //* INSERT UNLOADED DATA INTO DB2 TABLE //********************************************************************* //EPDMMIGR PROC //EPDMMIGR EXEC PGM=IKJEFT01,DYNAMNBR=25,REGION=6M //STEPLIB DD DISP=SHR,DSN=TME10PRF.SDRLLOAD // DD DISP=SHR,DSN=QMF330C.DSQLOAD // DD DISP=SHR,DSN=DB2V510.SDSNLOAD //SYSPROC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQCLSTE // DD DISP=SHR,DSN=QMF330C.DSQEXECE //SYSEXEC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQEXECE //DRLOUT DD SYSOUT=* //*
Figure 11. Migration Sample Job (Part 1 of 3)
38
//*********************** //* DEFINITION LIBRARIES //* YOU MAY WANT TO MIGRATE FROM YOUR LOCAL DEFINITION LIBRARY //* CHANGE THE DRLDEFS1 DD TO YOUR LOCAL LIBRARY //*********************** //DRLDEFS1 DD DISP=SHR,DSN=TME10PRF.SDRLDEFS //DRLDEFS2 DD DISP=SHR,DSN=TME10PRF.SDRLDEFS //* //* //***************** //* PRINTED OUTPUT //***************** //DSQPRINT DD SYSOUT=Q,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330) //* //***************** //* GDDM LIBRARIES //***************** //ADMGGMAP DD DISP=SHR,DSN=QMF330C.DSQMAPE //ADMCFORM DD DISP=SHR,DSN=QMF330C.DSQCHART // DD DISP=SHR,DSN=TME10PRF.SDRLFENU //ADMGDF DD DISP=SHR,DSN=TME10PRU.LOCAL.CHARTS //DSQUCFRM DD DISP=SHR,DSN=TME10PRU.LOCAL.ADMCFORM //* //* //***************** //* QMF LIBRARIES //***************** //DSQDEBUG DD DUMMY //DSQUDUMP DD DUMMY //DSQPNLE DD DISP=SHR,DSN=QMF330C.DSQPNLE //DSQSPILL DD DSN=&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA, // SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096) //DSQEDIT DD DSN=&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE), // DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029) //* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* // PEND //* //********************************************************************* //********************************************************************* //* UNLOAD SLR V3R3 TABLE(S): //********************************************************************* //* YOU MAY WANT TO MIGRATE FROM YOUR LOCAL DEFINITION LIBRARY //* CHANGE THE DSN IN THE DRERUN.IN DD //********************************************************************* /
39
//********************************************************************* //* //* WORKLOAD //* //DRLW07A0 EXEC DRERUN, // UNLOAD=TI3101A.DRLW07A0.S6., // PGMCALL=DREMNBEB,PARM=UPDATE //DELETE.SYSIN DD * DELETE TI3101A.DRLW07A0.S6.TABLE NONVSAM SET MAXCC = 0 //* //DRERUN.IN DD DISP=SHR,DSN=TME10PRF.SDRLDEFS(DRLW07A0) //* //********************************************************************* //* INSERT UNLOADED DATA INTO DB2 TABLE //********************************************************************* //* //* FROM: WORKLOAD //* TO: MVS_WORKLOAD_M //* //********************************************************************* //* RELOAD TI3101A.DRLW07A0.S6.TABLE //********************************************************************* //DRLWMVWO EXEC EPDMMIGR //SYSTSIN DD * EXECUTIL SEARCHDD(YES) %DRLEMIGR DB2C DRLDB DRLSG DRL 1 TI3101A.DRLW07A0.S6.TABLE DRLWMVWO WORKLOAD MVS_WORKLOAD_M //* //***************************************************************** //* DELETE UNLOADED TABLE(S) //***************************************************************** //CLEAR EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE TI3101A.DRLW07A0.S6.TABLE NONVSAM SET MAXCC = 0 //*
The migration job stream generated by the Performance Reporter migration dialog, as shown in Figure 11 on page 38, is a three step job comprising of the following in-line procedures: The first step (proc DRERUN) performs a delete of the old IXF file with the name of TI3101A.DRLW07A0.S6.TABLE (if it exists). It then produces a report driven by the DRLW07A0 member in the hlq.SDRLDEFS. Figure 14 on page 41 and Figure 15 on page 42 show the control statements in DRLW07A0. The second step (proc EPDMMIGR) creates a temporary table using QMF. This step then loads the MVS_WORKLOAD_M table using the SQL
40
statements defined in the member DRLWMVWO of hlq.SDRLDEFS. Figure 16 on page 43 shows the SQL statements from DRLWMVWO. The last step, CLEAR, deletes the IXF file used in the previous two steps.
/*********************************************************************/ /* */ /* Name: DRLW07A0 */ /* */ /* Status: Performance Reporter 1.1.0 */ /* */ /* Function: UNLOAD statements for DRLWMVWO */ /* */ /* Change activity: */ /* 00 1993-03-31 KFN Created */ /* */ /*********************************************************************/ /* */ /* Table: Keys: */ /* WORKLOAD YEAR MONTH DAY HOUR SYSID PGT TYPE */ /* */ /*********************************************************************/ /* */ /* SLR Columns EPDM Columns */ /* Key */ /* YEAR, MONTH DATE */ /* SYSID MVS_SYSTEM_ID */ /* PGT PERF_GROUP_TYPE */ /* TYPE WORKLOAD_TYPE */ /* Data */ /* ACTTIME TRAN_ELAPSED_TIME */ /* IOFACT IO_COUNT */ /* MAXCPUSU Not migrated */ /* MAXSWAP Not migrated */ /* MEASTIME Not migrated */ /* NROWS Not migrated */ /* NSERV SERVICE_UNITS_TOT */ /* NSWAPS SWAP_SEQUENCES */ /* NTRANS TRANSACTIONS */ /* SRBFACT Not migrated */ /* TCBFACT Not migrated */ /* TOTFRAMES Not migrated */ /* TOTPAGEIN PAGEINS (not SMF72HIN) */ /* TOTTIME MEASURED_SEC */ /
Figure 14. DRLW07A0 Member in hlq.SDRLDEFS (Part 1 of 2)
41
* Virtual */ /* AVGCPU Not migrated */ /* AVGFRAMES Not migrated */ /* AVGSERV SERVICE_UNITS_TOT/TRANSACTIONS */ /* CPUPCT Not migrated */ /* RESPTIME Not migrated */ /* SRBTIME SRB_SECONDS*3600 */ /* SWAPRATE Not migrated */ /* TCBTIME TCB_SECONDS*3600 */ /* TOT_CPUSU Not migrated */ /* TOT_EXCP Not migrated */ /* TOTCPU Not migrated */ /* TRANSRATE Not migrated */ /* TYPE_CPUSU Not migrated */ /* TYPE_EXCP Not migrated */ /* TYPE_SU Not migrated */ /*********************************************************************/ REPORT WORKLOAD SELECT COLUMNS(YEAR + MONTH + SYSID + PGT + TYPE + NTRANS + TOTTIME + IOFACT + ACTTIME + NSERV + NSWAPS + TOTPAGEIN + TCBTIME + SRBTIME + MAXCPUSU + AVGSERV) SELECT ROWS(YEAR ^= TOT AND + YEAR ^= AND + MONTH ^= TOT AND + MONTH ^= AND + SYSID ^= TOT AND + PGT ^= TOT AND + TYPE ^= TOT) UNLOAD IXF FILE(IXFILE) ENDREP
Figure 15. DRLW07A0 Member in hlq.SDRLDEFS (Part 2 of 2)
42
--*********************************************************************/ -*/ -- Name: DRLWMVWO */ -*/ -- Status: Performance Reporter 1.1.0 */ -*/ -- Function: Migrate SLR V3R3 table WORKLOAD (DREG07A0) */ -to EPDM DB2 table MVS_WORKLOAD_M */ -*/ -- Change activity: */ -00 1993-03-31 KFN Created */ -01 1993-06-03 VALUE(SYSID,-) added to handel missing */ -SYSID. APAR PN41799 */ -02 1995-09-13 JCS Prefix for DRLTEMP added EPDM120 */ -*/ --*********************************************************************/ -*/ -- See DRLTMVWO: MVS_WORKLOAD_M */ -*/ -- EPDM SLR V3R3 */ -- --------------------------*/ -- DATE YEAR,MONTH */ -- PERIOD_NAME * */ -- MVS_SYSTEM_ID SYSID */ -- WORKLOAD_TYPE TYPE */ -- PERF_GROUP_NO * */ -- PERF_GROUP_PERIOD * */ -- PERF_GROUP_TYPE PGT */ -- SUBSYSTEM_ID * */ -*/ -- CAPACITY_CPU_SU missing */ -- MEASURED_SEC TOTTIME */ -- TRANSACTIONS NTRANS */ -- TRAN_ACTIVE_SEC missing */ -- TRAN_ELAPSED_SEC ACTTIME */ -- TRAN_RESIDENCY_SEC missing */ -- SERVICE_UNITS_CPU missing */ -- SERVICE_UNITS_SRB missing */ -- SERVICE_UNITS_MS missing */ -- SERVICE_UNITS_IO missing */ -- SERVICE_UNITS_TOT NSERV */ -- TCB_SECONDS TCBTIME*3600 */ -- SRB_SECONDS SRBTIME*3600 */ -- IO_COUNT IOFACT */ -- PAGEINS TOTPAGEIN (+SMF72HIN) */ -- SWAP_SEQUENCES NSWAPS */ -- TOT_FRAME_SECONDS missing */ -- ES_FRAME_SECONDS missing */ -- CS_FRAME_SECONDS missing */ -*/ --*********************************************************************/
Figure 16. DRLWMVWO Member of hlq.SDRLDEFS (Part 1 of 2)
43
INSERT INTO &PREFIX.MVS_WORKLOAD_M (DATE, PERIOD_NAME, MVS_SYSTEM_ID, WORKLOAD_TYPE, PERF_GROUP_NO, PERF_GROUP_PERIOD, PERF_GROUP_TYPE, SUBSYSTEM_ID, MEASURED_SEC, TRANSACTIONS, TRAN_ELAPSED_SEC, IO_COUNT, PAGEINS, SERVICE_UNITS_TOT, SWAP_SEQUENCES, TCB_SECONDS, SRB_SECONDS) SELECT SUBSTR(DIGITS(YEAR), 2, 4)!!-!! SUBSTR(DIGITS(MONTH), 4, 2)!!-!!01, *, -PERIOD_NAME, VALUE(SYSID,-), -MVS_SYSTEM_ID, VALUE(TYPE,-), -WORKLOAD_TYPE, *, -PERF_GROUP_NO, *, -PERF_GROUP_PERIOD, VALUE(PGT,-), -PERF_GROUP_TYPE, *, -SUBSYSTEM_ID TOTTIME, -MEASURED_SEC NTRANS, -TRANSACTIONS ACTTIME, -TRAN_ELAPSED_SEC IOFACT, -IO_COUNT TOTPAGEIN, -PAGEINS NSERV, -SERVICE_UNITS_TOT NSWAPS, -SWAP_SEQUENCES TCBTIME*36E2, -TCB_SECONDS SRBTIME*36E2 -SRB_SECONDS FROM &PREFIX.DRLTEMP
PN41799 PN41799
--EPDM120
Figure 17. DRLWMVWO Member of hlq.SDRLDEFS (Part 2 of 2)
5. Before submitting the migration job stream for execution, you should review the JCL to verify the data set names are correct. You can submit the job for execution by typing Submit on the ISPF edit panel and pressing Enter. The job should finish with a completion code of zero (CC=00). 6. You can check the results of the migration using SPUFI or QMF to look at the contents of the MVS_WORKLOAD_M table. The SQL statement to display the contents of the MVS_WORKLOAD_M table using SPUFI is: SELECT * FROM DRL.MVS_WORKLOAD_M ;
44
This migration of the Service Level Reporter WORKLOAD table to the Performance Reporter MVS_WORKLOAD_M table is now complete. All of the predefined table migrations should be this straight forward and easy to perform.
3.2 Deviation from Default Data Migration

You may want to migrate some predefined tables at a different level of data selection in Service Level Reporter to a different level of DB2 table in Performance Reporter than is provided by the migration utility. For example, suppose you want to migrate the WORKLOAD Service Level Reporter table to the MVS_WORKLOAD_D with the data at the daily level instead of at the monthly level, as will be done by the default Performance Reporter migration utility. We have already seen that the migration of WORKLOAD table is controlled by two members located in hlq.SDRLDEFS: DRLW07A0 to unload the data from WORKLOAD table into an IXF file. DRLWMVWO to load the IXF file into the related Performance Reporter table. You need to copy the above members from hlq.SDRLDEFS to hlq.LOCAL.DEFS in order to modify them. After the modification, these members should look like Figure 21 on page 49 for DRLW07A0 and Figure 23 on page 51 for DRLWMVWO where the modifications have been indicated by -- Added or <===. You can compare these two members with their original versions in Figure 14 on page 41 for DRLW07A0 and Figure 16 on page 43 for DRLWMVWO. 1. Select 2. Copy SLR V3 data to predefined tables on the Migration Panel, as in Figure 9 on page 36, and then select WORKLOAD from the Performance Reporter tables listed on the Predefined Tables window as shown in Figure 10 on page 37, and press Enter. 2. Performance Reporter dialog will produce the migration sample job as shown in Figure 11 on page 38. 3. You need to modify this sample job by inserting the references to the hlq.LOCAL.DEFS and by altering the name of the target Performance Reporter table. After modification, the job should look like Figure 18 on page 46 where the modifications have been indicated by <===. 4. Verify and submit the job. The job should end with a completion code of zero (CC=00). 45
5. You can verify the contents of the target Performance Reporter MVS_WORKLOAD_D table as described in Chapter 3.1, Example of Data Migration on page 35.
//TI3101B1 JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //* //* //********************************************************************* //* //* MIGRATE TABLES: //* //* FROM: WORKLOAD <===== Changed Table //* TO: MVS_WORKLOAD_D //* //********************************************************************* //DRERUN PROC //* //********************************************************************* //* DELETE WORK TABLE //********************************************************************* //DELETE EXEC PGM=IDCAMS,REGION=2M //SYSPRINT DD SYSOUT=* //* //********************************************************************* //* UNLOAD SLR V3R3 TABLE IN IXF FORMAT //********************************************************************* //DRERUN EXEC PGM=&PGMCALL,REGION=6500K //STEPLIB DD DISP=SHR,DSN=SLR.V3R3M1.LINKLIB //LOAD DD DISP=SHR,DSN=TI3101.SLRSAMP // DD DISP=SHR,DSN=SLR.V3R3M1.SLRSAMP //SORTLIB DD DISP=SHR,DSN=SYS1.SORTLIB //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(10,5),,CONTIG) //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(10,5),,CONTIG) //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(10,5),,CONTIG) //IXFILE DD DISP=(NEW,CATLG,DELETE), // DSN=&UNLOAD.TABLE, // DCB=(RECFM=VB,LRECL=6000,BLKSIZE=12004), // SPACE=(CYL,(20,5)),UNIT=SYSDA //MAINFILE DD DISP=SHR,DSN=SLR.V3R3M1.SYSTEMDB //SYSOUT DD DUMMY //SYSTSPRT DD SYSOUT=* //OUT DD SYSOUT=* //DUMP DD SYSOUT=* // PEND //* //******************************************************************
Figure 18. Modified Migration Sample Job (Part 1 of 3)
46
//********************************************************************* //* INSERT UNLOADED DATA INTO DB2 TABLE //********************************************************************* //EPDMMIGR PROC //EPDMMIGR EXEC PGM=IKJEFT01,DYNAMNBR=25,REGION=6M //STEPLIB DD DISP=SHR,DSN=TME10PRF.SDRLLOAD // DD DISP=SHR,DSN=QMF330C.DSQLOAD // DD DISP=SHR,DSN=DB2V510.SDSNLOAD //SYSPROC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQCLSTE // DD DISP=SHR,DSN=QMF330C.DSQEXECE //SYSEXEC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQEXECE //DRLOUT DD SYSOUT=* //* //*********************** //* DEFINITION LIBRARIES //* YOU MAY WANT TO MIGRATE FROM YOUR LOCAL DEFINITION LIBRARY //* CHANGE THE DRLDEFS1 DD TO YOUR LOCAL LIBRARY //*********************** <===== Changed //DRLDEFS1 DD DISP=SHR,DSN=TME10PRU.LOCAL.DEFS //DRLDEFS2 DD DISP=SHR,DSN=TME10PRF.SDRLDEFS //* //* //***************** //* PRINTED OUTPUT //***************** //DSQPRINT DD SYSOUT=Q,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330) //* //***************** //* GDDM LIBRARIES //***************** //ADMGGMAP DD DISP=SHR,DSN=QMF330C.DSQMAPE //ADMCFORM DD DISP=SHR,DSN=QMF330C.DSQCHART // DD DISP=SHR,DSN=TME10PRF.SDRLFENU //ADMGDF DD DISP=SHR,DSN=TME10PRU.LOCAL.CHARTS //DSQUCFRM DD DISP=SHR,DSN=TME10PRU.LOCAL.ADMCFORM //* //* //***************** //* QMF LIBRARIES //***************** //DSQDEBUG DD DUMMY //DSQUDUMP DD DUMMY //DSQPNLE DD DISP=SHR,DSN=QMF330C.DSQPNLE //DSQSPILL DD DSN=&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA, // SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096) //DSQEDIT DD DSN=&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE), // DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029) //* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* // PEND //*
47
//********************************************************************* //* UNLOAD SLR V3R3 TABLE(S): //********************************************************************* //* YOU MAY WANT TO MIGRATE FROM YOUR LOCAL DEFINITION LIBRARY //* CHANGE THE DSN IN THE DRERUN.IN DD //********************************************************************* //* //* WORKLOAD //* //DRLW07A0 EXEC DRERUN, // UNLOAD=TI3101B.DRLW07A0.S6., // PGMCALL=DREMNBEB,PARM=UPDATE //DELETE.SYSIN DD * DELETE TI3101B.DRLW07A0.S6.TABLE NONVSAM SET MAXCC = 0 //* //DRERUN.IN DD DISP=SHR,DSN=TME10PRU.LOCAL.DEFS(DRLW07A0) <=== Changed //* //********************************************************************* //* INSERT UNLOADED DATA INTO DB2 TABLE //********************************************************************* //* //* FROM: WORKLOAD //* TO: MVS_WORKLOAD_D <=====Changed PR Table //* //********************************************************************* //* RELOAD TI3101B.DRLW07A0.S6.TABLE //********************************************************************* //DRLWMVWO EXEC EPDMMIGR //SYSTSIN DD * EXECUTIL SEARCHDD(YES) %DRLEMIGR DB2C DRLDB DRLSG DRL 1 TI3101B.DRLW07A0.S6.TABLE DRLWMVWO WORKLOAD MVS_WORKLOAD_D <==== Changed //* //***************************************************************** //* DELETE UNLOADED TABLE(S) //***************************************************************** //CLEAR EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE TI3101B.DRLW07A0.S6.TABLE NONVSAM SET MAXCC = 0 //*
48
/*********************************************************************/ /* */ /* Licensed Materials - Property of IBM */ /* */ /* 5695-101 (C) Copyright IBM Corporation 1993. */ /* See Copyright Instructions. */ /* */ /*********************************************************************/ /* */ /* Name: DRLW07A0 */ /* */ /* Status: Performance Reporter 1.1.0 */ /* */ /* Function: UNLOAD statements for DRLWMVWO */ /* */ /* Change activity: */ /* 00 1993-03-31 KFN Created */ /* 01 1998-12-04 ITSO Modified for migration of daily data */ /* */ /*********************************************************************/ /* */ /* Table: Keys: */ /* WORKLOAD YEAR MONTH DAY HOUR SYSID PGT TYPE */ /* */ /*********************************************************************/ /* */ /* SLR Columns EPDM Columns */ /* Key */ /* YEAR, MONTH, DAY DATE */ /* SYSID MVS_SYSTEM_ID */ /* PGT PERF_GROUP_TYPE */ /* TYPE WORKLOAD_TYPE */ /* Data */ /* ACTTIME TRAN_ELAPSED_TIME */ /* IOFACT IO_COUNT */ /* MAXCPUSU Not migrated */ /* MAXSWAP Not migrated */ /* MEASTIME Not migrated */ /* NROWS Not migrated */ /* NSERV SERVICE_UNITS_TOT */ /* NSWAPS SWAP_SEQUENCES */ /* NTRANS TRANSACTIONS */ /* SRBFACT Not migrated */ /* TCBFACT Not migrated */ /* TOTFRAMES Not migrated */ /* TOTPAGEIN PAGEINS (not SMF72HIN) */ /* TOTTIME MEASURED_SEC */
Figure 21. Modified DRLW07A0 Member in hlq.LOCAL.DEFS (Part 1 of 2)
49
/* Virtual */ /* AVGCPU Not migrated */ /* AVGFRAMES Not migrated */ /* AVGSERV SERVICE_UNITS_TOT/TRANSACTIONS */ /* CPUPCT Not migrated */ /* RESPTIME Not migrated */ /* SRBTIME SRB_SECONDS*3600 */ /* SWAPRATE Not migrated */ /* TCBTIME TCB_SECONDS*3600 */ /* TOT_CPUSU Not migrated */ /* TOT_EXCP Not migrated */ /* TOTCPU Not migrated */ /* TRANSRATE Not migrated */ /* TYPE_CPUSU Not migrated */ /* TYPE_EXCP Not migrated */ /* TYPE_SU Not migrated */ /*********************************************************************/ REPORT WORKLOAD SELECT COLUMNS(YEAR MONTH DAY SYSID PGT TYPE NTRANS TOTTIME IOFACT ACTTIME NSERV NSWAPS TOTPAGEIN TCBTIME SRBTIME MAXCPUSU AVGSERV) SELECT ROWS(YEAR = TOT AND YEAR = '' AND MONTH = TOT AND MONTH = '' AND DAY = TOT AND DAY = '' AND SYSID = TOT AND PGT = TOT AND TYPE = TOT) UNLOAD IXF FILE(IXFILE) ENDREP
+ + + + + + + + + + + + + + + + + + + + + + + +
--<=== Added --<=== Added
Figure 22. Modified DRLW07A0 Member in hlq.LOCAL.DEFS (Part 2 of 2)
50
--*********************************************************************/ -*/ -- Licensed Materials - Property of IBM */ -*/ -- 5695-101 (C) Copyright IBM Corporation 1993. */ -- See Copyright Instructions. */ -*/ --*********************************************************************/ -*/ -- Name: DRLWMVWO */ -*/ -- Status: Performance Reporter 1.1.0 */ -*/ -- Function: Migrate SLR V3R3 table WORKLOAD (DREG07A0) */ -to EPDM DB2 table MVS_WORKLOAD_D */ -*/ -- Change activity: */ -00 1993-03-31 KFN Created */ -01 1993-06-03 VALUE(SYSID,-) added to handel missing */ -SYSID. APAR PN41799 */ -02 1995-09-13 JCS Prefix for DRLTEMP added EPDM120 */ -*/ -03 1998-12-04 ITSO Modified for migration of daily data */ --*********************************************************************/ -*/ -- See DRLTMVWO: MVS_WORKLOAD_M */ -*/ -- EPDM SLR V3R3 */ -- --------------------------*/ -- DATE YEAR,MONTH,DAY */ -- PERIOD_NAME * */ -- MVS_SYSTEM_ID SYSID */ -- WORKLOAD_TYPE TYPE */ -- PERF_GROUP_NO * */ -- PERF_GROUP_PERIOD * */ -- PERF_GROUP_TYPE PGT */ -- SUBSYSTEM_ID * */ -*/ -- CAPACITY_CPU_SU missing */ -- MEASURED_SEC TOTTIME */ -- TRANSACTIONS NTRANS */ -- TRAN_ACTIVE_SEC missing */ -- TRAN_ELAPSED_SEC ACTTIME */ -- TRAN_RESIDENCY_SEC missing */ -- SERVICE_UNITS_CPU missing */ -- SERVICE_UNITS_SRB missing */ -- SERVICE_UNITS_MS missing */ -- SERVICE_UNITS_IO missing */ -- SERVICE_UNITS_TOT NSERV */ -- TCB_SECONDS TCBTIME*3600 */ -- SRB_SECONDS SRBTIME*3600 */ -- IO_COUNT IOFACT */ -- PAGEINS TOTPAGEIN (+SMF72HIN) */ -- SWAP_SEQUENCES NSWAPS */ -- TOT_FRAME_SECONDS missing */ -- ES_FRAME_SECONDS missing */ -- CS_FRAME_SECONDS missing */ -*/
Figure 23. Modified DRLWMVWO Member in hlq.LOCAL.DEFS (Part 1 of 2)
51
--*********************************************************************/ INSERT INTO &PREFIX.MVS_WORKLOAD_D -- <==== Altered (DATE, PERIOD_NAME, MVS_SYSTEM_ID, WORKLOAD_TYPE, PERF_GROUP_NO, PERF_GROUP_PERIOD, PERF_GROUP_TYPE, SUBSYSTEM_ID, MEASURED_SEC, TRANSACTIONS, TRAN_ELAPSED_SEC, IO_COUNT, PAGEINS, SERVICE_UNITS_TOT, SWAP_SEQUENCES, TCB_SECONDS, SRB_SECONDS) SELECT SUBSTR(DIGITS(YEAR), 2, 4)||-|| SUBSTR(DIGITS(MONTH), 4, 2)||-|| -- <======= Altered SUBSTR(DIGITS(DAY), 4, 2), -- <======= Added *, -PERIOD_NAME, VALUE(SYSID,-), -MVS_SYSTEM_ID, PN41799 VALUE(TYPE,-), -WORKLOAD_TYPE, PN41799 *, -PERF_GROUP_NO, *, -PERF_GROUP_PERIOD, VALUE(PGT,-), -PERF_GROUP_TYPE, *, -SUBSYSTEM_ID TOTTIME, -MEASURED_SEC NTRANS, -TRANSACTIONS ACTTIME, -TRAN_ELAPSED_SEC IOFACT, -IO_COUNT TOTPAGEIN, -PAGEINS NSERV, -SERVICE_UNITS_TOT NSWAPS, -SWAP_SEQUENCES TCBTIME*36E2, -TCB_SECONDS SRBTIME*36E2 -SRB_SECONDS FROM &PREFIX.DRLTEMP --EPDM120
Figure 24. Modified DRLWMVWO Member in hlq.LOCAL.DEFS (Part 2 of 2)
3.3 Other Modifications to the Standard Migration

There may be other requirements to alter the standard migration. For example, a Service Level Reporter table may have been amended but is still valid input to the appropriate Performance Reporter table. The following examples show the process involved in amending the standard migration to move data from an altered table.
52
3.3.1 Addition or Modification of Computed Columns

The COMPCOL function provided by Service Level Reporter is either part of the update definitions or coded within the supplied reports of Performance Reporter. It is, therefore, very easy to carry out the same function of any COMPCOLs that you have added or modified. An example is shown in Figure 25 where the COMPCOL AVGRESP in Service Level Reporter has been resolved in a Performance Reporter report using SQL.
SLR COMPCOL AVGRESP, VALUE=AVG(TRANS_ELAPSED,NTRANS) ------------------------------------------------------------PR SELECT ......, SUM(TRANS_ELAPSED/SUM(NTARNS)

Figure 25. Providing COMPCOL Function within a PR Report
3.3.2 Addition or Modification of Data Columns

Data columns may have been added to Service Level Reporter tables for two reasons: 1. To hold data in a summary table that is mapped in the parent log table 2. To hold newly mapped data How to handle newly mapped data is covered in Chapter 4.1, The A.L.L. Table Migration on page 57. In order to migrate data from the added column, you must first identify an equivalent column in the target Performance Reporter table. Normally, you will be able to identify an equivalent column, as there is a larger set of variables provided by Performance Reporter. If there is not a suitable target, then the steps outlined in Chapter 4.1, The A.L.L. Table Migration on page 57 should be followed. The commands necessary to perform data migration are held in members within the hlq.SDRLDEFS data set. Use the information contained in DRLMIGRATION to identify which members need to be altered. The SQL to query the DRLMIGRATION table is given in Appendix A.1, Viewing DLRMIGRATION on page 137).
53
For example, if the CICSTRANSUM table had been modified to include a system id (SYSID), then you need to create copies of DRLW0500 and DRLWC101 in the hlq.LOCAL.DEFS dataset. DRLW0500 contains the unload command to move the data out of Service Level Reporter and into a temporary file. This command must be modified to include the added data column(s). In this example, the modified DRLW0500 with the sysid added is shown in Figure 26. The modified statements are identified with "/* added this column".
Figure 26. Extract from Modified DRLW0500
DRLWC101 contains the SQL insert statements necessary to move the data from the file into a temporary table. The statements will need updating to show the added column(s). In this example the modified DRLWC101 with the asterisk changed to the Performance Reporter column name MVS_SYSTEM_ID is shown in Figure 27 on page 55. The modified statement is identified with " -- changed from * ".
54
Figure 27. Extract from Modified DRLWC101
You can now run the migration dialog as if it were a standard data migration. Any supplied reports based on the amended table may need altering.
Note
The same procedure, as described above for normal data columns, applies for moving data from key columns that may have been added to Service Level Reporter tables.
3.3.3 Migrating User-Defined Tables

If a predefined Service Level Reporter table has been modified significantly, or tables have been created to support new log sources, then these definitions need to be transferred to Performance Reporter. The Performance Reporter migration dialog contains the necessary tools to interpret Service Level Reporter table macros and create Performance Reporter definitions. The migration tool converts parameter tables to Lookup tables, log tables to record definitions, and summary tables to Performance Reporter tables and update definitions. Two scenarios exist for the migration of user-defined tables and data: 1. Migration based around Service Level Reporter log tables 2. Migration based on A.L.L log tables 3.3.3.1 Migration of Modified SLR Log Based Tables You may have taken a predefined Service Level Reporter table and used it as a model for building your own table. Because the number of modifications you can make to a Service Level Reporter log table are limited to the addition
55
of columns, rather than the modification of existing data, the migration process is straight forward. First you need to identify the relevant Performance Reporter definitions involved in replacing the Service Level Reporter based tables. Table 4 on page 56 shows an example where the JOBSTAT table has been researched to show where the column JOBNAME is found in Performance Reporter definitions.
Table 4. Comparison between SLR Tables and PR Definitions
SLR Table Log SLR Summary Table JOBSTAT PR Record Definition PR Table Definition PR Update Definition
JOBLOG
SMF_025 SMF_026 SMF_006
MVS_ADDRSPACE_T, MVS_ADDRSPACE_D, MVS_ADDRSPACE_M
MVSADDR_25_T, MVSADDR_26_T, MVSADDR_30_4_T, MVSADDR_30_5_A_T, MVSADDR_30_5_E_T, MVSADDR_30_5_T, MVSADDR_6_T
The modifications made for the Service Level Reporter table should now be made for the relevant Performance Reporter object. If, for example, JOBSTAT had been modified to change the column JOBNAME from data to key, then the following changes would have to be made to the Performance Reporter objects: The table definition MVS_ADDRSPACE_T is correct. JOBNAME is already a key column. (This table, along with the associated record definitions, performs the same function as JOBLOG) Modify table definitions MVS_ADDRSPACE_D and MVS_ADDRSPACE_M, to add a new key column JOBNAME. Delete and recreate the table indexes for MVS_ADDRSPACE_D and MVS_ADDRSPACE_M. to include JOBNAME. Modify update definitions MVSADDR_T_D and MVSADDR_D_M to add the new column JOBNAME. 3.3.3.2 Migration of User-Defined A.L.L Based Tables This process is described in detail in Chapter 4, Migrating User-Defined A.L.L Based Tables and Data on page 57.
56
Chapter 4. Migrating User-Defined A.L.L Based Tables and Data

This chapter provides details on how to migrate user defined Service Level Reporter tables (adaptable log layout or A.L.L.) to Performance Reporter. An example will be used to show you the step by step process we went through to migrate our user defined tables and data. For the purpose of this exercise, we created a Service Level Reporter user table with a low time of hourly data. The migration routine inspects the Service Level Reporter table definition, the Service Level Reporter log definition, and specified parameter table definitions and uses this information to create Performance Reporter definitions. These definitions will include a Performance Reporter log definition, a Performance Reporter record definition, a Performance Reporter table definition and table, a Performance Reporter Lookup table and definition (if one was specified), a unique index definition for the Performance Reporter table, and a Performance Reporter update definition. The migration routine copies the lowest time pattern data from the Service Level Reporter summary table into an IXF type file. All the Performance Reporter statements that were used to do this migration are saved in a member in your Performance Reporter local definitions library. The member is named MIGExxxx, where the xxxx is the unique number of your Service Level Reporter summary table member. For example, if your summary table member is named DREG3008, then your migration member name will be MIGE3008. This job will then insert the data from the IXF file into the Performance Reporter table it has just created. The Performance Reporter Table it creates will have the same name as the migrated Service Level Reporter summary table. The PR statements used for this task will also be saved in your local Performance Reporter DEFS library in a member called MIGELOAD. We suggest that you use the statements in the MIGExxxx member as the basis for actually creating your own Performance Reporter component for future data collection. An example of this process will be given later in this chapter.
4.1 The A.L.L. Table Migration

The following steps must be performed: 1. Ensure that all of your Performance Reporter dialog parameters are correct. Select 1. Dialog parameters from the System panel to display
57
and edit these parameters, as described in Chapter 3.1, Example of Data Migration on page 35. 2. Once your parameters are correctly set, you can start the migration by selecting 4. Migration from the System panel, as shown in Figure 28.
Figure 28. The System Panel
3. To enter the migration parameters select 1. Migration parameters for table migration from the Migration panel, as shown in Figure 29 on page 59. On the Migration Parameters for Table Migration panel, as shown in Figure 30 on page 60, you need to specify the data set names for all the Service Level Reporter libraries needed to perform a migration. 4. Select 3. Convert SLR V3 tables and copy data from the Migration panel to migrate user defined tables and data to Performance Reporter. On the SLR V3 Table Conversion panel, you will enter the Service Level Reporter log table, the Service Level Reporter summary table, and any related Service Level Reporter parameter table members to be migrated, as well as the Performance Reporter log name (to be created by this job) and the Performance Reporter tablespace name. In this example, we chose the name EXAMPL1H (you may choose any name you wish for the log). The Performance Reporter tablespace name points to a DB2 tablespace and must therefore already exist. We recommend that you define a new tablespace in Performance Reporter for this operation because it can be easily removed. For this example, as shown in Figure 31 on page
58
60, we used a tablespace called DRLSSAMP (in our example, we used the tablespace owned by the SAMPLE component). When youve completed entering the information into the SLR V3 Table Conversion, press Enter to create JCL to perform the migration as shown in Figure 32 on page 61.
Figure 29. The Migration Panel
Migrating User-Defined A.L.L Based Tables and Data
59
Figure 30. Migration Parameters for Table Migration
Figure 31. SLR V3 Table Conversion
60
//TI3101B1 JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //* //* //* //********************************************************************* //* //* PROCESS THE FOLLOWING TABLE(S): //* -----------------------------//* //* SOURCE/MEMBER TABLE NAME //* ---------------------//* SLR LOG TABLE : DREG3006 TESTLOG //* SLR SUMMARY TABLE : DREG3008 TESTSUM //* SLR PARAMETER TABLE(S): DREG3001 //* //***** WARNING *** WARNING *** WARNING *** WARNING *** PN53060 *** //* //* REVIEW THE EPDM DEFINITIONS CAREFULLY BEFORE SUBMITTING THE JOB. //* ESPECIALLY CHECK THE LINES MARKED WITH "--<== CHECK" COMMENT. //* ALL FUNCTIONS IN THE SLR DEFINITIONS CAN NOT BE CONVERTED TO //* A CORRESPONDING EPDM FUNCTION. //* //***** WARNING *** WARNING *** WARNING *** WARNING *** PN53060 ***
Figure 32. A.L.L. Migration Sample Job (Part 1 of 6)
61
//********************************************************************* //* //* CREATE A PDS MEMBER COPY OF EPDM DEFINITIONS INLINE //* EPDM COMMANDS. STEP 1 OF 6. //* //********************************************************************* //EPDMCOPY EXEC PGM=ICEGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD * ------------------------------------------------- DEFINE LOG EXAMPLEH ------------------------------------------------DEFINE LOG EXAMPLEH; COMMENT ON LOG EXAMPLEH IS SAMPLE DATA RECORD LOG; ------------------------------------------------- DEFINE RECORD TEST_1 ------------------------------------------------DEFINE RECORD TEST_1 IN LOG EXAMPLEH IDENTIFIED BY (SELECT_1 = 01) FIELDS ( SELECT_1 OFFSET 4 LENGTH 2 CHAR, TIMESTAMP_DATE OFFSET 7 LENGTH 6 DATE(MMDDYY), TIMESTAMP_TIME OFFSET 13 LENGTH 6 TIME(HHMMSS), SYSID OFFSET 20 LENGTH 4 CHAR, USERID OFFSET 25 LENGTH 8 CHAR, TRNS OFFSET 34 LENGTH 6 EXTERNAL INTEGER, RESP OFFSET 41 LENGTH 6 EXTERNAL INTEGER, CPU OFFSET 48 LENGTH 6 EXTERNAL INTEGER, PRNT OFFSET 55 LENGTH 6 EXTERNAL INTEGER, KBYTES OFFSET 62 LENGTH 6 EXTERNAL INTEGER); COMMENT ON RECORD TEST_1 IS SAMPLE DATA RECORD LOG; ------------------------------------------------- DEFINE LOOKUP TABLE SAMPARM ------------------------------------------------SQL CREATE TABLE &PREFIX.SAMPARM (USERID CHAR(8), DEPT CHAR(8)) IN &DATABASE.DRLSSAMP; ------------------------------------------------- DEFINE TABLE TESTSUM ------------------------------------------------SQL CREATE TABLE &PREFIX.TESTSUM (DATE DATE NOT NULL, TIME TIME NOT NULL, SYSID CHAR(4) NOT NULL, USERID CHAR(8) NOT NULL, DEPT CHAR(8) NOT NULL, TRNS FLOAT, RESP FLOAT, CPU FLOAT, PRNT FLOAT,
62
KBYTES
FLOAT,
PRIMARY KEY (DATE, TIME, SYSID, USERID, DEPT)) IN &DATABASE.DRLSSAMP; SQL CREATE UNIQUE INDEX &PREFIX.TESTSUM ON &PREFIX.TESTSUM (DATE, TIME, SYSID, USERID, DEPT) USING STOGROUP &STOGROUP PRIQTY 12 --<== CHECK SECQTY 12 --<== CHECK CLUSTER; ------------------------------------------------- DEFINE COMMENTS FOR TABLE TESTSUM ------------------------------------------------SQL COMMENT ON TABLE &PREFIX.TESTSUM IS SAMPLE STATISTICS; SQL COMMENT ON &PREFIX.TESTSUM (DATE IS DATE FROM THE SLR TIME KEY COLUMNS, TIME IS TIME FROM THE SLR HOUR KEY COLUMN, SYSID IS SYSTEM ID, USERID IS USER ID, DEPT IS DEPARTEMNT ID, TRNS IS NUMBER OF TRNS, RESP IS RESPONSE TIME, CPU IS CPU TIME, PRNT IS NUMBER OF PRINT LINES, KBYTES IS NUMBER OF KBYTES); ------------------------------------------------- GRANT USERS READ ACCESS TO TABLE TESTSUM ------------------------------------------------SQL GRANT SELECT ON &PREFIX.TESTSUM TO &USERS; ------------------------------------------------- DEFINE UPDATE FROM RECORD TEST_1 --TO TABLE TESTSUM ------------------------------------------------DEFINE UPDATE TESTSUM FROM TEST_1 TO &PREFIX.TESTSUM -- LET ( --<== CHECK --TIMESTAMP = TIMESTAMP_DATE ) --<== CHECK GROUP BY
63
(DATE TIME SYSID USERID DEPT
= = = = =
TIMESTAMP_DATE, TIMESTAMP_TIME, SYSID, USERID, VALUE(LOOKUP DEPT IN &PREFIX.SAMPARM WHERE USERID LIKE --<== CHECK USERID ,OTHER)) SUM(TRNS) , SUM(RESP) , SUM(CPU) , SUM(PRNT) , SUM(KBYTES)
SET ( TRNS RESP CPU PRNT KBYTES );
= = = = =
//SYSUT2 DD DSN=TME10PRU.LOCAL.DEFS(MIGE3008),DISP=SHR //* //********************************************************************* //* //* CREATE EPDM TABLE AND LOG COLLECTOR DEFINITIONS. STEP 2 OF 6. //* //********************************************************************* //EPDMIN EXEC PGM=DRLPLC, // PARM=(SYSTEM=DB2C SYSPREFIX=DRLSYS &PREFIX=DRL, // &DATABASE=DRLDB &STOGROUP=DRLSG &USERS=DRLUSER), // COND=(8,LE) //DRLIN DD DSN=TME10PRU.LOCAL.DEFS(MIGE3008),DISP=SHR //STEPLIB DD DISP=SHR,DSN=TME10PRF.SDRLLOAD // DD DISP=SHR,DSN=DB2V510.SDSNLOAD //DRLOUT DD SYSOUT=* //DRLDUMP DD SYSOUT=* //* //********************************************************************* //* //* UNLOAD DATA FROM SLR DATABASE TO A TEMPORARY IXF-FILE. STEP 3 OF 6. //* //********************************************************************* //SLRIN EXEC PGM=DREMNBEB,PARM=READ,COND=(8,LE) //STEPLIB DD DISP=SHR,DSN=SLR.V3R3M1.LINKLIB //LOAD DD DISP=SHR,DSN=TI3101.SLRSAMP // DD DISP=SHR,DSN=SLR.V3R3M1.SLRSAMP //IXFFILE DD DISP=(NEW,CATLG,DELETE), // DSN=TI3101B.DREG3008.IXF, // DCB=(RECFM=VB,LRECL=6000,BLKSIZE=12004,DSORG=PS), // SPACE=(CYL,(20,5)),UNIT=SYSDA //MAINFILE DD DISP=SHR,DSN=SLR.V3R3M1.SYSTEMDB //SYSOUT DD DUMMY //OUT DD SYSOUT=* //DUMP DD SYSOUT=* //IN DD * REPORT TESTSUM SELECT COLUMNS( + YEAR + MONTH +
64
DAY HOUR SYSID USERID DEPT TRNS RESP CPU PRNT KBYTES SELECT ROWS( YEAR MONTH DAY HOUR SYSID USERID DEPT UNLOAD IXF FILE(IXFFILE)
+ + + + + + + + + ) NE NE NE NE NE NE NE TOT TOT TOT TOT TOT TOT TOT AND AND AND AND AND AND + + + + + + + )
//* //********************************************************************* //* //* COPY THE GENERATED SQL INSERT STATEMENTS FROM THIS INLINE //* JCL TO A SPECIFIC MEMBER. STEP 4 OF 6. //* //********************************************************************* //SQLCOPY EXEC PGM=ICEGENER,COND=(8,LE) //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD * INSERT INTO &PREFIX.TESTSUM (DATE , TIME , SYSID , USERID , DEPT , TRNS , RESP , CPU , PRNT , KBYTES ) SELECT SUBSTR(DIGITS(YEAR), 2, 4)||-|| SUBSTR(DIGITS(MONTH), 4, 2)||-|| SUBSTR(DIGITS(DAY), 4, 2), SUBSTR(DIGITS(HOUR), 4, 2)||.00, VALUE(SYSID, ), VALUE(USERID, ), VALUE(DEPT, ), TRNS , RESP , CPU , PRNT , KBYTES FROM &PREFIX.DRLTEMP
65
//SYSUT2 DD DSN=TME10PRU.LOCAL.DEFS(MIGELOAD),DISP=SHR //* //********************************************************************* //* //* INSERT THE TEMPORARY IXF DATA INTO THE DB2 TABLE. STEP 5 OF 6. //* //********************************************************************* //SQLIN EXEC PGM=IKJEFT01,DYNAMNBR=25,COND=(8,LE) //STEPLIB DD DISP=SHR,DSN=TME10PRF.SDRLLOAD // DD DISP=SHR,DSN=QMF330C.DSQLOAD // DD DISP=SHR,DSN=DB2V510.SDSNLOAD //SYSPROC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQCLSTE //SYSEXEC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQEXECE //DRLOUT DD SYSOUT=* //*-----------------------------------------------------------//* QUERY DEFINITION LIBRARY //*-----------------------------------------------------------//DRLDEFS1 DD DISP=SHR,DSN=TME10PRU.LOCAL.DEFS //*-----------------------------------------------------------//* QMF LIBRARIES //*-----------------------------------------------------------//ADMGGMAP DD DISP=SHR,DSN=QMF330C.DSQMAPE //DSQDEBUG DD DUMMY //DSQUDUMP DD DUMMY //DSQPNLE DD DISP=SHR,DSN=QMF330C.DSQPNLE //DSQSPILL DD DSN=&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA, // SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096) //DSQEDIT DD DSN=&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE), // DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029) //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * EXECUTIL SEARCHDD(YES) %DRLEMIGR DB2C DRLDB DRLSG DRL 1 TI3101B.DREG3008.IXF MIGELOAD + TESTSUM TESTSUM //* //********************************************************************* //* //* DELETE THE TEMPORARY IXF-FILE. STEP 6 OF 6. //* //********************************************************************* //DELETE EXEC PGM=IEFBR14,COND=(8,LE) //IXFFILE DD DISP=(OLD,DELETE), // DSN=TI3101B.DREG3008.IXF
5. Review the JCL and the Performance Reporter definitions carefully before submitting the job. Especially check the lines marked with <== CHECK comment. Submit the JCL and check the output. If all is OK, then you have just successfully migrated your A.L.L. table and copied to it the lowest level of data maintained on that table.
66
Notes
1. In this exercise, we did not migrate a table with any computed columns. We did additional testing not shown in this redbook that gave the following result: A COMPCOL from the Service Level Reporter Log Source can be defined and resolved within Performance Reporter. A COMPCOL from the Service Level Reporter summary table is ignored. (Do not despair though because this calculation can be performed in any report) 2. Since we want to create a whole new component for this data, and well define all the required objects in it, this is the best time to delete the Log, Record, and Update definitions just created by the migration job. This will help you avoid duplicate names and/or un-needed objects in the Performance Reporter environment. To delete these definitions, you can create a member in hlq.LOCAL.DEFS, as shown in Figure 38, and execute it from the Other pull-down function 5. Process Performance Reporter Statements...
------------------------------------------------- DROP LOG EXAMPLEH ------------------------------------------------DROP LOG EXAMPL1H; ------------------------------------------------- DROP RECORD TEST_1 ------------------------------------------------DROP RECORD TEST_1 ; ------------------------------------------------- DROP UPDATE FROM RECORD TEST_1 --TO TABLE TESTSUM ------------------------------------------------DROP UPDATE TESTSUM ;
Figure 38. Drop Log, Record, and Update Object
4.2 Component Creation

In this section, we used the Performance Reporter statements created by the migration utility as a sample to create an entire component. We followed standard Performance Reporter conventions and created multiple members containing all the statements necessary to create the objects for our new component. As mentioned at the beginning of this chapter, these statements will be found in your hlq.LOCAL.DEFS library in a member called MIGExxxx,
67
where xxxx will be the unique number of the summary table that you have just migrated. In our example, it was MIGE3008. Using these statements in our Performance Reporter local definitions library, we created the following four members: 1. DRLLS001 (member containing the "define log" statement)
---********************************************************************/ --*/ --- Name: DRLLS001 Sample log definition */ --- Function: */ --- Define EXAMPLEH log. */ --*/ ---********************************************************************/ DEFINE LOG EXAMPLEH VERSION IBM.110; COMMENT ON LOG EXAMPLEH IS Sample log definition;
Figure 39. PR Statements for Log Definition - DRLLS001
2. DRLRS001 (member containing the "define record" statement)
------------------------------------------------- DEFINE RECORD TEST_1 ------------------------------------------------DEFINE RECORD TEST_1 IN LOG EXAMPLEH IDENTIFIED BY (SELECT_1 = 01) FIELDS ( SELECT_1 OFFSET 4 LENGTH 2 CHAR, TIMESTAMP_DATE OFFSET 7 LENGTH 6 DATE(MMDDYY), TIMESTAMP_TIME OFFSET 13 LENGTH 6 TIME(HHMMSS), SYSID OFFSET 20 LENGTH 4 CHAR, USERID OFFSET 25 LENGTH 8 CHAR, TRNS OFFSET 34 LENGTH 6 EXTERNAL INTEGER, RESP OFFSET 41 LENGTH 6 EXTERNAL INTEGER, CPU OFFSET 48 LENGTH 6 EXTERNAL INTEGER, PRNT OFFSET 55 LENGTH 6 EXTERNAL INTEGER, KBYTES OFFSET 62 LENGTH 6 EXTERNAL INTEGER); COMMENT ON RECORD TEST_1 IS SAMPLE DATA RECORD LOG;
Figure 40. PR Statements for Record Definition - DRLRS001
3. DRLSS001 (create this SQL yourself: it is merely a member containing Performance Reporter statements to define a tablespace)
68
------------------------------------------------- DEFINE TABLE SPACE FOR EXAMPLE H ------------------------------------------------SQL CREATE TABLESPACE DRLSEXMP IN &DATABASE USING STOGROUP &STOGROUP PRIQTY 60 SECQTY 30 SEGSIZE 8 LOCKSIZE TABLE;
Figure 41. PR Statements for Tablespace Definition - DRLSS001
4. DRLTS001 (member containing the Performance Reporter statements to define all the tables and update definitions required)
------------------------------------------------- DEFINE TABLE TESTSUM_H ------------------------------------------------SQL CREATE TABLE &PREFIX.TESTSUM_H (DATE DATE NOT NULL, TIME TIME NOT NULL, SYSID CHAR(4) NOT NULL, USERID CHAR(8) NOT NULL, DEPT CHAR(8) NOT NULL, TRNS FLOAT, RESP FLOAT, CPU FLOAT, PRNT FLOAT, KBYTES FLOAT, PRIMARY KEY (DATE, TIME, SYSID, USERID, DEPT)) IN &DATABASE.DRLSEXMP; SQL CREATE UNIQUE INDEX &PREFIX.TESTSUMX_H ON &PREFIX.TESTSUM_H (DATE, TIME, SYSID, USERID, DEPT) USING STOGROUP &STOGROUP PRIQTY 12 --<== CHECK SECQTY 12 --<== CHECK CLUSTER;
Figure 42. PR Table, Index, Lookup & Update Definition - DRLTS001 (Part 1 of 4)
69
-- DEFINE COMMENTS FOR TABLE TESTSUM_H -SQL COMMENT ON TABLE &PREFIX.TESTSUM_H IS SAMPLE STATISTICS; SQL COMMENT ON &PREFIX.TESTSUM_H (DATE IS DATE FROM THE SLR TIME KEY COLUMNS, TIME IS TIME FROM THE SLR HOUR KEY COLUMN, SYSID IS SYSTEM ID, USERID IS USER ID, DEPT IS DEPARTEMNT ID, TRNS IS NUMBER OF TRNS, RESP IS RESPONSE TIME, CPU IS CPU TIME, PRNT IS NUMBER OF PRINT LINES, KBYTES IS NUMBER OF KBYTES); -- GRANT USERS READ ACCESS TO TABLE TESTSUM_H -SQL GRANT SELECT ON &PREFIX.TESTSUM_H TO &USERS; -- DEFINE LOOKUP TABLE SAMPARM1 -SQL CREATE TABLE &PREFIX.SAMPARM1 (USERID CHAR(8), DEPT CHAR(8)) IN &DATABASE.DRLSEXMP; -DEFINE COMMENTS FOR SAMPARM1 SQL COMMENT ON TABLE &PREFIX.SAMPARM1 IS THIS LOOKUP TABLE ASSIGNS DEPARTMENT NAMES TO USERS.; SQL COMMENT ON &PREFIX.SAMPARM1 (USERID IS USER ID., DEPT IS DEPARTMENT NAME.); -- GRANT USERS READ ACCESS TO SAMPARM1 SQL GRANT SELECT ON &PREFIX.SAMPARM1 TO &USERS; ------------------------------------------------- DEFINE UPDATE FROM RECORD TEST_1 --TO TABLE TESTSUM_H ------------------------------------------------DEFINE UPDATE TESTSUM_01_H FROM TEST_1 TO &PREFIX.TESTSUM_H GROUP BY (DATE = TIMESTAMP_DATE, TIME = TIMESTAMP_TIME, SYSID = SYSID, USERID = USERID, DEPT = VALUE(LOOKUP DEPT IN &PREFIX.SAMPARM1 WHERE USERID LIKE --<== CHECK USERID ,OTHER)) SET ( TRNS = SUM(TRNS) , RESP = SUM(RESP) , CPU = SUM(CPU) , PRNT = SUM(PRNT) , KBYTES = SUM(KBYTES) );
70
-- DEFINE TABLE TESTSUM_D -SQL CREATE TABLE &PREFIX.TESTSUM_D (DATE DATE NOT NULL, SYSID CHAR(4) NOT NULL, USERID CHAR(8) NOT NULL, DEPT CHAR(8) NOT NULL, TRNS FLOAT, RESP FLOAT, CPU FLOAT, PRNT FLOAT, KBYTES FLOAT, PRIMARY KEY (DATE, SYSID, USERID, DEPT)) IN &DATABASE.DRLSEXMP; SQL CREATE UNIQUE INDEX &PREFIX.TESTSUMX_D ON &PREFIX.TESTSUM_D (DATE, SYSID, USERID, DEPT) USING STOGROUP &STOGROUP PRIQTY 12 --<== CHECK SECQTY 12 --<== CHECK CLUSTER; -- DEFINE COMMENTS FOR TABLE TESTSUM_D -SQL COMMENT ON TABLE &PREFIX.TESTSUM_D IS SAMPLE STATISTICS; SQL COMMENT ON &PREFIX.TESTSUM_D (DATE IS DATE FROM THE SLR TIME KEY COLUMNS, SYSID IS SYSTEM ID, USERID IS USER ID, DEPT IS DEPARTEMNT ID, TRNS IS NUMBER OF TRNS, RESP IS RESPONSE TIME, CPU IS CPU TIME, PRNT IS NUMBER OF PRINT LINES, KBYTES IS NUMBER OF KBYTES); -- GRANT USERS READ ACCESS TO TABLE TESTSUM_D -SQL GRANT SELECT ON &PREFIX.TESTSUM_D TO &USERS; -- DEFINE UPDATE FROM TABLE TESTSUM_H --TO TABLE TESTSUM_D -DEFINE UPDATE TESTSUM_H_D FROM &PREFIX.TESTSUM_H TO &PREFIX.TESTSUM_D GROUP BY (DATE = DATE, SYSID = SYSID, USERID = USERID, DEPT = DEPT) SET ( TRNS = SUM(TRNS) , RESP = SUM(RESP) , CPU = SUM(CPU) , PRNT = SUM(PRNT) , KBYTES = SUM(KBYTES) );
71
-- DEFINE TABLE TESTSUM_M -SQL CREATE TABLE &PREFIX.TESTSUM_M (DATE DATE NOT NULL, SYSID CHAR(4) NOT NULL, USERID CHAR(8) NOT NULL, DEPT CHAR(8) NOT NULL, TRNS FLOAT, RESP FLOAT, CPU FLOAT, PRNT FLOAT, KBYTES FLOAT, PRIMARY KEY (DATE, SYSID, USERID, DEPT)) IN &DATABASE.DRLSEXMP; SQL CREATE UNIQUE INDEX &PREFIX.TESTSUMX_M ON &PREFIX.TESTSUM_M (DATE, SYSID, USERID, DEPT) USING STOGROUP &STOGROUP PRIQTY 12 --<== CHECK SECQTY 12 --<== CHECK CLUSTER; -- DEFINE COMMENTS FOR TABLE TESTSUM_M -SQL COMMENT ON TABLE &PREFIX.TESTSUM_M IS SAMPLE STATISTICS; SQL COMMENT ON &PREFIX.TESTSUM_M (DATE IS DATE FROM THE SLR TIME KEY COLUMNS, SYSID IS SYSTEM ID, USERID IS USER ID, DEPT IS DEPARTEMNT ID, TRNS IS NUMBER OF TRNS, RESP IS RESPONSE TIME, CPU IS CPU TIME, PRNT IS NUMBER OF PRINT LINES, KBYTES IS NUMBER OF KBYTES); -- GRANT USERS READ ACCESS TO TABLE TESTSUM_M -SQL GRANT SELECT ON &PREFIX.TESTSUM_M TO &USERS; -- DEFINE UPDATE FROM TABLE TESTSUM_D --TO TABLE TESTSUM_M -DEFINE UPDATE TESTSUM_D_M FROM &PREFIX.TESTSUM_D TO &PREFIX.TESTSUM_M GROUP BY (DATE = SUBSTR(CHAR(DATE),1,8) || 01, SYSID = SYSID, USERID = USERID, DEPT = DEPT) SET ( TRNS = SUM(TRNS) , RESP = SUM(RESP) , CPU = SUM(CPU) , PRNT = SUM(PRNT) , KBYTES = SUM(KBYTES) );
72
Note
Since you want to create a whole new component for this data, it is best that you view the Performance Reporter table that was created in the migration as temporary. Only use it to insert data into the lowest summary level table in your new component. All our definitions in the above members created new objects. This will prohibit any SQL errors relating to duplicate tables, tablespaces, and updates. You can either create new names for the definitions and tables, or you can delete the ones that were created by the migration and re-create them in the component. To create a new component in Performance Reporter, you do the following: (We will continue using the members that we created earlier to complete this example) 1. Go to the Performance Reporter Administration panel and select 2. Components to get into the Components panel as shown in Figure 46.
Figure 46. Component Panel
2. Press F5 to create a new component. You will get a panel as in Figure 47
73
Figure 47. New Component Panel
3. On the New Component panel, do the following: In the Component Name field, enter your desired component name. (SLR2PRSA, in our case) In the Description field, enter a description of what the component is all about. Press the F5=Add obj PF-key to add the component objects. The Add Object panel will be displayed. On the Add Object panel, you will enter each and every object necessary to create your new component. When creating a new component, as we are in this case, we need not put in anything for Part or Part Description. Figure 48 on page 75 shows how we added our log definition, and we chose to leave these two fields empty.
74
Figure 48. Add Objects
4. To add the log definition, do the following: In the Object Name field, enter your desired log name, in our case, EXAMPLEH. In the Object Type field, enter 1. In the Member Name field, enter the member name that contains your "define log statement", in our case DRLLS001. Press Enter. 5. To add the record definition, do the following: In the Object Name field enter your desired record name, in our case, TEST_1. In the Object Type field, enter 2. In the Member Name field, enter the member name that contains your "define record statement", in our case, DRLRS001. Press Enter. 6. To add a tablespace, do the following: In the Object Name field, enter your desired tablespace name, in our case, DRLSEXMP. In the Object Type field, enter 5. In the Member Name field, enter the member name that contains your "create tablespace statements", in our case, DRLSS001.
75
Press Enter. 7. To add an hourly summary table, do the following: In the Object Name field, enter your desired table name, in our case, TESTSUM_H. In the Object Type field, enter 6. In the Member Name field, enter the member name that contains your "create table statements", in our case, DRLTS001. Press Enter. 8. To add a Lookup table, do the following: In the Object Name field, enter your desired Lookup table name, in our case, SAMPARM1. (Note: We used a different name here to the one in the actual migrate to prevent conflict.) In the Object Type field, enter 7. In the Member Name field, enter the member name that contains your "create table statements", in our case, DRLTS001. Press Enter. 9. To add an update from record definition, in our case, TEST_1, to hourly summary table, in our case, TESTSUM_H, do the following: In the Object Name field, enter your desired update name, in our case TESTSUM_01_H. In the Object Type field, enter 4. In the Member Name field, enter the member name that contains your "update definition statements", in our case, DRLTS001. Press Enter. 10. To add a daily summary table, do the following: In the Object Name field enter your desired table name, in our case, TESTSUM_D. In the Object Type field, enter 6. In the Member Name field enter the member name which contains your "create table statements", in our case, DRLTS001. Press Enter. 11. To add an update from hourly summary table, TESTSUM_H, to daily summary table, in our case TESTSUM_D, do the following:
76
In the Object Name field enter your desired update name, in our case, TESTSUM_H_D. In the Object Type field, enter 4. In the Member Name field, enter the member name that contains your "update definition statements", in our case, DRLTS001. Press Enter. 12. To add a monthly summary table, do the following: In the Object Name field, enter your desired table name, in our case, TESTSUM_M. In the Object Type field, enter 6. In the Member Name field, enter the member name that contains your "create table statements", in our case, DRLTS001. Press Enter. 13. To add an update from daily summary table, TESTSUM_D, to monthly summary table, in our case, TESTSUM_M, do the following: In the Object Name field, enter your desired update name, in our case, TESTSUM_D_M. In the Object Type field, enter 4. In the Member Name field, enter the member name that contains your "update definition statements", in our case, DRLTS001. Press Enter. If all of these steps were followed correctly, you have now created a component that is fully capable of reading your data log and populating your tables. Figure 49 on page 78 shows all of the objects that were created in our component.
77
SLR2PRSA Component Select an object. Then press Enter to Edit definition. Description . . . . . slr2pr mig sample component Installation time . : 1998-11-23-19.34.13 Installed by . . . . : TI3101B / _ _ _ _ _ _ _ _ _ _ Object Name DRLSEXMP EXAMPLEH SAMPARM1 TEST_1 TESTSUM_D TESTSUM_D_M TESTSUM_H TESTSUM_H_D TESTSUM_M TESTSUM_01_H Object Type TABSPACE LOG LOOKUP RECORD TABLE UPDATE TABLE UPDATE TABLE UPDATE Member DRLSS001 DRLLS001 DRLTS001 DRLRS001 DRLTS001 DRLTS001 DRLTS001 DRLTS001 DRLTS001 DRLTS001 Part
Row 1 from 10
Command ===> ______________________________________________________________ F1=Help F2=Split F3=Exit F4=Exclude F5=Add obj F7=Bkwd F8=Fwd F9=Swap F10=View F11=Delete F12=Cancel
Figure 49. Created Component
In order to collect data to this component, we will (like the pre-defined components) have to install it. You install this component in exactly the same manner as any pre-defined component. An alternative means of defining a component in Performance Reporter is to create a member DRLIxxxx in hlq.LOCAL.DEFS, insert the necessary code, and execute the member from the Other pull-down function 5. Process Performance Reporter Statements.... In this exercise, we created the member DRLIMS2P as shown in Figure 50 on page 79. It is incomplete because we have omitted the objects pertaining to report definition that we intend to complete at the end of Chapter 6.3, Example of Report Migration on page 106 (see Figure 101 on page 128 in Chap. 6), after the migration of the related report.
78
/**********************************************************************/ /* */ /* Licensed Materials - Property of IBM */ /* */ /* 5695-101 (C) Copyright IBM Corporation 1993, 1998 */ /* See Copyright Instructions. */ /* */ /**********************************************************************/ /* */ /* Name: DRLIMS2P */ /* */ /* Status: Performance Reporter 1.2.0 */ /* */ /* Function: */ /* SLR2PR Mig Sample Component Initialization */ /* */ /* This member initializes the component and component object */ /* tables. It should be executed when Performance Reporter is */ /* installed if the sample component will be used. After that, */ /* the component can be installed from the administration dialog. */ /* */ /* Change activity: */ /* 00 1998-12-10 MB Created for migration activities */ /* */ /**********************************************************************/ /**********************************************************************/ /* */ /* SLR2PR Mig Sample Component */ /* */ /**********************************************************************/ SQL INSERT INTO &SYSPREFIX.DRLCOMPONENTS (COMPONENT_NAME, DESCRIPTION, USER_ID) VALUES(SLR2PRSA,SLR2PR Mig Sample Component,USER); /**********************************************************************/ /* Log and record definitions */ /**********************************************************************/ SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,LOG ,EXAMPLEH,DRLLS001); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,RECORD ,TEST_01,DRLRS001); /**********************************************************************/ /* Tablespace, table, and update definitions */ /**********************************************************************/ SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,TABSPACE,DRLSEXMP,DRLSS001);
Figure 50. Component Creation DRLIMS2P in hlq.LOCAL.DEFS (Part 1 of 2)
79
SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,LOOKUP ,SAMPARM1,DRLTS001); SQL UPDATE &SYSPREFIX.DRLCOMP_OBJECTS SET MEMBER_NAME = DRLTS001 WHERE COMPONENT_NAME = SLR2PRSA AND OBJECT_TYPE = LOOKUP AND OBJECT_NAME = SAMPARM1; SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,TABLE ,TESTSUM_H,DRLTS001); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,UPDATE ,TESTSUM_01_H,DRLTS001); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,TABLE ,TESTSUM_D,DRLTS001); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,UPDATE ,TESTSUM_H_D,DRLTS001); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,TABLE ,TESTSUM_M,DRLTS001); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,UPDATE ,TESTSUM_D_M,DRLTS001);
Figure 51. Component Creation DRLIMS2P in hlq.LOCAL.DEFS (Part 2 of 2)
We executed this member to create the component by using the process from the Administration Panel, Other pull down, and selecting option 5. Process Performance Reporter statements... as shown in following Figure 52.
NOTE
In this way, you will retain these definition statements even if you delete the component. To rebuild the component, you would only have to re-process your member or perform the System Tables Update process.
80
Figure 52. Process Performance Reporter Statements
4.3 Populating Your New Tables with Migrated Data

Chapter 4.2, Component Creation on page 67 describes creating and installing a new component. Now you need to insert the migrated data into the low level hourly table and then cascade that data into the daily and monthly tables. We will continue with the same example. 1. Create a member in your local definitions library that contains a simple insert statement. The statement will tell Performance Reporter to insert data from the temporary summary table (the one that contains the data from the migration) into the newly created low level summary table, which, in our case, is the hourly table TESTSUM_H. The statement looks like this: SQL INSERT INTO &PREFIX.TESTSUM_H SELECT * FROM &PREFIX.TESTSUM ; 2. From the Performance Reporter Administration Panel, select 4. Tables for the Tables menu. 3. Put your cursor on Other on the Action Bar at the top of the panel and press Enter. 4. Select 5. Process Performance Reporter statements.... See Figure 53 on page 82 for an example of what to enter in this panel.
81
Figure 53. Process Performance Reporter Statements
5. In the Input data set name field, enter your local definitions data set name and the member that contains your insert statements. 6. In the Type of statements field, enter a 1 for Log collector. 7. Press Enter to edit the member if required. 8. Then press F5 to execute the statement and populate your _H table.
NOTE
Since we moved the content of the migrated data from the temporary table created by the migration job to the hourly table created by our component, we no longer need the temporary table. This would be an appropriate time to delete it in order to avoid having un-needed objects in your Performance Reporter environment. To do this, you create a member in hlq.LOCAL.DEFS as shown in Figure 54 and execute it using the 5. Process Performance Reporter Statements... in the Other pull-down from any Performance Reporter dialog.
------------------------------------------------- DROP TABLE TESTSUM ------------------------------------------------SQL DROP TABLE &PREFIX.TESTSUM ;
Figure 54. Drop Migrated Temporary Table
82
Your low level summary table, the _H table, now contains all of your migrated data. You now need to populate the cascading members. To do this, you perform a recalculate on the _H table. 1. Select the table that you have just populated and select Utilities from the action bar as shown in Figure 55.
Figure 55. Utility Window
2. Select 8. Recalculate to do a recalculation and press Enter. 3. In the Recalculate menu, select 4. Recalculate and press Enter. See Figure 56 on page 84 for an example of the Recalculate panel. After pressing enter here, you will get to a Condition panel. The Condition panel should generally be left blank. You can, however, specify one or more conditions that restrict the affect of recalculation to specific rows of the source table. Type only one condition on each line. If you do not specify a condition, Performance Reporter recalculates every row of the source table (this is what we want in our case). Each condition statement can be up to 60 alphanumeric characters long. 4. When you press Enter, Performance Reporter will automatically propagate recalculation to all dependent tables. Every summary table in your component will thus be populated with summarized data as specified. In our case, the daily (_D) and monthly (_M) summary tables.
83
Figure 56. Recalculate
5. Check your tables to ensure that they have been populated and for data consistency. At this point, if the Lookup table(s) in your component has been populated, (see Chapter 5, Migrating Parameter Table Data on page 85) you are ready to collect data as you would normally do within Service Level Reporter. You should now collect log data to both Service Level Reporter and Performance Reporter and compare results.
84
Chapter 5. Migrating Parameter Table Data

This chapter provides details on how to migrate Service Level Reporter parameter tables to Performance Reporter update tables. The Performance Reporter equivalent of the Service Level Reporter parameter table is the Lookup table. There are some differences between their operation, as follows: A Lookup table can be used at collect or report time as with Service Level Reporter; however, a view is not needed when accessing a Lookup table from a report. A Lookup table has no GEN values; these are replaced by wild cards. A Lookup table can be used against any level of summarization, not just at the transaction (log table) level. Lookup tables are referenced during recalculation. The contents of parameter tables can be migrated from Service Level Reporter to Performance Reporter, but caution must be exercised as some tables are now merged. For example: BATCH_BE_TAB and TSO_BE_TAB are merged into one Lookup table, USER_GROUP within Performance Reporter. This table is based around the RACF user ID of a TSO session or batch job, whereas the Service Level Reporter tables use a WID derived from an exit. There are three possible ways to populate the Performance Reporter Lookup table with information from the Service Level Reporter parameter table. These three ways are: 1. Enter the data manually as described in Chapter 5.1, Reenter Data on page 86. 2. Unload the data from the parameter table into a flat file and use a DB2 utility to load the data into the Lookup table as described in Chapter 5.2, DB2 Load Utility on page 87. 3. Unload the data from the parameter table into IXF file format and use the Performance Reporter utility to populate the Lookup table as described in Chapter 5.3, IXF Unload on page 93. We recommend that you do not migrate parameter table data if it is not very large. Rather, populate the new Performance Reporter Lookup tables by keying the data in afresh.
85
5.1 Reenter Data

To manually enter the data into a Lookup table, it must be done from the Tables menu. You can access the Tables menu by selecting 2. Administration from the Performance Reporter Primary Menu and then selecting 4. TABLES from the Administration window. 1. Locate and select the desired Lookup table. Do not press Enter yet. 2. Move focus to the action bar of the Tables window and open the Edit pull-down as shown in Figure 57.
Note
If you used the migration dialog to migrate predefined data from Service Level Reporter, then the Lookup table you are looking for is the Lookup table associated with the Performance Reporter table your data was migrated into. If you used the migration dialog to migrate user defined tables from Service Level Reporter to Performance Reporter, then the Lookup table you are looking for is the Lookup table created by the migration utility.
Figure 57. Selecting SAMPARM from Table List
86
3. From the Edit pull-down, select 1. Add Rows and press Enter. The ADD ROWS window in QMF, as shown in Figure 58, is displayed.
Figure 58. QMF ADD SAMPARM Data Entry Window
4. Enter the values for each row that you want to add to the Lookup table.
Note
It is recommended that you do not use the ISPF editor to enter the data into the table because the ISPF rules are not the same as Performance Reporter rules that can cause you to lose the data you entered. 5. When you have completed entering the data into the Lookup table, press the F3=End pf-key to save and exit the QMF edit session and return to Performance Reporter Tables window.
5.2 DB2 Load Utility

Another means of populating a Lookup table is to migrate the Parameter Tables data. This can be done by using a DB2 utility to load the table using a flat file as input. 1. Generate a complete report of the parameter table contents and write the output to a disk data set. For example, the JCL shown in Figure 59 sends
Migrating Parameter Table Data
87
the Service Level Reporter report of the parameter table SAMPARM to the data set called TI3101.SLR.OUT.
//TI3101AB JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //****************************************************************** //* //* REPORT DATA FROM SLR DATABASE TO A WORKING DATA SET //* //****************************************************************** //SLRIN EXEC PGM=DREMNBEB,PARM=READ //STEPLIB DD DISP=SHR,DSN=SLR.V3R3M1.LINKLIB //LOAD DD DISP=SHR,DSN=TI3101.SLRSAMP // DD DISP=SHR,DSN=SLR.V3R3M1.SLRSAMP //MAINFILE DD DISP=SHR,DSN=SLR.V3R3M1.SYSTEMDB //OUT DD DSN=TI3101.SLR.OUT,DISP=(NEW,CATLG), // DCB=(RECFM=FBA,LRECL=133,BLKSIZE=13300), // UNIT=SYSDA,SPACE=(13300,(3,3)) //IN DD * REPORT SAMPARM LIST ALL ENDREP /*
Figure 59. Parameter Table Report
2. You will need to edit the parameter table report output to ensure that all rows that do not contain data to be loaded into the Lookup table contain a non-valid control character in column one. For the DB2 load utility to work correctly, the first byte of each record that is to be loaded into the Lookup table must contain a valid control character. In the JCL, shown in Figure 62 on page 92, the control character we used is the space character (X40). This is communicated to the load utility by the statement WHEN (1:1) = in the SYSIN DD * input for the step LOADTAB. For example, some of the non data records of the parameter table report produced in step 1. have a space in column 1, as can be seen in the report listing for the parameter table SAMPARM shown in Figure 60. The report heading/footing, as well as the default parameter table value of GENER, contain a space in column one. In the edited report, shown in Figure 61.
88
on page 90, these values have had the * placed in column 1 for each row that should not be loaded into the Lookup table.
DRE2500I SLR VERSION 3 RELEASE 3, MODIFICATION LEVEL 1 REPORT SAMPARM LIST ALL -USERID | DEPT | *********|********* ADAMS | APPL DEV GEYER | FINANCE GOUNOT | RETAIL HAAS | FINANCE JONES | APPL DEV KWAN | MARKETNG LEE | MANUFACT LUTZ | MANUFACT MARINO | RETAIL MEHTA | MANUFACT PARKER | FINANCE PEREZ | RETAIL PIANKA | SYS SUPP PULASKI | MANUFACT SMITH | APPL DEV SPENCER | FINANCE STERN | MARKETNG THOMPSON | SYS SUPP GENERAL | GENER ENDREP END /* GENERATED */
Figure 60. SAMPARM Report Listing
89
*DRE2500I SLR VERSION 3 RELEASE 3, MODIFICATION LEVEL 1 * REPORT SAMPARM * LIST ALL -USERID | DEPT * | **********|********* ADAMS | APPL DEV GEYER | FINANCE GOUNOT | RETAIL HAAS | FINANCE JONES | APPL DEV KWAN | MARKETNG LEE | MANUFACT LUTZ | MANUFACT MARINO | RETAIL MEHTA | MANUFACT PARKER | FINANCE PEREZ | RETAIL PIANKA | SYS SUPP PULASKI | MANUFACT SMITH | APPL DEV SPENCER | FINANCE STERN | MARKETNG THOMPSON | SYS SUPP *GENERAL | GENER * ENDREP * END /* GENERATED */
Figure 61. SAMPARM Report after Correcting
Use the DB2 utility DSNUTILB to load the information from the report generated in step 1. on page 87 into the Lookup table. The JCL to run the DB2 utility to load the data is shown in Figure 62 on page 92. The job has two parts: 1. An IEBGENER step to convert the report data set to the correct record length (LRECL) required for the DB2 load utility to work successfully. 2. The DSNUTILB step to load the converted report data into the Lookup table. Specify the following values in the JCL for the DB2 utility job shown in Figure 62.
90
Set the correct values for the parameters on the TABPROC PROC statement for OUTC, UNIT, DB2SS, PARMDATA, DRLIDX1,and DSNLOAD. Change the SYSUT2 DD LRECL value of the ALTSIZE step to the size of the records of the data in the parameter report data set. In the SAMPARM, example the data being migrated is 20 bytes in length. Code the parameters in the ALTSIZE.SYSIN DD * to the length of the data being migrated. In the SAMPARM example, this value is 20. Code the parameters in the LOADTAB.SYSIN DD * to the values: The name of the Lookup table to be loaded. In the SAMPARM example, it is DRL.SAMPARM. The names or the columns to be loaded in the Lookup table. In the SAMPARM example, these are USERID and DEPT. The location of the data in the report flat file where the data can be found. In the SAMPARM example, the USERID data is found in columns 2 through 9, and the DEPT data is found in columns 13 through 20.
91
//TI3101AP JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //******************************************************************** //* //* LOAD DATA FROM UNLOADED FLAT PARAMETER TABLE INTO PR LOOKUP TABLE //* //******************************************************************** //* //******************************************************************** //* IN LINE PROC //******************************************************************** //TABPROC PROC OUTC=*, // UNIT=SYSALLDA, // DB2SS=DB2C, // PARMDATA=TI3101.SLR.OUT1, // DRLIDX1=TI3101, // DSNLOAD=DB2V510.SDSNLOAD //* //* //******************************************************************** //* ALTSIZE: - MAKE THE INPUT DATA CORRECT RECORD SIZE * //******************************************************************** //ALTSIZE EXEC PGM=IEBGENER //SYSUT1 DD DISP=SHR,DSN=&PARMDATA //SYSPRINT DD SYSOUT=&OUTC //SYSUT2 DD DISP=(NEW,PASS,KEEP),DSN=&DRLIDX1..TEMPTAB, // UNIT=&UNIT,SPACE=(TRK,(15,15),RLSE), // DCB=(BLKSIZE=06160,LRECL=0020,RECFM=FB,DSORG=PS) //* //******************************************************************** //* LOADTAB: - LOAD LOOKUP TABLE USING DB2 LOAD UTILITY * //******************************************************************** //LOADTAB EXEC PGM=DSNUTILB,REGION=4096K, // PARM=&DB2SS //STEPLIB DD DSN=&DSNLOAD, // DISP=SHR DB2 DSNLOAD LIBRARY //SYSPRINT DD SYSOUT=&OUTC //UTPRINT DD SYSOUT=&OUTC //SYSUDUMP DD SYSOUT=&OUTC //SYSREC DD DSN=&DRLIDX1..TEMPTAB,DISP=(OLD,DELETE) //SYSUT1 DD UNIT=&UNIT,SPACE=(CYL,(3,1)) //SORTOUT DD UNIT=&UNIT,SPACE=(CYL,(3,1)) // PEND //* //******************************************************************** //* END OF INLINE PROC //********************************************************************
Figure 62. TABPROC DB2 Load Utility (Part 1 of 2)
92
//******************************************************************** //* //* // EXEC TABPROC //* //* //******************************************************************** //* ALTSIZE: - MAKE THE INPUT DATA CORRECT RECORD SIZE * //******************************************************************** //ALTSIZE.SYSIN DD * GENERATE MAXNAME=10,MAXFLDS=10,MAXLITS=80 RECORD FIELD=(0020,1,,1) /* //* //******************************************************************** //* LOADTAB: - LOAD LOOKUP TABLE USING DB2 LOAD UTILITY * //******************************************************************** //LOADTAB.SYSIN DD * LOAD DATA RESUME YES INTO TABLE DRL.SAMPARM WHEN (1:1) = (USERID POSITION(02:09), DEPT POSITION(13:20)) /*
Figure 63. TABPROC DB2 Load Utility (Part 2 of 2)
5.3 IXF Unload

Another method for migrating large amounts of data from a parameter table into a Performance Reporter Lookup table is to unload the data into an IXF file format and then load it into the related Performance Reporter Lookup table that has already been created. To demonstrate this technique, we used the job shown in Figure 64 on page 94. We used the JCL shown in Figure 32 on page 61 created by the migration of the SAMPSUM summary table in Chapter 4.1, The A.L.L. Table Migration on page 57 as a starting point. The job has two steps: 1. To perform the unload operation (step SLRIN) to an IXF file and 2. To perform a load operation (step SQLIN) into the Lookup table.
93
//TI3101AB JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //********************************************************************* //* //* UNLOAD DATA FROM SLR DATABASE TO A TEMPORARY IXF-FILE. STEP 1 OF 2. //* //********************************************************************* //SLRIN EXEC PGM=DREMNBEB,PARM=READ //STEPLIB DD DISP=SHR,DSN=SLR.V3R3M1.LINKLIB //LOAD DD DISP=SHR,DSN=TI3101.SLRSAMP // DD DISP=SHR,DSN=SLR.V3R3M1.SLRSAMP //IXFFILE DD DISP=(NEW,CATLG,DELETE), // DSN=TI3101A.SUMPARM.IXF, // DCB=(RECFM=VB,LRECL=6000,BLKSIZE=12004,DSORG=PS), // SPACE=(CYL,(20,5)),UNIT=SYSDA //MAINFILE DD DISP=SHR,DSN=SLR.V3R3M1.SYSTEMDB //OUT DD SYSOUT=* //* //IN DD * REPORT SAMPARM LIST ALL UNLOAD IXF ID(PARAMETER TABLE) FILE(IXFFILE) ENDREP //********************************************************************* //* //* INSERT THE TEMPORARY IXF DATA INTO THE DB2 TABLE. STEP 2 OF 2. //* //********************************************************************* //SQLIN EXEC PGM=IKJEFT01,DYNAMNBR=25,COND=(8,LE) //STEPLIB DD DISP=SHR,DSN=TME10PRF.SDRLLOAD // DD DISP=SHR,DSN=QMF330C.DSQLOAD // DD DISP=SHR,DSN=DB2V510.SDSNLOAD //SYSPROC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQCLSTE //SYSEXEC DD DISP=SHR,DSN=TME10PRF.SDRLEXEC // DD DISP=SHR,DSN=QMF330C.DSQEXECE //DRLOUT DD SYSOUT=* //*-----------------------------------------------------------//* QUERY DEFINITION LIBRARY //*-----------------------------------------------------------//DRLDEFS1 DD DISP=SHR,DSN=TME10PRU.LOCAL.DEFS
Figure 64. Unload and Load Using IXF File and QMF (Part 1 of 2)
94
//*-----------------------------------------------------------//* QMF LIBRARIES //*-----------------------------------------------------------//ADMGGMAP DD DISP=SHR,DSN=QMF330C.DSQMAPE //DSQDEBUG DD DUMMY //DSQUDUMP DD DUMMY //DSQPNLE DD DISP=SHR,DSN=QMF330C.DSQPNLE //DSQSPILL DD DSN=&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA, // SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096) //DSQEDIT DD DSN=&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE), // DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029) //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //*--------------------------------------------------------------------//* INPUT PARAMETERS: */ //* DB2SUBS - NAME OF DB2 SUBSYSTEM (DEFAULT=DSN) */ //* DBNAME - NAME OF DB2 DATABASE (DEFAULT=DRLDB) */ //* STOGROUP - NAME OF DB2 STORAGE GR.(DEFAULT=DRLSG) */ //* TBPREFIX - TABLE PREFIX (DEFAULT=DRL) */ //* NR_TABLES - NUMBER OF TABLES TO BE MIGRATED */ //* FOR EACH TABLE: */ //* UNLOAD_TAB - UNLOADED SLR TABLE TO BE IMPORTED TO QMF */ //* Q_NAME - MEMBERNAME FOR QUERY (INSERT STATEMENTS) */ //* FROM_TABLE - SLR V3 TABLE NAME (MIGRATE FROM) */ //* TO_TABLE - EPDM TABLE NAME (MIGRATE TO) */ //*--------------------------------------------------------------------//SYSTSIN DD * EXECUTIL SEARCHDD(YES) %DRLEMIGR DB2C DRLDB DRLSG DRL 1 TI3101A.SUMPARM.IXF MIGPARM + SAMPARM SAMPARM //*
Figure 65. Unload and Load Using IXF File and QMF (Part 2 of 2)
The first step, SLRIN, is a normal SLR report job to perform a list of the complete contents of SAMPARM table in an IXF file pointed to by IXFFILE DD statement. The second step, SQLIN , performs the load operation from the IXF file (in our case, TI3101A.SUMPARM.IXF) into the SAMPARM table by using SQL statements contained in the MIGPARM member of the hlq.LOCAL.DEFS. The MIGPARM member for the parameter table being migrated is shown in Figure 66.
95
INSERT INTO &PREFIX.SAMPARM (USERID , DEPT ) SELECT VALUE(USERID, ) , VALUE(DEPT, ) FROM &PREFIX.DRLTEMP
Figure 66. Load SQL Statement (MIGPARM)
The MIGPARM member, created in hlq.LOCAL.DEFS, contains the SQL statements that the DRLEMIGR Exec will use to load the target Lookup table SAMPARM.
NOTE
The comments for the SQLIN step shown in Figure 65 on page 95 describe the input parameters used by the DRLEMIGR Exec.
5.4 Populate the Lookup Table Defined by the New Component

In the three methods above, we populated the SAMPARM Lookup table in Performance Reporter created by the migration job in Chapter 4.1, The A.L.L. Table Migration on page 57. But we defined a SAMPARM1 Lookup table in 4.2, Component Creation on page 67, and now we need to populate it with the data that actually resides in SAMPARM. We did it by performing the following procedure that is very similar to the process described in 4.3, Populating Your New Tables with Migrated Data on page 81: 1. Create a member in your hlq.LOCAL.DEFS library that contains a simple insert statement as seen in Figure 67. The statement tells Performance Reporter to insert data from the temporary Lookup table (the one that contains the data from the migration) into the newly created Lookup table, which, in our case, is SAMPARM1.
96
SQL INSERT INTO &PREFIX.SAMPARM1 SELECT * FROM &PREFIX.SAMPARM ;

Figure 67. Member to Populate Lookup Table
2. From the Performance Reporter Administration Panel select the Other pull-down. 3. Select 5. Process Performance Reporter statements.. and press Enter. 4. Execute the member containing the SQL insert statement. Your Lookup table SAMPARM1 will now contain the parameter data.
NOTE
Since we used a temporary Lookup table created by the migration job to populate the Lookup table (SAMPARM1), defined by our component, we no longer need the temporary table, and it is an appropriate time to delete it in order to avoid un-needed objects in your Performance Reporter environment. To do this, you should create a member in hlq.LOCAL.DEFS as shown in Figure 68 and execute it from the Other pull-down function by selecting 5. Process Performance Reporter Statements...
------------------------------------------------- DROP TABLE SAMPARM ------------------------------------------------SQL DROP TABLE &PREFIX.SAMPARM ; ------------------------------------------------
Figure 68. Drop SAMPRM Temporary Lookup Table
97
98
Chapter 6. Migrating SLR Reports

This chapter shows how to migrate Service Level Reporter reports to Performance Reporter and presents an example of migrating a report for the user-defined table migrated in Chapter 4, Migrating User-Defined A.L.L Based Tables and Data on page 57.
NOTE
Additional information pertaining to Service Level Reporter report migration can be found in "Appendix F. Migrating from SLR Version 3.3" in the Performance Reporter for OS/390 Administration Guide. In the analysis of your Service Level Reporter installation, you may have discovered some reports that had been created or customized so that they better fit the reporting needs of your organization. Before you migrate these reports to Performance Reporter, you need to look at the supplied reports provided with Performance Reporter and its components. Many of these Performance Reporter reports are improved over the predefined Service Level Reporter reports. You may find that they meet your needs, thereby removing the need to migrate your customized Service Level Reporter reports. Keep the following in mind when you plan to migrate from Service Level Reporter to Performance Reporter: New table (and update definitions) capabilities - Do different things in Performance Reporter reports than Service Level Reporter. Better report-time summarization in Performance Reporter. Expect to change most (all user-defined) reports (where the data is not already in standard reports). Use report migration (available in Performance Reporter Base) to produce a "first draft" report. Table 5 shows the differences between Performance Reporter reporting and Service Level Reporter reporting.
Table 5. Comparison of SLR and PR Reporting Functions
Task Read Data from DB Row Calculation Summarize Data
SLR Similar VIEW - DATACOL Limited - SUBTOT
PR Similar SQL or Update Definition Powerful SQL and QMF Functions
99
Task Merge Tables
SLR VIEW
PR DB2 View or DB2 Join in Query
Performance Reporter provides a report migration tool called ERMT to assist you in migrating reports from Service Level Reporter. ERMT helps convert Service Level Reporter V3 report language statements to SQL queries and QMF forms. You access the ERMT tool when you select to migrate reports from the Performance Reporter Migration dialog. The reports are migrated from Service Level Reporter ISPF tables (SLRTABL) or from Service Level Reporter report command source data sets. During migration, QMF queries and forms are created, as well as Performance Reporter report definitions that are used to create Performance Reporter report groups and reports.
NOTE
The queries and forms created are in QMF format, but you can use them if you are using the reporting dialog without QMF (just as you can use the predefined Performance Reporter reports, which are also created using QMF). The reports are migrated group by group.
NOTE
If you are migrating user-defined Service Level Reporter reports (SLRTABL input), we recommend that you put the user-defined reports in a Service Level Reporter report group of their own and use this Service Level Reporter report group when migrating. Before you can start migrating reports, you must define migration parameters for report migration.
6.1 SLR Report Description

For the example in this chapter, a user-defined report was built for the A.L.L user defined summary table (TESTSUM) that was migrated in Chapter 4, Migrating User-Defined A.L.L Based Tables and Data on page 57.
100
It was a very simple report called TESTSUM_01 contained in a group called MAURO as listed on the SLR Report Dialog panel shown in Figure 69 on page 101.
NOTE
The migration tool (ERMT) bases its migration process at group boundary level. This means that if you have multiple reports belonging to one group, all the reports will be migrated during the same process.
Figure 69. SLR Group and Report Names
Press the F4=Commands PF-key on the SLR Report Dialog panel shown in Figure 69 to list the statements pertaining to the report TESTSUM_01. This report is run against the table TESTSUM that resides in the SYSTEMDB data base. An example of the SLR Report Generation: Command View panel is shown in Figure 70 on page 102.
Migrating SLR Reports
101
Figure 70. SLR Command View for Report Generation
Press F5=Report on the SLR Report Generation: Command View panel shown in Figure 70 to request Service Level Reporter to run the report. The result of the example report is shown in Figure 71.
Figure 71. SLR Report Output (Part 1 of 2)
102
Figure 72. SLR Report Output (Part 2 of 2)
It is not necessary to run your Service Level Reporter report before migrating it, but we have done so to show you the report before and after.
6.2 Setting Migration Parameters for Reports

Before you migrate user-defined reports, you must set the migration parameters in Performance Reporter. You set (or check) the migration parameters using the administration dialogs. 1. From the Administration window, select 1. System. Performance Reporter displays the System window. 2. From the System window, select 4. Migration. Performance Reporter displays the Migration window shown in Figure 73.
103
Figure 73. Migration Parameters for Report Migration Window
3. From the Migration window Select 4. Migration parameters for report migration. The Migration Parameters for Report Migration window is displayed as shown in Figure 74 on page 105.
104
Figure 74. Migration Parameters for Reports Window (Part 1 of 2)
Figure 75. Migration Parameters for Reports Window (Part 2 of 2)
4. Type the required library information, and press Enter.
105
Performance Reporter returns to the Migration window as in Figure 73 on page 104.

NOTE NOTE
The libraries should be concatenated with the local (user) libraries first, followed by the SLR product libraries as shown in the example in Figure 74 on page 105.
6.3 Example of Report Migration

Following are the steps performed to make the migration of the Report Group called MAURO: 1. From the Migration Panel as shown in Figure 73 on page 104, select option 5.Convert SLR V3 reports to Performance Reporter reports and press Enter. The Convert SLR V3 Reports to Performance Reporter Reports window, as shown in Figure 76 on page 107, is displayed. Enter the values associated with the report you are migrating into the panel. For this example, the migration of the TESTSUM_01 report, the following values have been set: MAURO 1. As SLR report Group name. In the SLR Report command input. This means that the source information will be retrieved from the SLRTBL data sets. As Performance Reporter report library. This defines where to put the results for the migration. As Member name for report definition. This defines the name of the member that will be processed by Performance Reporter in order to install the new report group. As Member name prefix for QUERY and FORM. This defines the first 3-char prefix of the members that will be created in hlq.LOCAL.DEFS data set for the query and form member(s). In the ID field. This defines the report group name in Performance Reporter where the report(s) belong.
hlq.LOCAL.DEFS TESTSUMR
TXT
TESTSUM_REP
106
TESTSUM REPORT MIGRATED FROM SLR 001 In Description field. This text will be shown in the report group object in Performance Reporter. In Sequence number field. It defines the starting sequence number that will be appended to the created query and form objects. A sequence number will be assigned for each report migrated. If you have already migrated other reports using the same 3-char prefix (TXT), you will want to set this value so that the reports being migrated at this time dont override any previous object names.
NOTE
Make a note of the data set name specified as Performance Reporter report library and the member name specified as Member name for report definitions. These names will be used later when you run the report definition statements to create the report groups and reports.
Figure 76. PR Report Migration Window (Part 1 of 2)
107
Figure 77. PR Report Migration Window (Part 2 of 2)
2. When you have entered the information on the Convert SLR V3 Reports to Performance Reporter Reports window press Enter. The Performance Reporter migration tool will process the information you input and generate a job stream to perform the migration as shown in Figure 78 on page 110. This job stream is a multi-step job that performs the following: Step2 Step3 Step4 Extract report command information from SLRTBL data sets. This is done by the DRLEARM1 EXEC. Extract data set and member names from SLRCLIST for View definitions. This is done by DRLEARM2 EXEC. Extract Service Level Reporter Table and Column information. Virtual Column calculation (COMPCOLs). Access, Lookup and DATACOL for Views. This is done by DRLEARM3 EXEC. Consolidate all information extracted in one file. This is done by DRLEARM4 EXEC. Create DEFINE GROUP and DEFINE REPORT commands. This is done by DRLEARM5 EXEC. Create SQL and QMF FORMs. This is done by DRLEARM6 EXEC. Delete all work files created by the steps above.
Step5 Step6 Step7 Step8
108
NOTE
You need to modify the created job stream to correctly specify the JOB card and the ISPF library names according to your MVS environment. 3. Submit the job and press F3 to exit from the ISPF Edit function.
109
//TI3101AG JOB (999,POK),EXPERT,MSGLEVEL=1,MSGCLASS=T,NOTIFY=&SYSUID, // CLASS=A //* //* //********************************************************************* //* //* MIGRATE SLR V3 REPORTS TO EPDM REPORTS //* //* NOTES: //* //********************************************************************* //* SLR V3 REPORT GROUP NAME : MAURO //* //* SLR REPORT COMMAND INPUT : TI3101.SLRTABL //* SLR.V3R3M1.SLRTABL //* //* EPDM REPORT LIBRARY : TME10PRU.LOCAL.DEFS //* //********************************************************************* //********************************************************************* //* //* EXTRACT REPORT COMMAND INFORMATION //* FROM SLRTABL //* //********************************************************************* //STEP2 EXEC PGM=IKJEFT01, // DYNAMNBR=25, // REGION=6M //********************************************************************* //STEPLIB DD DSN=SLR.V3R3M1.LINKLIB, // DISP=SHR // DD DSN=ISP.SISPLOAD, // DISP=SHR //* DD DSN=SYS1.ISRLOAD, //* DISP=SHR //********************************************************************* //SYSPROC DD DSN=TME10PRF.SDRLEXEC, // DISP=SHR //********************************************************************* //*SPPLIB DD DSN=SYS1.ISRPENU, //* DISP=SHR //ISPPLIB DD DSN=ISP.SISPPENU, // DISP=SHR //*SPMLIB DD DSN=SYS1.ISRMENU, //* DISP=SHR //ISPMLIB DD DSN=ISP.SISPMENU, // DISP=SHR //*SPSLIB DD DSN=SYS1.ISRSENU, //* DISP=SHR //ISPSLIB DD DSN=ISP.SISPSLIB, // DISP=SHR //*SPTLIB DD DSN=SYS1.ISRTLIB, //* DISP=SHR //ISPTLIB DD DSN=ISP.SISPTENU, // DISP=SHR
Figure 78. PR Job Created by ERMT Tool (Part 1 of 6)
110
//********************************************************************* //SLRTABL DD DSN=TI3101.SLRTABL, // DISP=SHR // DD DSN=SLR.V3R3M1.SLRTABL, // DISP=SHR //********************************************************************* //ISPPROF DD DSN=&&ISPFTEMP, // DISP=(NEW,PASS), // UNIT=SYSDA, // SPACE=(TRK,(1,1,10)), // DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3120) //********************************************************************* //ERMTF1 DD DSN=TI3101A.ERMT.FILE1A, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * ISPSTART CMD(%DRLEARM1 1 U MAURO) //********************************************************************* //* //* EXTRACT DATA SET AND MEMBER NAMES FOR VIEW DEFINITIONS //* FROM SLRCLIST //* //********************************************************************* //STEP3 EXEC PGM=IKJEFT01, // DYNAMNBR=25, // COND=(0,NE), // REGION=6M //********************************************************************* //SYSPROC DD DSN=TME10PRF.SDRLEXEC, // DISP=SHR //********************************************************************* //ERMTF4 DD DSN=TI3101A.ERMT.FILE4A, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //VSOURCE DD DSN=TI3101.SLRCLIST, // DISP=SHR // DD DSN=SLR.V3R3M1.SLRCLIST, // DISP=SHR //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * %DRLEARM2 1 VSOURCE //********************************************************************* //* //* EXTRACT SLR TABLE AND COLUMN INFORMATION. //* EXTRACT SLR VIRTUAL COLUMN CALCULATIONS (COMPCOLS). //* EXTRACT SLR ACCESS, LOCKUP AND DATACOL FOR VIEWS. //*
111
//********************************************************************* //STEP4 EXEC PGM=IKJEFT01, // DYNAMNBR=25, // COND=(0,NE), // REGION=6M //********************************************************************* //STEPLIB DD DSN=SLR.V3R3M1.LINKLIB, // DISP=SHR // DD DSN=ISP.SISPLOAD, // DISP=SHR //* DD DSN=SYS1.ISRLOAD, //* DISP=SHR //********************************************************************* //SYSPROC DD DSN=TME10PRF.SDRLEXEC, // DISP=SHR //********************************************************************* //*SPPLIB DD DSN=SYS1.ISRPENU, //* DISP=SHR //ISPPLIB DD DSN=ISP.SISPPENU, // DISP=SHR //*SPMLIB DD DSN=SYS1.ISRMENU, //* DISP=SHR //ISPMLIB DD DSN=ISP.SISPMENU, // DISP=SHR //*SPSLIB DD DSN=SYS1.ISRSENU, //* DISP=SHR //ISPSLIB DD DSN=ISP.SISPSLIB, // DISP=SHR //*SPTLIB DD DSN=SYS1.ISRTLIB, //* DISP=SHR //ISPTLIB DD DSN=ISP.SISPTENU, // DISP=SHR //********************************************************************* //ISPPROF DD DSN=&&ISPFTEMP, // DISP=(NEW,PASS), // UNIT=SYSDA, // SPACE=(TRK,(1,1,10)), // DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3120) //********************************************************************* //LOAD DD DSN=TI3101.SLRSAMP, // DISP=SHR // DD DSN=SLR.V3R3M1.SLRSAMP, // DISP=SHR // DD DSN=SLR.V3R3M1.LINKLIB, // DISP=SHR //********************************************************************* //SORTLIB DD DSN=SYS1.SORTLIB, // DISP=SHR //********************************************************************* //SYSOUT DD DUMMY //OUT DD SYSOUT=* //DUMP DD SYSOUT=* //********************************************************************* //MAINFILE DD DSN=SLR.V3R3M1.REPORTDB, // DISP=SHR //********************************************************************* //TSOURCE DD DSN=TI3101.SLRASM, // DISP=SHR
112
// DD DSN=SLR.V3R3M1.SLRASM, // DISP=SHR //********************************************************************* //ERMTF1 DD DSN=TI3101A.ERMT.FILE1A, // DISP=SHR //********************************************************************* //ERMTF2 DD DSN=TI3101A.ERMT.FILE2A, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //ERMTF3 DD DSN=TI3101A.ERMT.FILE3A, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //ERMTF3B DD DSN=TI3101A.ERMT.FILE3B, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //ERMTF4 DD DSN=TI3101A.ERMT.FILE4A, // DISP=SHR //********************************************************************* //ERMTF5 DD DSN=TI3101A.ERMT.FILE5A, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //* CROSSREF DATA SET FROM TOOLS DISK * //* DD-NAME MUST BE CRS * //********************************************************************* //* CRS DD DSN=TI3101A.ERMT.SLR2EPDM, //* DISP=SHR //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * ISPSTART CMD(%DRLEARM3 1) //********************************************************************* //* //* CONSOLIDATE ALL EXTRACTED INFO INTO ONE FILE //* //********************************************************************* //STEP5 EXEC PGM=IKJEFT01, // DYNAMNBR=25, // COND=(0,NE), // REGION=6M //********************************************************************* //SYSPROC DD DSN=TME10PRF.SDRLEXEC, // DISP=SHR //*********************************************************************
113
//ERMTF1 DD DSN=TI3101A.ERMT.FILE1A, // DISP=SHR //********************************************************************* //ERMTF2 DD DSN=TI3101A.ERMT.FILE2A, // DISP=SHR //********************************************************************* //ERMTF3 DD DSN=TI3101A.ERMT.FILE3A, // DISP=SHR //********************************************************************* //ERMTF5 DD DSN=TI3101A.ERMT.FILE5A, // DISP=SHR //********************************************************************* //ERMTF6 DD DSN=TI3101A.ERMT.FILE6A, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,(5,5),RLSE), // DCB=(RECFM=VB,LRECL=255,BLKSIZE=6160) //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * %DRLEARM4 1 //********************************************************************* //* //* CREATE "DEFINE GROUP" AND "DEFINE REPORT" COMMANDS //* //********************************************************************* //STEP6 EXEC PGM=IKJEFT01, // DYNAMNBR=25, // COND=(0,NE), // REGION=6M //********************************************************************* //SYSPROC DD DSN=TME10PRF.SDRLEXEC, // DISP=SHR //********************************************************************* //ERMTF1 DD DSN=TI3101A.ERMT.FILE1A, // DISP=SHR //********************************************************************* //ERMTF6 DD DSN=TI3101A.ERMT.FILE6A, // DISP=SHR //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * %DRLEARM5 1,+ TME10PRU.LOCAL.DEFS,+ TESTSUMR,+ TXT,+ "TESTSUM_REP",+ "TESTSUM REPORT MIGRATED FROM SLR",+ "",+ "",+ "" //********************************************************************* //* //* CREATE SQL QUERIES AND QMF FORMS //* //*********************************************************************
114
//STEP7 EXEC PGM=IKJEFT01, // DYNAMNBR=25, // COND=(0,NE), // REGION=6M //********************************************************************* //SYSPROC DD DSN=TME10PRF.SDRLEXEC, // DISP=SHR //********************************************************************* //ERMTF3B DD DSN=TI3101A.ERMT.FILE3B, // DISP=SHR //********************************************************************* //ERMTF6 DD DSN=TI3101A.ERMT.FILE6A, // DISP=SHR //********************************************************************* //* CROSSREF DATA SET FROM TOOLS DISK * //* DD-NAME MUST BE CRS * //********************************************************************* //* CRS DD DSN=TI3101A.ERMT.SLR2EPDM, //* DISP=SHR //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * %DRLEARM6 1 TME10PRU.LOCAL.DEFS TXT //********************************************************************* //* //* DELETE WORK FILES //* //********************************************************************* //STEP8 EXEC PGM=IEFBR14, // COND=(0,NE), // REGION=2M //********************************************************************* //ERMTF1 DD DSN=TI3101A.ERMT.FILE1A, // DISP=(OLD,DELETE,DELETE) //********************************************************************* //ERMTF2 DD DSN=TI3101A.ERMT.FILE2A, // DISP=(OLD,DELETE,DELETE) //********************************************************************* //ERMTF3 DD DSN=TI3101A.ERMT.FILE3A, // DISP=(OLD,DELETE,DELETE) //********************************************************************* //ERMTF3B DD DSN=TI3101A.ERMT.FILE3B, // DISP=(OLD,DELETE,DELETE) //********************************************************************* //ERMTF4 DD DSN=TI3101A.ERMT.FILE4A, // DISP=(OLD,DELETE,DELETE) //********************************************************************* //ERMTF5 DD DSN=TI3101A.ERMT.FILE5A, // DISP=(OLD,DELETE,DELETE) //********************************************************************* //ERMTF6 DD DSN=TI3101A.ERMT.FILE6A, // DISP=(OLD,DELETE,DELETE)
4. Check the output for the return codes of each step. They all should be zero (RC=00).
115
The job results will be found in the data set defined in the Performance Reporter report library field as shown in Figure 76 on page 107. In this example, it is TME10PRU.LOCAL.DEFS. For this example, there are three elements (members in the data set) created as shown in the ISPF browse panel in Figure 84. The three members are: TESTSUMR TXTFA001 TXTQA001 Is the object to be run in order to create the group and the report in Performance Reporter. Is the QMF Form used with the SQL queries to produce the report. Is the element containing the SQL queries based on the Service Level Reporter commands for the report being migrated. Our example was shown in Figure 70 on page 102.
BROWSE TME10PRU.LOCAL.DEFS Command ===> Name Prompt VV MM _________ ........ _________ ........ _________ TESTSUMR _________ TXTFA001 _________ TXTQA001 _________ ........ _________ ........
Changed
Size
In
Figure 84. Element Created in Local.DEFS after the Migration Job
5. You need to make slight modifications to the TESTSUMR and TXTQA001 members in order to run the migration without errors. Figure 85 on page 117 shows the TESTSUMR element as it was created from the report migration dialog. Figure 86 on page 117 shows the TESTSUMR member after the modifications to correct the ATTRIBUTES statement that was not generated completely by the tool.
116
/**********************************************************************/ /* */ /* Group definitions created 7 Dec 1998 14:34:13 */ /* */ /**********************************************************************/ DEFINE GROUP "TESTSUM_REP" DESC TESTSUM REPORT MIGRATED FROM SLR; DROP REPORT TESTSUM_01 ; /**********************************************************************/ /* */ /* Report definitions created 7 Dec 1998 14:34:13 */ /* */ /**********************************************************************/ /**********************************************************************/ /* TESTSUM_01 A001 TESTSUM */ /**********************************************************************/ DEFINE REPORT TESTSUM_01 DESC Report for migration test TESTSUM table QUERY TXTQA001 FORM TXTFA001 ATTRIBUTES , DAILY, MONTHLY GROUPS "TESTSUM_REP" ;
Figure 85. Contents of Member TESTSUMR before Modification
/**********************************************************************/ /* */ /* Group definitions created 7 Dec 1998 14:34:13 */ /* */ /**********************************************************************/ DEFINE GROUP "TESTSUM_REP" DESC TESTSUM REPORT MIGRATED FROM SLR; DROP REPORT TESTSUM_01 ; /**********************************************************************/ /* */ /* Report definitions created 7 Dec 1998 14:34:13 */ /* */ /**********************************************************************/ /**********************************************************************/ /* TESTSUM_01 A001 TESTSUM */ /**********************************************************************/ DEFINE REPORT TESTSUM_01 DESC Report for migration test TESTSUM table QUERY TXTQA001 FORM TXTFA001 ATTRIBUTES HOURLY -- <=== Changed GROUPS "TESTSUM_REP" ;
Figure 86. Contents of Member TESTSUMR after Modification
117
Figure 87 shows the TXTQA001 member and the SQL statements generated by the report migration dialog. Figure 88 on page 119 shows the TXTQA001 element after the modification to: Define the appropriate table name (TESTSUM_H) against which the report should be run Modify the DATE statement to work correctly. In this example, the SQL query member was modified so that the report would extract the desired information. This was accomplished by changing the statement from AND DATE = &DATE to AND MONTH(DATE)=05 to report on data for the month of May.
--Created 98/12/07 14:34 -TESTSUM_01 Report for migration test TESTSUM table -SELECT DATE , -- COL YEAR SYSID , -USERID , -DEPT , -SUM(CPU) , -SUM(KBYTES) , -SUM(PRNT) , -SUM(RESP) , -SUM(TRNS) -FROM &PREFIX.TESTSUM -- SLR SUMMARY TESTSUM WHERE -- (MONTH = MAY) -- AND (DAY ^= TOT) (DEPT = SYS SUPP) -- AND(SYSID ^= TOT) -- AND (USERID ^= TOT) AND DATE = &DATE GROUP BY DATE, SYSID, USERID, DEPT
Figure 87. Contents of Member TXTQA001 before Modification
118
--Created 98/12/07 14:34 -TESTSUM_01 Report for migration test TESTSUM table -SELECT DATE , -- COL YEAR SYSID , -USERID , -DEPT , -SUM(CPU) , -SUM(KBYTES) , -SUM(PRNT) , -SUM(RESP) , -SUM(TRNS) -FROM &PREFIX.TESTSUM_H -- SLR SUMMARY TESTSUM <=== Changed WHERE -- AND (DAY ^= TOT) (DEPT = SYS SUPP) -- AND(SYSID ^= TOT) -- AND (USERID ^= TOT) -- AND DATE = &DATE -- <==== Changed AND MONTH(DATE) = 05 -- <==== Changed GROUP BY DATE, SYSID, USERID, DEPT
Figure 88. Contents of Member TXTQA001 after Modification
6. Define the report group and related reports to Performance Reporter. To do this, you execute the modified TESTSUMR member. From the Administration panel, open the Other pull-down from the action bar area of the panel as shown in Figure 89 on page 120. Select 5. Process Performance Reporter Statements from the Other pull-down. The Process Performance Reporter Statements window will be displayed as shown in Figure 90 on page 120. Enter the information about the member to be processed on the Process Performance Reporter Statements window as shown in Figure 90.
Note
For the Type of Statements value 2. Report definition has been selected for processing statements to define report objects. Press the F5=Execute PF-key to execute the TESTSUMR statements.
119
The results of this process for the example TESTSUMR are shown in Figure 91 on page 121
Figure 89. Other Pull-down from Main Administration Panel
Figure 90. Process PR Statements Panel
120
Figure 91. Report Installation Output
On the Performance Reporter Report window shown in Figure 92, you will find the report that was defined in Step 6. on page 119. To run this report, select it from the Report window and press Enter. In our example, the report TESTSUM_01 is selected from the Report window as shown in Figure 92. Performance Reporter will produce a report as shown in Figure 93 on page 122.
121
Figure 92. Reports Windows
Figure 93. Report View
The data in the CPU,KBYTES,PRNT, and RESP columns in the Performance Reporter report shown in Figure 93 on page 122 are not displayed correctly as indicated in some of the rows of the report by the string of "******". This can be corrected using the Performance Reporter Form definition. To adjust the form definition, press the F9=Form PF-key.
122
The FORM panel (in this example, QMF is being used) shown in Figure 94 is displayed.
Figure 94. Form Panel (Part 1 of 2)
Figure 95. Form Panel (Part 2 of 2)
Scroll down by pressing the F8=Forward until the EDIT values for the incorrectly displayed columns are found. Change the EDIT values for these
123
columns to the correct values. In this example, the EDIT value should be L instead of L2.
NOTE NOTE
Refer to the Performance Reporter for OS/390 Guide to Reporting Dialog (SH19-6842), Chapter 7 on how to modify a form for a report.
When you have completed the alterations to the form definition, press the F12=Report PF-key to view the altered report. For this example, the new format of the report is shown in Figure 96 on page 124. You should save the corrected form definition. To save the form with the same name, you must enter the following command on the command line of the report view panel: Save Form as TXTFA001
Figure 96. Report Output (Part 1 of 2)
124
Figure 97. Report Output (Part 2 of 2)
NOTE
Compare the migrated Performance Reporter report output (in our example, Figure 96 on page 124) with the Service Level Reporter report output (in our example, Figure 71 on page 102). You may need to modify the SQL query and/or the form as was done in this example. You may want to add your report group to a component. In this example, the report group and the report migrated were added to the slr2pr mig sample component created in 4.2, Component Creation on page 67 as follows: 1. From the Administration window select 2 .Components and press Enter. The Component window shown in Figure 98 is displayed.
125
Figure 98. Component Panel
2. Select the component and press Enter. A list of the objects belonging to the selected component (in this example, slr2pr mig sample component) will be displayed on the ...Component window as shown in Figure 49 on page 78. 3. Press the F5=Add obj PF-key to add the new object to the component. The Add Object window, as shown in Figure 99, will be displayed.
Figure 99. Add Objects to a Component (Part 1 of 2)
126
4. To add the report group to the component, enter the information about the report on the Add Object window and press Enter. In this example, to add the report group TESTSUM_REP the following information is entered as shown in Figure 99: Object name Object type Member name TESTSUM_REP - for the report group name that will be displayed on the ...Component window. 9 - to indicate this definition is for a Report Group TESTSUMR - for member name containing the Performance Reporter statements that were executed in Step 6. on page 119. TESTSUM REPORT MIGRATED FROM SLR - will be displayed on the Report window.
Part description
5. To add the report to the component, enter the information about the report on the Add Object window and press Enter. In this example, to add the report TESTSUM_01 the following information is entered as shown in Figure 100 on page 128: Object name Object type Member name Part description TESTSUM_01 - for the report name that will be displayed on the ...Component window. 10 - to indicate this definition is for a Report. TESTSUMR - for member name containing the Performance Reporter statements. Report for migration test TESTSUM table - will be displayed on the Report window.
127
Figure 100. Add Objects to a Component (Part 2 of 2)
6. When you have completed entering information about the objects you want to add to the component, press the F12=Cancel PF-key to exit from the Add Object window. You will return to the ...Component window, and the new objects you added to the component will be listed. For this example the new objects TESTSUM_REP and TESTSUM_01 are shown on the SLR2PRSA Component window in Figure 102 on page 129. If you choose to define a component using the alternative method as described on page 78, you must modify the member used to define your component in hlq.LOCAL.DEFS. In this example, the statements shown in Figure 101 were appended to the member DRLIMS2P and executed using the process described on page 79.
/**********************************************************************/ /* Report and report group definitions */ /**********************************************************************/ SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,REPGROUP,TESTSUM_REP,TESTSUMR); SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS (COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME) VALUES(SLR2PRSA,REPORT ,TESTSUM_01,TESTSUMR);
Figure 101. Append to Member DRLIMS2P in hlq.LOCAL.DEFS
128
Note
By having added the definitions for the report group and report to the component, you will be able to de-install and install the component at any time in the future, and all the objects belonging to it will be handled correctly. This will save you from having to manually perform any of the steps associated with setting up the migrated definitions when, or if, you decide to remove and reinstall the migrated definitions.
SLR2PRSA Component Select an object. Then press Enter to Edit definition. Description . . . . . slr2pr mig sample component Installation time . : 1998-11-23-19.34.13 Installed by . . . . : TI3101B / _ _ _ _ _ _ _ _ _ _ _ _ Object Name DRLSEXMP EXAMPLEH SAMPARM1 TEST_1 TESTSUM_D TESTSUM_D_M TESTSUM_H TESTSUM_H_D TESTSUM_M TESTSUM_REP TESTSUM_01 TESTSUM_01_H Object Type TABSPACE LOG LOOKUP RECORD TABLE UPDATE TABLE UPDATE TABLE REPGROUP REPORT UPDATE Member DRLSS001 DRLLS001 DRLTS001 DRLRS001 DRLTS001 DRLTS001 DRLTS001 DRLTS001 DRLTS001 TESTSUMR TESTSUMR DRLTS001 Part
Row 1 from 12
Command ===> ______________________________________________________________ F1=Help F2=Split F3=Exit F4=Exclude F5=Add obj F7=Bkwd F8=Fwd F9=Swap F10=View F11=Delete F12=Cancel
Figure 102. Component List Panel
129
130
Chapter 7. Miscellaneous Items

This chapter covers other activities associated with the migration process.
7.1 Setting Purge Conditions

Purge conditions are used to tell Performance Reporter when redundant data should be removed from the tables. You can use the administration dialog to modify the purge condition of a table.
Note:
1. A table can have only one purge condition. 2. Purge conditions are supplied for all data tables. Pre-defined tables have default conditions, change them as required. For newly created user-defined tables, the conditions will be blank. Again, insert your own values as required. To display and edit the purge conditions of tables: 1. From the Tables window (Figure 103 on page 132), select the table(s) to update and press the F6=PurCond pf-key. Performance Reporter displays the Retention Period for... window shown in Figure 104 on page 132.
131
Figure 103. PR Tables Window
Figure 104. Retention Period Window
To modify a purge condition on the Retention Period for... window (Figure 104 on page 132):
132
1. Modify the Retention Period. The column is the date or timestamp column that Performance Reporter uses to determine the age of the rows. 2. To display the full purge condition, press the F5=Cond pf-key. The Purge Condition window (Figure 105 on page 133) is shown and purge (SQL condition...) statement is displayed. Modify the SQL statement as required and press Enter to save and return to the Retention Period for... window.
Figure 105. Purge Condition Window
3. Press Enter on the Retention Period for... window and Performance Reporter saves the changes and returns to the Tables window.
Miscellaneous Items
133
Note
Purge may be on information other than date or timestamp values. For example, the purge condition could be set on: MVS ABEND codes you no longer wish to track. User IDs you no longer wish to track. Address spaces you do not wish to report on. Purge can also be set conditionally if you need to keep certain rows longer than others. You may, for instance, want to keep data pertaining to certain departments longer than others or statistics based on different work groups longer than others. Figure 106 on page 134 shows an example of a modified purge condition statement with conditions pertaining to variables other than date or timestamp.
Figure 106. Purge Condition Window Showing Conditional Purge Conditions
7.2 Executing Purge Conditions

You can execute your purge condition statements either in batch or online.
7.2.1 Online Purge

To invoke the on-line purge of redundant data from tables:
134
1. From the Tables window, select the table(s) you want to purge. In the example shown in Figure 107 on page 135, tables TESTSUM_D and TESTSUM_H have been selected. 2. Put your cursor on the Utilities pull-down on the action bar and press Enter. 3. Select 9. Purge and press Enter to invoke the on-line purge.
Figure 107. Online Purge Example
The Confirmation window will be displayed, asking you to confirm the purge. Press Enter to confirm. You will need to confirm purge for each table selected. The purge will be initiated, and purge status information will be displayed on completion of the task.
7.2.2 Batch Purge

You can also run batch jobs to purge redundant data. This is a recommended approach to follow as these jobs can be automated. Sample JCL for a purge job can be found in the member DRLJPURG in the hlq.SDRLCNTL dataset. Figure 108 on page 136 shows the non-comment cards from the DRLJPURG job.
Miscellaneous Items
135
Figure 108. Non-comment Cards from DRLJPURG Job
Before running the job, check the following in Table 6 on page 136:
Table 6. DRLJPURG Parameters to Check
ITEM
DESCRIPTION DB2 Subsystem Name Prefix for Performance Reporter System Tables for the Database Whose Tables are to be Purged Performance Reporter Load Library DB2 Load Library
SYSTEM=DSN SYSPREFIX=DRLSYS
DSN=DRL130.SDRLLOAD DSN=DSN230.DSNLOAD
You can also specify inclusion or exclusion of tables on the purge statement. For example, to include all tables with names starting with TESTSUM having DRL as their owner for the purge, use: PURGE INCLUDE DRL.TESTSUM%; To exclude table TESTSUM_M having DRL as its owner, use: PURGE EXCLUDE DRL.TESTSUM_M;
7.3 Parallel Collection

It is not possible to suggest any fixed timeframe for parallel collection of data to Service Level Reporter and Performance Reporter. Each installation and their policies would differ in this regard. Suffice to say, parallel collection should be used until such time as you are comfortable that Performance Reporter is affording you the information you want to derive from it before discontinuing the parallel collection.
136
Appendix A. The Key to Predefined Migration - DLRMIGRATION

This appendix provides a cross reference list for the Service Level Reporter product areas and the corresponding Performance Reporter components as determined in the DB2 table DRLSYS.DRLMIGRATION. Performance Reporter uses the DRLMIGRATION table to cross reference information about Service Level Reporter tables and Performance Reporter tables. In addition, the members of the hlq.SDRLDEFS data set contain control statements that will be used by the migration dialog to preform the migration of predefined Service Level Reporter tables and data to Performance Reporter.
A.1 Viewing DLRMIGRATION

You can view the information in DRLSYS.DLRMIGRATION by using a DB2 utility program such as SPUFI. The SQL statements to list the contents of the DRLMIGRATION table are:
SET CURRENT SQLID = DRLSYS; SELECT * FROM DRLMIGRATION ;
Figure 109 on page 141 shows the result of the above query. The columns in the DRLMIGRATION table and the meaning of the information in them are shown in Table 7.
Table 7. DRLMIGRATION Table Values
Column Name TABLE_NAME DATA_BASE
Contents The name of the Performance Reporter table into which predefined Service Level Reporter data will be migrated. The name of the Service Level Reporter data base where the Performance Reporter migration tool expects to find the data to be migrated. The name of the Service Level Reporter table or tables where the Performance Reporter migration utility expects to find the data to be migrated. The name of the member in the hlq.SDRLDEFS data set that contains the control statements that will be used to unload the data from the first Service Level Reporter table in the SLR_TABLES column.
SLR_TABLES
UNLOAD_MEMBER1
137
Column Name INSERT_MEMBER1
Contents The name of the member in the hql.SDRLDEFS data set that contains the insert statements that will be used to load the unloaded data from the first table noted in the SLR_TABLES column into the Performance Reporter tables named in TABLE_NAMES. The name of the member in the hlq.SDRLDEFS data set that contains the control statements that will be used to unload the data from the second Service Level Reporter table in the SLR_TABLES column. The name of the member in the hql.SDRLDEFS data set that contains the insert statements that will be used to load the unloaded data from the second table noted in the SLR_TABLES column into the Performance Reporter tables named in TABLE_NAMES. The name of the member in the hlq.SDRLDEFS data set that contains the control statements that will be used to unload the data from the third Service Level Reporter table in the SLR_TABLES column. The name of the member in the hql.SDRLDEFS data set that contains the insert statements that will be used to load the unloaded data from the third table noted in the SLR_TABLES column into the Performance Reporter tables named in TABLE_NAMES. The name of the member in the hql.SDRLDEFS data set that contains additional statements to process to complete the population of Performance Reporter tables with data being migrated into the Performance Reporter table named in TABLE_NAMES. Examples of statements that could be processed would be a recalculate of data in the table named in TABLES_NAMES or to copy the data to other tables.
UNLOAD_MEMBER2
INSERT_MEMBER2
UNLOAD_MEMBER3
INSERT_MEMBER3
LOGCOL_MEMBER
Each row in the DRLMIGRATION table represents one Performance Reporter table into which predefined Service Level Reporter table data will be migrated. The information in a row of the table is what the Performance Reporter migration dialog and utility uses to locate the data to be migrated
138
and the control statements to be used to unload the data from SLR and how to insert it into the designated Performance Reporter table.
Table 8. MVS_ADDRSPACE_H Contents
DRLMIGRATION Column Name TABLE_NAME DATA_BASE SLR_TABLES UNLOAD_MEMBER1 INSERT_MEMBER1 UNLOAD_MEMBER2 INSERT_MEMBER2 UNLOAD_MEMBER3 INSERT_MEMBER3 LOGCOL_MEMBER
Information in Row MVS_ADDRSPACE_M SYSTEMDB ADDRSTAT, JOBSTAT, TSOSTAT DRLW0630 DRLWMVAS DRLW0720 DRLWMVAT DRLW0750 DRLWMVAU
For example, one of the rows in DRLMIGRATION contains the information shown in Table 8. The Performance Reporter dialog and migration utility use this information to: 1. The Performance Reporter dialog has information on how to migrate data from the three Service Level Reporter tables (ADDRSTAT, JOBSTAT, TSOSTAT) into the Performance Reporter MVS_ADDRSPACE_M table. 2. The unload data from the Service Level Reporter table ADDRSTAT will be controlled by the statements in DRLW0630, and the inserting of this data into MVS_ADDRSPACE_M will be controlled by the statements in DRLWMVAS. 3. The unload data from the Service Level Reporter table JOBSTAT will be controlled by the statements in DRLW0720, and the inserting of this data into MVS_ADDRSPACE_M will be controlled by the statements in DRLWMVAT. 4. The unload data from the Service Level Reporter table TSOSTAT will be controlled by the statements in DRLW0750, and the inserting of this data into MVS_ADDRSPACE_M will be controlled by the statements in DRLWMVAU.
The Key to Predefined Migration - DLRMIGRATION
139
5. There are no additional control statements to be processed for the data being migrated to the Performance Reporter MVS_ADDRSPACE_M table.
140
Figure 109. DRLMIGRATION Table Contents
141
A.2 DRLMIGRATION Values

This section contains the information from the DRLSYS.DRLMIGRATION table that you can reference if you do not want to list the values contained in the table as described in Appendix A.1, Viewing DLRMIGRATION on page 137. A.2.1 MVS_SYSTEM_M Table 9 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_SYSTEM_M.
Table 9. MVS_SYSTEM_M
Information in Row MVS_SYSTEM_M SYSTEMDB PAGESUM/CPULOAD/WORKLOAD, CPULOAD/IPLSUM DRLW0790 DRLWMVSY DRLW0780 DRLWMVS1
A.2.2 MVS_ADDRSPACE_M Table 10 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_ADDRSPACE_M.
Table 10. MVS_ADDRSPACE_H
DRLMIGRATION Column Name TABLE_NAME DATA_BASE SLR_TABLES
Information in Row MVS_ADDRSPACE_M SYSTEMDB ADDRSTAT, JOBSTAT, TSOSTAT
142
DRLMIGRATION Column Name UNLOAD_MEMBER1 INSERT_MEMBER1 UNLOAD_MEMBER2 INSERT_MEMBER2 UNLOAD_MEMBER3 INSERT_MEMBER3 LOGCOL_MEMBER
Information in Row DRLW0630 DRLWMVAS DRLW0720 DRLWMVAT DRLW0750 DRLWMVAU
A.2.3 MVS_ADDRDISTR_M Table 11 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_ADDRDISTR_M.
Table 11. MVS_ADDRDISTR_M
Information in Row MVS_ADDRDISTR_M SYSTEMDB ADDRDISTR DRLW0640 DRLWMVAD
143
A.2.4 MVS_PROGRAM_M Table 12 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_PROGRAM_M.
Table 12. MVS_PROGRAM_M
Information in Row MVS_PROGRAM_M SYSTEMDB PGMSTAT DRLW0730 DRLWMVPG
A.2.5 MVS_COMPCODE_M Table 13 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_COMPCODE_M.
Table 13. MVS_COMPCODE_M
DRLMIGRATION Column Name TABLE_NAME DATA_BASE SLR_TABLES UNLOAD_MEMBER1 INSERT_MEMBER1 UNLOAD_MEMBER2 INSERT_MEMBER2 UNLOAD_MEMBER3
Information in Row MVS_COMPCODE_M SYSTEMDB COMPCODE DRLW0740 DRLWMVCC
144
DRLMIGRATION Column Name INSERT_MEMBER3 LOGCOL_MEMBER
Information in Row
A.2.6 MVS_WORKLOAD_M Table 14 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_WORKLOAD_M.
Table 14. MVS_WORKLOAD_M
Information in Row MVS_WORKLOAD_M SYSTEMDB WORKLOAD DRLW07A0 DRLWMVWO
A.2.7 MVS_PRINTER_M Table 15 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_PRINTER_M.
Table 15. MVS_PRINTER_M
DRLMIGRATION Column Name TABLE_NAME DATA_BASE SLR_TABLES UNLOAD_MEMBER1
Information in Row MVS_PRINTER_M SYSTEMDB PRINTLOAD DRLW0760
145
DRLMIGRATION Column Name INSERT_MEMBER1 UNLOAD_MEMBER2 INSERT_MEMBER2 UNLOAD_MEMBER3 INSERT_MEMBER3 LOGCOL_MEMBER
Information in Row DRLWMVPT
A.2.8 MVS_TAPE_M Table 16 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_TAPE_M.
Table 16. MVS_TAPE_M
Information in Row MVS_TAPE_M SYSTEMDB TAPESTAT DRLW07E0 DRLWMVTA
146
A.2.9 MVS_IPL_T Table 17 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MVS_IPL_T.
Table 17. MVS_IPL_T
Information in Row MVS_IPL_T SYSTEMDB IPLLOG DRLW2022 DRLWMVIL
A.2.10 AVAILABILITY_M Table 18 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table AVAILABILITY_M.
Table 18. AVAILABILITY_M
Information in Row AVAILABILITY_M SYSTEMDB AVAILSTAT DRLW0890 DRLWAVAI
147
Information in Row
A.2.11 DFSMS_DATASET_D/M Table 19 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_DATASET_D/M.
Table 19. DFSMS_DATASET_D/M
Information in Row DFSMS_DATASET_D/M SYSTEMDB DASD_DSNSTAT DRLW0E3B DRLWDFDA
DRLWDFDX
A.2.12 DFSMS_VOLUME_D/M Table 20 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_VOLUME_D/M.
Table 20. DFSMS_VOLUME_D/M
Information in Row DFSMS_VOLUME_D/M SYSTEMDB DASD_VOLSTAT DRLW0E3A
148
Information in Row DRLWDFVO
DRLWDFVX
A.2.13 DFSMS_BACKUP_D/M Table 21 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_BACKUP_D/M.
Table 21. DFSMS_BACKUP_D/M
Information in Row DFSMS_BACKUP_D/M SYSTEMDB HSM_BCKUPSUM DRLW0E3C DRLWDFBA
DRLWDFBX
149
A.2.14 DFSMS_MIGRATION_D/M Table 22 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_MIGRATION_D/M.
Table 22. DFSMS_MIGRATION_D/M
Information in Row DFSMS_MIGRATION_D/M SYSTEMDB HSM_MIGR_SUM DRLW0E3D DRLWDFMI
DRLWDFMX
A.2.15 DFSMS_DASD_CAP_D/M Table 23 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_DASD_CAP_D/M.
Table 23. DFSMS_DASD_CAP_D/M
Information in Row DFSMS_DASD_CAP_D/M SYSTEMDB HSM_DASD_SUM DRLW0E3E DRLWDFDC
150
Information in Row
DRLWDFDY
A.2.16 DFSMS_TAPE_CAP_D/M Table 24 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DSFMS_TAPE_CAP_D/M.
Table 24. DFSMS_TAPE_CAP_D/M
Information in Row DFSMS_TAPE_CAP_D/M SYSTEMDB HSM_TAPE_SUM DRLW0E3F DRLWDFTC
DRLWDFTX
A.2.17 DFSMS_ACTIVITY_M Table 25 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table
Table 25. DFSMS_ACTIBVITY_M
Information in Row DFSMS_ACTIVITY_M SYSTEMDB HSM_BKUP_ACT, HSM_MIGR_ACT DRLW0E38
151
Information in Row DRLWDFA1 DRLW0E39 DRLWDFA2
A.2.18 DFSMS_LAST_RUN Table 26 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_LAST_RUN.
Table 26. DFSMS_LAST_RUN
Information in Row DFSMS_LAST_RUN SYSTEMDB DASD_CTLPARM DRLW0E32 DRLWDFLR
152
A.2.19 DFSMS_MIGRATE_DAYS Table 27 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_MIGRATE_DAYS.
Table 27. DFSMS_MIGRATE_DAYS
Information in Row DFSMS_MIGRATE_DAYS SYSTEMDB DASD_MGTPARM DRLW0E33 DRLWDFMD
A.2.20 DFSMS_DS_OWNER Table 28 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DFSMS_DS_OWNER.
Table 28. DFSMS_DS_OWNER
Information in Row DFSMS_DS_OWNER SYSTEMDB DASD_DSNPARM DRLW0E31 DRLWDFOW
153
Information in Row
A.2.21 DB2_TRANSACTION_W Table 29 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_TRANSACTION_W.
Table 29. DB2_TRANSACTION_W
Information in Row DB2_TRANSACTION_W SYSTEMDB DB2ACCTSUM1/DB2ACCTSUM2 DRLW0B60 DRLWD2T
A.2.22 DB2_USER_TRAN_W Table 30 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_USER_TRAN_W.
Table 30. DB2_USER_TRAN_W
Information in Row DB2_USER_TRAN_W SYSTEMDB DB2ACCTSUM1/DB2ACCTSUM2 DRLW0B60
154
Information in Row DRLWD2UT
A.2.23 DB2_APPL_DIST_W Table 31 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_APPL_DIST_W.
Table 31. DB2_APPL_DIST_W
Information in Row DB2_APPL_DIST_W SYSTEMDB DB2DISTSUM DRLW0B63 DRLWD2DA
155
A.2.24 DB2_USER_AP_DIST_W Table 32 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_USER_AP_DIST_W.
Table 32. DB2_USER_AP_DIST_W
Information in Row DB2_USER_AP_DIST_W SYSTEMDB DB2DISTSUM DRLW0B63 DRLWD2DP
A.2.25 DB2_TRAN_DIST_W Table 33 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_TRAN_DIST_W.
Table 33. DB2_TRAN_W
Information in Row DB2_TRAN_DIST_W SYSTEMDB DB2DISTSUM DRLW0B63 DRLWD2DT
156
Information in Row
A.2.26 DB2_USER_DIST_W Table 34 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_USER_DIST_W.
Table 34. DB2_USER_DIST_W
Information in Row DB2_USER_DIST_W SYSTEMDB DB2DISTSUM DRLW0B63 DRLWD2DU
A.2.27 DB2_APPLICATION_W Table 35 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_APPLICATION_W.
Table 35. DB2_APPLICATION_W
Information in Row DB2_APPLICATION_W SYSTEMDB DB2CAPASUM DRLW0B66
157
Information in Row DRLWD2A
A.2.28 DB2_USER_APPL_W Table 36 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table DB2_USER_APPL_W.
Table 36. DB2_USER_APPL_W
Information in Row DB2_USER_APPL_W SYSTEMDB DB2CAPASUM DRLW0B66 DRLWD2UA
158
A.2.29 EREP_DASD_M Table 37 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table EREP_DASD_M.
Table 37. EREP_DASD_M
Information in Row EREP_DASD_M SYSTEMDB LR_DASD_SUM DRLW0A52 DRLWERDA
A.2.30 EREP_VTAM_M Table 38 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table EREP_VTAM_M.
Table 38. EREP_VTAM_M
Information in Row EREP_VTAM_M SYSTEMDB LR_VTAM_SUM DRLW0A54 DRLWERVT
159
Information in Row
A.2.31 EREP_CPU_ID Table 39 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table EREP_CPU_ID.
Table 39. EREP_CPU_ID
Information in Row EREP_CPU_ID SYSTEMDB LR_CPU_PARM DRLW0A4B DRLWERCI
A.2.32 EREP_DASD_GROUP Table 40 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table EREP_DASD_GROUP.
Table 40. EREP_DASD_GROUP
Information in Row EREP_DASD_GROUP SYSTEMDB LR_DASD_PARM DRLW0A4A
160
Information in Row DRLWERDG
A.2.33 VMACCT_SESSION_M Table 41 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table VMACCT_SESSION_M.
Table 41. VMACCT_SESSION_M
Information in Row VMACCT_SESSION_M SYSTEMDB VMSUM DRLW0A31 DRLWVACT
161
A.2.34 VMPRF_SYSTEM_M Table 42 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table VMPRF_SYSTEM_M.
Table 42. VMPRF_SYSTEM_M
Information in Row VMPRF_SYSTEM_M SYSTEMDB VMPRFSYSSUM DRLW0E51 DRLWVM01
A.2.35 VMPRF_PROCESSOR_M Table 43 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table VMPRF_PROCESSOR_M.
Table 43. VMPRF_PROCESSOR_M
Information in Row VMPRF_PROCESSOR_M SYSTEMDB VMPRFPROCSUM DRLW0E52 DRLWVM02
162
Information in Row
A.2.36 VMPRF_USER_M Table 44 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table VMPRF_USER_M.
Table 44. VMPRF_USER_M
Information in Row VMPRF_USER_M SYSTEMDB VMPRFUSERSUM DRLW0E53 DRLWVM41
A.2.37 VMPRF_DASD_M Table 45 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table VMPRF_DASD_M.
Table 45. VMPRF_DASD_M
Information in Row VMPRF_DASD_M SYSTEMDB VMPRFDASDSUM DRLW0E54
163
Information in Row DRLWVM61
A.2.38 CICS_TRANSACTION_W Table 46 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table CICS_TRANSACTION_W.
Table 46. CICS_TRANSACTION_W
Information in Row CICS_TRANSACTION_W SYSTEMDB CICSTRANSUM DRLW0500 DRLWC101
164
A.2.39 CICS_M_GLOBAL_D Table 47 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table CICS_M_GLOBAL_D.
Table 47. CICS_M_GLOBAL_D
Information in Row CICS_M_GLOBAL_D SYSTEMDB CICSSYSSTAT DRLW0520 DRLWC702
A.2.40 MSG_SYSLOG_TYPE Table 48 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MSG_SYSLOG_TYPE.
Table 48. MSG_SYSLOG_TYPE
Information in Row MSG_SYSLOG_TYPE SYSTEMDB MSGPARM DRLW0E0F DRLWMAMI
165
Information in Row
A.2.41 MSG_SYSLOG_M Table 49 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table MSG_SYSLOG_M.
Table 49. MSG_SYSLOG_M
Information in Row MSG_SYSLOG_M SYSTEMDB MSGSUM DRLW0E11 DRLWMASY
A.2.42 AVAILABILITY_W/M Table 50 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table AVAILABILITY_W/M.
Table 50. AVAILABILITY_W/M
Information in Row AVAILABILITY_W/M NRDB NR_AVAILS DRLW2391
166
Information in Row DRLWNAVW
DRLWNAVM
A.2.43 NW_NPM_UTIL_W Table 51 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_NPM_UTIL_W.
Table 51. NW_NPM_UTIL_W
Information in Row NW_NPM_UTIL_W NRDB NR_NPMUTIS DRLW2366 DRLWNNPM
167
A.2.44 NW_ALERT_BASIC_W Table 52 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_ALERT_BASIC_W.
Table 52. NW_ALERT_BASIC_W
Information in Row NW_ALERT_BASIC_W NRDB NR_ALERTS DRLW2322 DRLWNHAB
A.2.45 NW_ALERT_GENERIC_W Table 53 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_ALERT_GENERIC_W.
Table 53. NW_ALERT_GENERIC_W
Information in Row NW_ALERT_GENERIC_W NRDB NR_GENALERTS DRLW2325 DRLWNHAG
168
Information in Row
A.2.46 NW_SESSION_FAIL_W Table 54 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_SESSION_W.
Table 54. NW_SESSION_W
Information in Row NW_SESSION_FAIL_W NRDB NR_SESSFS DRLW2342 DRLWNSSF
A.2.47 NW_RTM_RESONSE_W/M Table 55 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_RTM_SESONSE_W/M.
Table 55. NW_RTM_RESONSE_W/M
Information in Row NW_RTM_RESONSE_W/M NRDB NR_NVRESPS DRLW2357
169
Information in Row DRLWNRTW
DRLWNRTM
A.2.48 NW_SM_UTIL_W Table 56 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_SM_UTIL_W.
Table 56. NW_SM_UTIL_W
Information in Row NW_SM_UTIL_W NRDB NR_NVSMUTIS DRLW2368 DRLWNMSM
170
A.2.49 NW_NCP_UTIL_W Table 57 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_NCP_UTIL_W.
Table 57. NW_NCP_UTIL_W
Information in Row NW_NCP_UTIL_W NRDB NR_NCPUTIS DRLW2372 DRLWNCP
A.2.50 NW_PU_UTIL_W Table 58 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_PU_UTIL_W.
Table 58. NW_PU_UTIL_W
Information in Row NW_PU_UTIL_W NRDB NR_PUUTIS DRLW2364 DRLWNPU
171
Information in Row
A.2.51 NW_LINE_UTIL_W Table 59 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_LINE_UTIL_W.
Table 59. NW_LINE_UTIL_W
Information in Row NW_LINE_UTIL_W NRDB NR_LINEUTIS DRLW2362 DRLWNLI
A.2.52 NW_NPM_TRANSIT_W/M Table 60 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_NPM_TRANSIT_W/M.
Table 60. NW_NPM_TRANSIT_W/M
Information in Row NW_NPM_TRANSIT_W/M NRDB NR_NPMRESPS DRLW2356
172
Information in Row DRLWNTW
DRLWNTM
A.2.53 NW_X25LN_UTIL_W Table 61 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_X25LN_UTIL_W.
Table 61. NW_X25LN_UTIL_W
Information in Row NW_X25LN_UTIL_W NRDB NR_X25LNKS DRLW2378 DRLWNXLN
173
A.2.54 NW_X25PU_UTIL_W Table 62 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_X25PU_UTIL_W.
Table 62. NW_X25PU_UTIL_W
Information in Row NW_X25PU_UTIL_W NRDB NR_X25PUS DRLW237B DRLWNXPU
A.2.55 NW_X25NI_UTIL_W Table 63 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_X25NI_TUIL_W.
Table 63. NW_X25NI_UTIL_W
Information in Row NW_X25NI_UTIL_W NRDB NR_NPSIVCS DRLW237E DRLWNXNI
174
Information in Row
A.2.56 NW_NTRIP_UTIL_W Table 64 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_NTRIP_UTIL_W.
Table 64. NW_NTRIP_UTIL_W
Information in Row NW_NTRIP_UTIL_W NRDB NR_NTRIPHYS DRLW236B DRLWNIP
A.2.57 NW_NTRIL_UTIL_W Table 65 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_NTRIL_UTIL_W.
Table 65. NW_NTRIL_UTIL_W
Information in Row NW_NTRIL_UTIL_W NRDB NR_NTRILOGS DRLW236E
175
Information in Row DRLWNIL
A.2.58 NW_NEO_UTIL_W Table 66 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table NW_NEO_UTIL_W.
Table 66. NW_NEO_UTIL_W
Information in Row NW_NEO_UTIL_W NRDB NR_NEOS DRLW2376 DRLWNE
176
A.2.59 IMS_TRANSACTION_W Table 67 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table IMS_TRANSACTION_W.
Table 67. IMS_TRANSACTION_W
Information in Row IMS_TRANSACTION_W SYSTEMDB IMSDLI/IMSTRANS, IMSTRANS, IMSFPSUM DRLW0710 DRLWITRA DRLW0700 DRLWITRB DRLW0713 DRLWIFPS
A.2.60 OPC_AUTO_EVENT_M Table 68 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table OPC_AUTO_EVENT_M.
Table 68. OPC_AUTO_EVENT_M
Information in Row OPC_AUTO_EVENT_M SYSTEMDB OPCAUTEVSTAT DRLW0AD4 DRLWOPA
177
Information in Row
A.2.61 OPC_MCP_M Table 69 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table OPC_MCP_M.
Table 69. OPC_MCP_M
Information in Row OPC_MCP_M SYSTEMDB OPCMCPSUM DRLW0AD1 DRLWOPMP
A.2.62 OPC_MISSED_FB_M Table 70 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table OPC_MISSED_FB_M.
Table 70. OPC_MISSED_FB_M
Information in Row OPC_MISSED_FB_M SYSTEMDB OPCFBMSUM DRLW0AD2
178
Information in Row DRLWOPM
A.2.63 OPC_OPER_EVENT_M Table 71 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table OPC_OPER_EVENT_M. OPC_OPER_EVENT_M
Table 71. OPC_OPER_EVENT_M
Information in Row OPC_OPER_EVENT_M SYSTEMDB OPCOPEVSUM DRLW0AD0 DRLWOPOE
179
A.2.64 OPC_OPER_EVENT_T Table 72 shows the information in DRLMIGRATION for the migration of data into the Performance Reporter table OPC_OPER_EVENT_T.
Table 72. OPC_OPER_EVENT_T
Information in Row OPC_OPER_EVENT_T SYSTEMDB OPCOPEVLOG DRLW0AC0 DRLWOPOT
180
Appendix B. Predefined SLR Tables to PR Tables Cross Reference

This appendix lists the Service Level Reporter to Performance Reporter table mapping. Both the Service Level Reporter to Performance Reporter cross reference list, as well as the reverse Performance Reporter to Service Level Reporter list, are provided.
B.1 SLR to PR Cross Reference

Figure 73 lists the Service Level Reporter Version 3 tables alphabetically and the corresponding Performance Reporter table where the predefined Service Level Reporter tables data will be migrated by the Performance Reporter migration utility.
Table 73. Predefined SLR Table to PR Table Cross Reference
Service Level Reporter V3 Table Names ADDRDISTR ADDRSTAT AVAILSTAT
Performance Reporter Table Name MVS_ADDRDISTR_M MVS_ADDRSPACE_M AVAILABILITY_M
Perforformance Reporter Component Required MVS Component MVS Component MVS Component Network Availability Component CICS Monitoring Component CICS Monitoring Component MVS Component MVS Component DFSMS Component DFSMS Component DFSMS Component DFSMS Component DFSMS Component DB2 Component DB2 Component
CICSSYSSTAT CICSTRANSUM COMPCODE CPULOAD DASD_CTLPARM DASD_DSNSTAT DASD_DSNPARM DASD_MGTPARM DASD_VOLSTAT DB2ACCTSUM1 DB2ACCTSUM1
CICS_M_GLOBAL_D CICS_TRANSACTION_W MVS_COMPCODE_M MVS_SYSTEM_M DFSMS_LAST_RUN DFSMS_DATASET_D/M DFSMS_DS_OWNER DFSMS_MIGRATE_DAYS DFSMS_VOLUME_D/M DB2_TRANSACTION_W DB2_USER_TRAN_W
181
Service Level Reporter V3 Table Names DB2ACCTSUM2 DB2ACCTSUM2 DB2CAPASUM DB2CAPASUM DB2DISTSUM DB2DISTSUM DB2DISTSUM DB2DISTSUM HSM_BKUP_ACT HSM_BCKUPSUM HSM_DASD_SUM HSM_MIGR_ACT HSM_MIGR_SUM HSM_TAPE_SUM IMSDLI IMSFPSUM IMSTRANS IPLLOG IPLSUM JOBSTAT LR_CPU_PARM LR_DASD_PARM LR_DASD_SUM LR_VTAM_SUM MSGPARM
Performance Reporter Table Name DB2_TRANSACTION_W DB2_USER_TRAN_W DB2_APPLICATION_W DB2_USER_APPL_W DB2_APPL_DIST_W DB2_TRAN_DIST_W DB2_USER_AP_DIST_W DB2_USER_DIST_W DB2_USER_TRAN_W DFSMS_BACKUP_D/M DFSMS_DASD_CAP_D/M DB2_USER_TRAN_W DFSMS_MIGRATION_D/M DFSMS_TAPE_CAP_D/M IMS_TRANSACTION_W IMS_TRANSACTION_W IMS_TRANSACTION_W MVS_IPL_T MVS_SYSTEM_M MVS_ADDRSPACE_M EREP_CPU_ID EREP_DASD_GROUP EREP_DASD_M EREP_VTAM_M MSG_SYSLOG_TYPE
Perforformance Reporter Component Required DB2 Component DB2 Component DB2 Component DB2 Component DB2 Component DB2 Component DB2 Component DB2 Component DB2 Component DFSMS Component DFSMS Component DB2 Component DFSMS Component DFSMS Component IMS Collect Component IMS Collect Component IMS Collect Component MVS Component MVS Component MVS Component EREP Component EREP Component EREP Component EREP Component Message Analysis/Automation Component
182
Service Level Reporter V3 Table Names MSGSUM
Performance Reporter Table Name MSG_SYSLOG_M
Perforformance Reporter Component Required Message Analysis/Automation Component Network Problem Component Network Availability Component Network Problem Component Network Line Utilization Component Network NCP Utilization Component Network NEO Utilization Component Network NPM Transit Time Component Network NPM Internal Utilization Component Network X25 Utilization Component Network NTRI Utilization Component Network NTRI Utilization Component Network RTM Response Time Component Network NV/SM Internal Utilization Component Network PU Utilization Component
NR_ALERTS NR_AVAILS NR_GENALERTS NR_LINEUTIS NR_NCPUTIS NR_NEOS NR_NPMRESPS NR_NPMUTIS NR_NPSIVCS NR_NTRILOGS NR_NTRIPHYS NR_NVRESPS
NW_ALERT_BASIC_W AVAILABILITY_M NW_ALERT_GENERIC_W NW_LINE_UTIL_W NW_NCP_UTIL_W NW_NEO_UTIL_W NW_NPM_TRANSIT_W/M NW_NPM_UTIL_W NW_X25NI_UTIL_W NW_NTRIL_UTIL_W NW_NTRIP_UTIL_W NW_RTM_RESPONSE_W/M
NR_NVSMUTIS NR_PUUTIS
NW_SM_UTIL_W NW_PU_UTIL_W
Predefined SLR Tables to PR Tables Cross Reference
183
Service Level Reporter V3 Table Names NR_SESSFS NR_X25LNKS NR_X25PUS OPCAUTEVSTAT OPCFBMSUM OPCMCPSUM OPCOPEVLOG OPCOPEVSUM PAGESUM PGMSTAT PRINTLOAD TAPESTAT TSOSTAT VMSUM VMPRFDASDSUM VMPRFPROCSUM VMPRFSYSSUM VMPRFUSERSUM WORKLOAD WORKLOAD
Performance Reporter Table Name NW_SESSION_FAIL_W NW_X25LN_UTIL_W NW_X25PU_UTIL_W OPC_AUTO_EVENT_M OPC_MISSED_FB_M OPC_MCP_M OPC_OPER_EVENT_T OPC_OPER_EVENT_M MVS_SYSTEM_M MVS_PROGRAM_M MVS_PRINTER_M MVS_TAPE_M MVS_ADDRSPACE_M VMACCT_SESSION_M VMPRF_DASD_M VMPRF_PROCESSOR_M VMPRF_SYSTEM_M VMPRF_USER_M MVS_SYSTEM_M MVS_WORKLOAD_M
Perforformance Reporter Component Required Network Session Failure Component Network X25 Utilization Component Network X25 Utilization Component OPC Component OPC Component OPC Component OPC Component OPC Component MVS Component MVS Component MVS Component MVS Component MVS Component VM Accounting Component VMPRF Component VMPRF Component VMPRF Component VMPRF Component MVS Component MVS Component
184
B.2 PR to SLR Cross Reference

Figure 74 lists the Performance Reporter tables alphabetically and the corresponding predefined Service Level Reporter table or tables from where data will be migrated by the Performance Reporter migration utility.
Table 74. PR to Predefined SLR Table Cross Reference
Performance Reporter Table Name AVAILABILITY_M AVAILABILITY_M CICS_M_GLOBAL_D CICS_TRANSACTION_W DB2_APPL_DIST_W DB2_APPLICATION_W DB2_TRAN_DIST_W DB2_TRANSACTION_W DB2_USER_AP_DIST_W DB2_USER_APPL_W DB2_USER_DIST_W DB2_USER_TRAN_W DB2_USER_TRAN_W DFSMS_BACKUP_D/M DFSMS_DASD_CAP_D/M DFSMS_DATASET_D/M DFSMS_DS_OWNER DFSMS_LAST_RUN DFSMS_MIGRATE_DAYS DFSMS_MIGRATION_D/M DFSMS_TAPE_CAP_D/M DFSMS_VOLUME_D/M
Service Level Reporter V3 Table Names AVAILSTAT NR_AVAILS CICSSYSSTAT CICSTRANSUM DB2DISTSUM DB2CAPASUM DB2DISTSUM DB2ACCTSUM1/DB2ACCTSUM2 DB2DISTSUM DB2CAPASUM DB2DISTSUM DB2ACCTSUM1/DB2ACCTSUM2 HSM_BKUP_ACT, HSM_MIGR_ACT HSM_BCKUPSUM HSM_DASD_SUM DASD_DSNSTAT DASD_DSNPARM DASD_CTLPARM DASD_MGTPARM HSM_MIGR_SUM HSM_TAPE_SUM DASD_VOLSTAT
185
Performance Reporter Table Name EREP_CPU_ID EREP_DASD_GROUP EREP_DASD_M EREP_VTAM_M IMS_TRANSACTION_W MSG_SYSLOG_M MSG_SYSLOG_TYPE MVS_ADDRDISTR_M MVS_ADDRSPACE_M MVS_COMPCODE_M MVS_IPL_T MVS_PRINTER_M MVS_PROGRAM_M MVS_SYSTEM_M MVS_TAPE_M MVS_WORKLOAD_M NW_ALERT_BASIC_W NW_ALERT_GENERIC_W NW_LINE_UTIL_W NW_NCP_UTIL_W NW_NEO_UTIL_W NW_NPM_TRANSIT_W/M NW_NPM_UTIL_W NW_NTRIL_UTIL_W NW_NTRIP_UTIL_W NW_PU_UTIL_W
Service Level Reporter V3 Table Names LR_CPU_PARM LR_DASD_PARM LR_DASD_SUM LR_VTAM_SUM IMSDLI/IMSTRANS, IMSTRANS, IMSFPSUM MSGSUM MSGPARM ADDRDISTR ADDRSTAT, JOBSTAT, TSOSTAT COMPCODE IPLLOG PRINTLOAD PGMSTAT PAGESUM/CPULOAD/WORKLOAD, CPULOAD/IPLSUM TAPESTAT WORKLOAD NR_ALERTS NR_GENALERTS NR_LINEUTIS NR_NCPUTIS NR_NEOS NR_NPMRESPS NR_NPMUTIS NR_NTRILOGS NR_NTRIPHYS NR_PUUTIS
186
Performance Reporter Table Name NW_RTM_RESONSE_W/M NW_SESSION_FAIL_W NW_SM_UTIL_W NW_X25LN_UTIL_W NW_X25NI_UTIL_W NW_X25PU_UTIL_W OPC_AUTO_EVENT_M OPC_MCP_M OPC_MISSED_FB_M OPC_OPER_EVENT_M OPC_OPER_EVENT_T VMACCT_SESSION_M VMPRF_DASD_M VMPRF_PROCESSOR_M VMPRF_SYSTEM_M VMPRF_USER_M
Service Level Reporter V3 Table Names NR_NVRESPS NR_SESSFS NR_NVSMUTIS NR_X25LNKS NR_NPSIVCS NR_X25PUS OPCAUTEVSTAT OPCMCPSUM OPCFBMSUM OPCOPEVSUM OPCOPEVLOG VMSUM VMPRFDASDSUM VMPRFPROCSUM VMPRFSYSSUM VMPRFUSERSUM
187
188
Appendix C. Parameter Table to Lookup Table Cross Reference

This appendix presents an alphabetical cross reference of pre-defined SLR parameter tables to the PR components Lookup tables. The Lookup tables and the Parameter tables are not an exact match by any means. Many of the pre-defined SLR parameter tables have no equivalent Performance Reporter Lookup tables. Much of the data kept in these parameter tables is now collected into the actual Performance Reporter data tables. You should refer to your Performance Reporter manuals, which describe all Lookup Tables in each component, for detailed information.
Table 75. SLR Parameter Table to PR Lookup Table Cross Reference
SLR Parameter Table Name ABENDCODES ACCTCICSPRIC
Product Supported SMF CICS
Log Tables Updated None None
Equivalent PR Lookup Table MVS_ABEND_CODE Refer to the Lookup tables Contained in the Resource Accounting Component Refer to the Lookup tables Contained in the Resource Accounting Components Refer to the Lookup tables Contained in the Resource Accounting Components Refer to the Lookup tables Contained in the Resource Accounting Components Refer to the Lookup tables Contained in the Resource Accounting Components USER_GROUP MVS_AVAIL_RESOURCE
ACCTIMSPRICE
IMS
None
ACCTIMSRES
IMS
None
ACCTJOBPRICE
SMF
None
ACCTTSOPRICE
SMF
None
BATCH_BE_TAB
SMF
ADDRLOG ADDRDELTALO G JOBLOG IMSALOG None CICSTRANSLOG
BMPPARMS CICSAPPLIDS CICS_BE_TAB
IMS CICS CICS
IMS_APPLICATION CICS_LOOKUP_APPL CICS_LOOKUP_APPL,U SER_GROUP
189
SLR Parameter Table Name CICS_PRICES CICSRESPOBJ CPU_RATE DASD_CTLPARM DASD_DSNPARM
Product Supported CICS CICS SMF DCOLLECT DCOLLECT
Log Tables Updated CICSACCTLOG CICSTRANSLOG WACTLOG None HSM_BACKUP HSM_DASDCAP HSM_MIGRATE HSM_MIGRATE DB2ACCTLOG1 DB2ACCTLOG1 FTPALOG IMSTLOG IN_PRBOPNLOG IN_PRBCLSLOG LR_IPL_LOG LR_VTAM_LOG LR_MCH_LOG LR_DASD_LOG LR_IPL_LOG LR_DASD_LOG LR_MCH_LOG LR_VTAM_LOG MSGLOG NLDMACCTLOG NLDMRTMLOG NLDMACCTLOG None
Equivalent PR Lookup Table CICS_LOOKUP_APPL, PRICE_LIST CICS_LOOKUP_APPL CPU_NORMAL_DATA DFSMS_LAST_RUN DFSMS_DS_OWNER
DASD_MGTPARM DB2APPLIC DB2USERGR FTPAPAR IMS_BE_TAB IN_PRB_OBJ LR_CPU_PARM
DCOLLECT DB2 DB2 Netview FTP IMS Information/ Management LOGREC
DFSMS_MIGRATE_DAYS DB2_APPLICATION USER_GROUP NONE NONE INFOMAN_OBJECTIVE EREP_CPU_ID
LR_DASD_PARM LR_SYS_PARM
LOGREC LOGREC
EREP_DASD_GROUP EREP_CPU_ID
MSGPARM NET_BE_TAB NLDM_PARM
SYSLOG NetView NetView
MSG_SYSLOG_TYPE NONE Refer to the Lookup Tables Contained in the Network Components Refer to the Lookup Tables Contained in the Network Components
NODETYPES
NetView, VNCA
190
SLR Parameter Table Name OPCFBMPARM OPCMCPPARM OPCNODEPARM PPCPUC
Product Supported OPC/A, OPC/ESA OPC/A, OPC/ESA OPC/A, OPC/ESA SMF Performance Management SMF Performance Management
Log Tables Updated OPCFBMLOG OPCMCPLOG OPCAUTEVLOG PLWORK
Equivalent PR Lookup Table NONE OPC_WORKSTATION NONE NONE
PPSHIFT
PLADEV PLAPPL PLASPC PLDCACHE PDEV PLDSET PLENQ PLHSM PLLPAR PLPAGE PLPCACHE PLPCH PLPDS PLSCLASS PLSTOR PLSWAP PLVLF PLWORK PLAPPL PLADEV PLDSET PLWORK PLSTOR
MVSPM_TIME_RES
PPTYPE
SMF Performance Management SMF Performance Management SMF RACF RACF
MVS_WORKLOAD_TYPE
PPTYPE2
MVS_WORKLOAD_TYPE
PRICE_PARAM RACFACC_ALW RACFACC_REQ
JOBLOG RACFLOG RACFLOG
Refer to Accounting Feature Lookup Tables NONE NONE
Parameter Table to Lookup Table Cross Reference
191
SLR Parameter Table Name RACFEVENT RACF_OM_UID RACFRESPARMD RACFRESPARMG RACFUSERPARM SWAPREASONS TIMEZONES
Product Supported RACF RACF RACF RACF RACF SMF CICS
Log Tables Updated RACFLOG RACFLOG RACFLOG RACFLOG RACFLOG SWAPLOG CICSACCTLOG CICSEXCEPLOG CICSTRANSLOG CICSSYSLOG CICSXLOG TSOCMDLOG TSODELTALOG TSOSESLOG TSOCMDLOG VMACCTLOG CPULOG DEVICELOG DEVLOG JOBLOG LR_IPL_LOG PAGINGLOG STEPLOG SYSAVUPLOG SYSLOG TSOSESLOG WACTLOG
Equivalent PR Lookup Table RACF_EVENT_CODE RACF_USER_OWNER RACF_RES_OWNER RACF_RES_OWNER RACF_USER_OWNER NONE NONE
TSO_BE_TAB
SMF
USER_GROUP
TSO_PRICES VMPARM WKLD_PER_TAB
SMF VM Accounting SMF
Refer to Accounting Feature Lookup Tables USER_GROUP PERIOD_PLAN, SPECIAL_DAY
W_TYPE_PARAM
SMF
MVS_WORKLOAD_TYPE
192
Appendix D. Special Notices

This publication is intended to help the enterprise perfromance administrator migrate Service Level Reporter information to Performance Reporter. The information in this publication is not intended as the specification of any programming interfaces that are provided by Service Level Reporter or Tivoli Performance Reporter for OS/390. See the PUBLICATIONS section of the IBM Programming Announcement for Service Level Reporter and Tivoli Performance Reporter for OS/390 for more information about what publications are considered to be product documentation. References in this publication to IBM products, programs or services do not imply that IBM intends to make 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 IBMs product, program, or service may be used. Any functionally equivalent program that does not infringe any of IBMs intellectual property rights may be used instead of the IBM product, program or service. Information in this book was developed in conjunction with use of the equipment specified, and is limited in application to those specific hardware and software products and levels. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, NY 10594 USA. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact IBM Corporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The information contained in this document has not been submitted to any formal IBM test and is distributed AS IS. The information about non-IBM ("vendor") products in this manual has been supplied by the vendor and IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customers ability to evaluate and integrate
193
them into the customers operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites. Any performance data contained in this document was determined in a controlled environment, and therefore, the results that may be obtained in other operating environments may vary significantly. Users of this document should verify the applicable data for their specific environment. The following document contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples contain the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Reference to PTF numbers that have not been released through the normal distribution process does not imply general availability. The purpose of including these reference numbers is to alert IBM customers to specific information relative to the implementation of the PTF when it becomes available to each customer according to the normal IBM PTF distribution process. You can reproduce a page in this document as a transparency, if that page has the copyright notice on it. The copyright notice must appear on each page being reproduced. The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries:
AIX Application Systems/400 Business Partner CUA DATABASE 2 DFSMS/MVS DRDA Enterprise Systems Architecture/390 IBM IMS/ESA IAS/400 BookManager CICS/MVS DB2 DB2 Universial Database Distributed Relational Database Architecture ESA/390 GDDM IMS MQSeries
194
MVS MVS/XA OS/390 RACF VM/ESA
MVS/ESA NetView QMF System/390 VM/XA
The following terms are trademarks of other companies: Tivoli Management Environment, TME10, TME 10 Framework, TME 10 Software Distribution AutoPack, TME 10 Inventory, and TME 10 Software Installation Service are trademarks of Tivoli Systems, and IBM Company. Java and HotJava are trademarks of Sun Microsystems, Incorporated. Microsoft, Windows, Windows NT, Windows 98 logo and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names may be trademarks or service marks of others.
Special Notices
195
196
Appendix E. Related Publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.
E.1 International Technical Support Organization Publications

For information on ordering these ITSO publications see How to Get ITSO Redbooks on page 199. An Introduction to Tivoli, SG24-4948
E.2 Redbooks on CD-ROMs

Redbooks are also available on CD-ROMs. Order a subscription and receive updates 2-4 times a year at significant savings.
CD-ROM Title System/390 Redbooks Collection Networking and Systems Management Redbooks Collection Transaction Processing and Data Management Redbook Lotus Redbooks Collection Tivoli Redbooks Collection AS/400 Redbooks Collection RS/6000 Redbooks Collection (HTML, BkMgr) RS/6000 Redbooks Collection (PostScript) RS/6000 Redbooks Collection (PDF Format) Application Development Redbooks Collection
Subscription Number SBOF-7201 SBOF-7370 SBOF-7240 SBOF-6899 SBOF-6898 SBOF-7270 SBOF-7230 SBOF-7205 SBOF-8700 SBOF-7290
Collection Kit Number SK2T-2177 SK2T-6022 SK2T-8038 SK2T-8039 SK2T-8044 SK2T-2849 SK2T-8040 SK2T-8041 SK2T-8043 SK2T-8037
E.3 Other Publications

These publications are also relevant as further information sources:
AS/400 System Performance Feature, SH19-4019 Capacity Planner Feature Guide and Reference , SH19-4021 Messages and Problem Determination , SH19-6902 Administration Guide, SH19-6816 P.R. V1R3 Guide to the Reporting Dialog , SH19-6842
197
System Performance Feature: Reference Vol II, SH19-4494 CICS Performance Feature Guide and Reference , SH19-6820 IMS Performance Feature Guide and Reference , SH19-6825 Accounting Feature Guide and Reference, SH19-4495 Network Performance Feature Reports , SH19-6821 P.R. V1R3 Language Guide and Reference , SH19-6817 System Performance Feature Guide , SH19-6818 Network Perform. Feature Install. and Admin., SH19-6901 P.R. V1R3 Reporting Dialog/2 Feature Guide , SH19-6843 P.R. V1R2 Network Performance Feature Reference, SH19-6822 System Performance Feature: Reference Vol. I, SH19-6819 Workstation Performance Feature Guide and Reference , SH19-4018
SLR V3R3.1 Installation and Customization, SH19-6437 SLR V3R3.1 Users Guide: Performance Management, SH19-6442 SLR 3.3 Users Guide: Reporting, SH19-6530 SLR V3R3.1 Tailoring Guide, SH19-6531 SLR 3.3.1 Command and Macro Reference, SH19-6532 SLR V3R3.1 Data Base Table Reference, SH19-6533 SLR 3.3.1 Messages and Abend Codes, SH19-6534 SLR V3R3.1 Network Reporter: Installation and Customization, SH19-6722 SLR 3.3 Capacity Planner: Installation Guide, SH19-6876 SLR 3.3 Capacity Planner: Users Guide and Reference, SH19-6877
198
How to Get ITSO Redbooks

This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change. The latest information may be found at http://www.redbooks.ibm.com/.
How IBM Employees Can Get ITSO Redbooks

Employees may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: Redbooks Web Site on the World Wide Web
http://w3.itso.ibm.com/
PUBORDER to order hardcopies in the United States Tools Disks To get LIST3820s of redbooks, type one of the following commands:
TOOLCAT REDPRINT TOOLS SENDTO EHONE4 TOOLS2 REDPRINT GET SG24xxxx PACKAGE TOOLS SENDTO CANVM2 TOOLS REDPRINT GET SG24xxxx PACKAGE (Canadian users only)
To get BookManager BOOKs of redbooks, type the following command:

TOOLCAT REDBOOKS
To get lists of redbooks, type the following command:

TOOLS SENDTO USDIST MKTTOOLS MKTTOOLS GET ITSOCAT TXT
To register for information on workshops, residencies, and redbooks, type the following command:
TOOLS SENDTO WTSCPOK TOOLS ZDISK GET ITSOREGI 1998
REDBOOKS Category on INEWS Online send orders to: USIB6FPL at IBMMAIL or DKIBMBSH at IBMMAIL Redpieces For information so current it is still in the process of being written, look at "Redpieces" on the Redbooks Web Site (http://www.redbooks.ibm.com/redpieces.html). Redpieces are redbooks in progress; not all redbooks become redpieces, and sometimes just a few chapters will be published this way. The intent is to get the information out much quicker than the formal publishing process allows.
199
How Customers Can Get ITSO Redbooks

Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: Online Orders send orders to: In United States In Canada Outside North America Telephone Orders United States (toll free) Canada (toll free) Outside North America (+45) 4810-1320 - Danish (+45) 4810-1420 - Dutch (+45) 4810-1540 - English (+45) 4810-1670 - Finnish (+45) 4810-1220 - French Mail Orders send orders to: IBM Publications Publications Customer Support P.O. Box 29570 Raleigh, NC 27626-0570 USA Fax send orders to: United States (toll free) Canada Outside North America 1-800-445-9269 1-800-267-4455 (+45) 48 14 2207 IBM Publications 144-4th Avenue, S.W. Calgary, Alberta T2P 3N5 Canada IBM Direct Services Sortemosevej 21 DK-3450 Allerd Denmark 1-800-879-2755 1-800-IBM-4YOU (long distance charges apply) (+45) 4810-1020 - German (+45) 4810-1620 - Italian (+45) 4810-1270 - Norwegian (+45) 4810-1120 - Spanish (+45) 4810-1170 - Swedish IBMMAIL usib6fpl at ibmmail caibmbkz at ibmmail dkibmbsh at ibmmail Internet usib6fpl@ibmmail.com lmannix@vnet.ibm.com bookshop@dk.ibm.com
(long distance charge)
1-800-IBM-4FAX (United States) or (+1) 408 256 5422 (Outside USA) ask for: Index # 4421 Abstracts of new redbooks Index # 4422 IBM redbooks Index # 4420 Redbooks for last six months On the World Wide Web Redbooks Web Site IBM Direct Publications Catalog Redpieces For information so current it is still in the process of being written, look at "Redpieces" on the Redbooks Web Site (http://www.redbooks.ibm.com/redpieces.html). Redpieces are redbooks in progress; not all redbooks become redpieces, and sometimes just a few chapters will be published this way. The intent is to get the information out much quicker than the formal publishing process allows. http://www.redbooks.ibm.com http://www.elink.ibmlink.ibm.com/pbl/pbl
200
IBM Redbook Order Form

Please send me the following: Title Order Number Quantity
First name Company Address City Telephone number Invoice to customer number Credit card number
Last name
Postal code Telefax number
Country VAT number
Credit card expiration date
Card issued to
Signature
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment.
201
202
Glossary
Adaptable Log Layout (A.L.L.) Service Level Reporter log table definition that is flexible and can be redefined by the user. Central Processing Unit (CPU) The part of a computer that includes the circuits that control the interpretation and execution of instructions. A CPU is the circuitry and storage that executes instructions. Traditionally, the complete processing unit was often regarded as the CPU, whereas today the CPU is often a microchip. In either case, the centrality of a processor or processing unit depends on the configuration of the system or network in which it is used. Command Line Interface (CLI) A type of computer interface in which the input command is a string of text characters. Contrast with graphical user interface. Customer Information Control System (CICS) An IBM licensed program that provides online transaction processing services and management for critical business applications. CICS runs on many IBM and non-IBM platforms (from the desktop to the mainframe) and is used in various types of networks that range in size from a few terminals to many thousands of terminals. The CICS application programming interface (API) enables programmers to port applications among the hardware and software platforms on which CICS is available. Each product in the CICS family can interface with the other products in the CICS family, thus enabling interproduct communication. DB2 An IBM relational database management system that is available as a licensed program on several operating systems. Programmers and users of DB2 can create, access, modify, and delete data in relational tables using a variety of interfaces. Direct Access Storage Device (DASD) A mass storage medium on which a computer stores data. Contrast with random access memory. Extended Architecture (XA) An extension to System/370 architecture that takes advantage of continuing high performance enhancements to computer system hardware. Graphical User Interface (GUI) A type of computer interface consisting of a visual metaphor of a real-world scene, often of a desktop. Within that scene are icons, representing actual objects, that the user can access and manipulate with a pointing device. Contrast with command line interface. Information Management System/Virtual Storage (IMS/VS) A database/data communication (DB/DC) system that can manage complex databases and networks. Java Database Connectivity (JDBC) An application programming interface (API) that has the same characteristics as Open Database Connectivity (ODBC) but is specifically designed for use by Java database applications. Also, for databases that do not have a JDBC driver, JDBC includes a JDBC to ODBC bridge, which is a mechanism for converting JDBC to ODBC; it presents the JDBC API to Java database applications and converts this to ODBC. JDBC was developed by Sun Microsystems, Inc. and various partners and vendors. MVS Multiple Virtual Storage. Implies MVS/390, MVS/XA, MVS/ESA, and the MVS element of the OS/390 operating system. Open Database Connectivity (ODBC) A standard application programming interface (API) for accessing data in both relational and nonrelational database management systems. Using this API, database applications can access data stored in database management systems on a variety of computers even if each database management system uses a different data storage format and programming interface. ODBC is based on the call level interface (CLI) specification of the X/Open SQL Access Group and was developed by Digital Equipment Corporation (DEC), Lotus, Microsoft, and
203
Sybase. Contrast with Java Database Connectivity. NetView Performance Monitor (NPM) An IBM licensed program that collects, monitors, analyzes, and displays data relevant to the performance of a VTAM telecommunication network. It runs as an on-line VTAM application program. Random Access Memory (RAM) A temporary storage location in which the central processing unit (CPU) stores and executes its processes. Contrast with direct access storage device. SQL A programming language that is used to define and manipulate data in a relational database. Structured Programming Facility (SPF) An IBM product that is a full-screen editor. Structured Query Language See SQL. System Management Facility (SMF) A standard feature of OS/390 that collects and records a variety of system and job-related information. Time Sharing Option (TSO) An option of the MVS operating system that provides interactive time sharing from remote terminals. Transmission Control Protocol/Internet Protocol (TCP/IP) A set of communications protocols that support peer-to-peer connectivity functions for both local and wide area networks. UNIX An operating system developed by Bell Laboratories that features multiprogramming in a multiuser environment. The UNIX operating system was originally developed for use on minicomputers but has been adapted for mainframes and microcomputers. The AIX operating system is IBMs implementation of the UNIX operating system.
204
List of Abbreviations
A.L.L Adaptable Log Layout SPF SQL TCP/IP Structured Programming Facility Structured Query Language Transmission Control Protocol/Internet Protocol
DASD
DB2 DMS CICS CLI CPU DRDA
Direct Access Storage Device

DATABASE 2 Data Management System Customer Information Control System Command Line Interface Central Processing Unit
TOTPATS
TSO
Total Patterns
Time Sharing Option
Distributed Relational Database Architecture

Graphical User Interface International Business Machines Corporation Information Management System International Technical Support Organization Multiple Virtual Storage/Enterprise Systems Architecture Multiple Virtual Storage/Extended Architecture NetView Performance Monitor Open Database Connectivity Performance Reporter Service Level Reporter Systems Management Facilities
GUI IBM IMS ITSO MVS/ESA
MVS/XA
NPM ODBC PR SLR SMF
205
206
Index A
ADDRDISTR 143 ADDRSTAT 142 AVAILABILITY_M 147 AVAILABILITY_W 166 AVAILSTAT 147 DRLSYS DRLSYS.DRLMIGRATION 137 DRLW0500 164 DRLW0520 165 DRLW0630 143 DRLW0640 143 DRLW0700 177 DRLW0710 177 DRLW0713 177 DRLW0720 143 DRLW0730 144 DRLW0740 144 DRLW0750 143 DRLW0760 145 DRLW0780 142 DRLW0790 142 DRLW07A0 145 DRLW07E0 146 DRLW0890 147 DRLW0A31 161 DRLW0A4A 160 DRLW0A4B 160 DRLW0A52 159 DRLW0A54 159 DRLW0AC0 180 DRLW0AD0 179 DRLW0AD1 178 DRLW0AD2 178 DRLW0AD4 177 DRLW0B60 154 DRLW0B63 155, 156, 157 DRLW0B66 157, 158 DRLW0E0F 165 DRLW0E11 166 DRLW0E31 153 DRLW0E32 152 DRLW0E33 153 DRLW0E38 151 DRLW0E39 152 DRLW0E3A 148 DRLW0E3B 148 DRLW0E3C 149 DRLW0E3D 150 DRLW0E3E 150 DRLW0E3F 151 DRLW0E51 162 DRLW0E52 162
C
CICS_M_GLOBAL_D 165 CICS_TRANSACTION_W 164 CICSSYSSTAT 165 CICSTRANSUM 164 COMPCODE 144 CPULOAD/IPLSUM 142
D
DASD_CTLPARM 152 DASD_DSNPARM 153 DASD_DSNSTAT 148 DASD_MGTPARM 153 DASD_VOLSTAT 148 DATA_BASE 137 DB2_APPL_DIST_W 155 DB2_APPLICATION_W 157 DB2_TRAN_DIST_W 156 DB2_TRANSACTION_W 154 DB2_USER_AP_DIST_W 156 DB2_USER_APPL_W 158 DB2_USER_DIST_W 157 DB2_USER_TRAN_ 154 DB2ACCTSUM1/DB2ACCTSUM2 154 DB2CAPASUM 157, 158 DB2DISTSUM 155, 156, 157 DFSMS_ACTIVITY_M 151 DFSMS_BACKUP_D/M 149 DFSMS_DASD_CAP_D/M 150 DFSMS_DATASET_D/M 148 DFSMS_DS_OWNE 153 DFSMS_LAST_RUN 152 DFSMS_MIGRATE_DAYS 153 DFSMS_MIGRATION_D/M 150 DFSMS_TAPE_CAP_D/M 151 DFSMS_VOLUME_D/M 148 DRLMIGRATION 137
207
DRLW0E53 163 DRLW0E54 163 DRLW2022 147 DRLW2322 168 DRLW2325 168 DRLW2342 169 DRLW2356 172 DRLW2357 169 DRLW2362 172 DRLW2364 171 DRLW2366 167 DRLW2368 170 DRLW236B 175 DRLW236E 175 DRLW2372 171 DRLW2376 176 DRLW2378 173 DRLW237B 174 DRLW237E 174 DRLW2391 166 DRLWAVAI 147 DRLWC101 164 DRLWC702 165 DRLWD2A 158 DRLWD2DA 155 DRLWD2DP 156 DRLWD2DT 156 DRLWD2DU 157 DRLWD2T 154 DRLWD2UA 158 DRLWD2UT 155 DRLWDFA1 152 DRLWDFA2 152 DRLWDFBA 149 DRLWDFBX 149 DRLWDFDA 148 DRLWDFDC 150 DRLWDFDX 148 DRLWDFDY 151 DRLWDFLR 152 DRLWDFMD 153 DRLWDFMI 150 DRLWDFMX 150 DRLWDFOW 153 DRLWDFTC 151 DRLWDFTX 151 DRLWDFVO 149 DRLWDFVX 149 DRLWERCI 160
DRLWERDA 159 DRLWERDG 161 DRLWERVT 159 DRLWIFPS 177 DRLWITRA 177 DRLWITRB 177 DRLWMAMI 165 DRLWMASY 166 DRLWMVAD 143 DRLWMVAS 143 DRLWMVAT 143 DRLWMVAU 143 DRLWMVCC 144 DRLWMVIL 147 DRLWMVPG 144 DRLWMVPT 146 DRLWMVS1 142 DRLWMVSY 142 DRLWMVTA 146 DRLWMVWO 145 DRLWNAVM 167 DRLWNAVW 167 DRLWNCP 171 DRLWNE 176 DRLWNHAB 168 DRLWNHAG 168 DRLWNIP 175 DRLWNLI 172 DRLWNMSM 170 DRLWNNPM 167 DRLWNPU 171 DRLWNRTM 170 DRLWNRTW 170 DRLWNSSF 169 DRLWNTM 173 DRLWNTW 173 DRLWNXLN 173 DRLWNXNI 174 DRLWNXPU 174 DRLWOPA 177 DRLWOPM 179 DRLWOPMP 178 DRLWOPOE 179 DRLWOPOT 180 DRLWVACT 161 DRLWVM01 162 DRLWVM41 163 DRLWVM61 164
208
E
EREP_CPU_ID 160 EREP_DASD_GROUP 160 EREP_DASD_M 159 EREP_VTAM_M 159
MVS_TAPE_M 146 MVS_WORKLOAD_M 145
N
NR_ALERTS 168 NR_AVAILS 166 NR_GENALERTS 168 NR_LINEUTIS 172 NR_NCPUTIS 171 NR_NEOS 176 NR_NPMRESPS 172 NR_NPMUTIS 167 NR_NPSIVCS 174 NR_NTRILOGS 175 NR_NTRIPHYS 175 NR_NVRESPS 169 NR_NVSMUTIS 170 NR_PUUTIS 171 NR_SESSFS 169 NR_X25LNKS 173 NR_X25PUS 174 NRDB 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176 NW_ALERT_BASIC_W 168 NW_ALERT_GENERIC_W 168 NW_LINE_UTIL_W 172 NW_NCP_UTIL_W 171 NW_NEO_UTIL_W 176 NW_NPM_TRANSIT_W 172 NW_NPM_UTIL_W 167 NW_NTRIL_UTIL_W 175 NW_NTRIP_UTIL_W 175 NW_PU_UTIL_W 171 NW_RTM_RESONSE_W 169 NW_SESSION_FAIL_W 169 NW_SM_UTIL_W 170 NW_X25LN_UTIL_W 173 NW_X25NI_UTIL_W 174 NW_X25PU_UTIL_W 174
H
HSM_BCKUPSUM HSM_BKUP_ACT HSM_DASD_SUM HSM_MIGR_ACT HSM_MIGR_SUM HSM_TAPE_SUM 149 151 150 151 150 151
I
IMS_TRANSACTION_W 177 IMSFPSUM 177 IMSTRANS 177 INSERT_MEMBER1 138 INSERT_MEMBER2 138 INSERT_MEMBER3 138 IPLLOG 147
J
JOBSTAT 142
L
LOGCOL_MEMBER 138 LR_CPU_PARM 160 LR_DASD_PARM 160 LR_DASD_SUM 159 LR_VTAM_SUM 159
M
MSDLI/IMSTRANS 177 MSG_SYSLOG_M 166 MSG_SYSLOG_TYPE 165 MSGPARM 165 MSGSUM 166 MVS_ADDRDISTR_M 143 MVS_ADDRSPACE_M 142 MVS_COMPCODE_M 144 MVS_IPL_T 147 MVS_PRINTER_M 145 MVS_PROGRAM_M 144 MVS_SYSTEM_M 142
O
OPC_AUTO_EVENT_M 177 OPC_MCP_M 178 OPC_MISSED_FB_M 178 OPC_OPER_EVENT_M 179 OPC_OPER_EVENT_T 180 OPCAUTEVSTAT 177 OPCFBMSUM 178
209
OPCMCPSUM 178 OPCOPEVLOG 180 OPCOPEVSUM 179
P
PAGESUM/CPULOAD/WORKLOAD 142 PGMSTAT 144 PRINTLOAD 145
S
SDRLDEFS 137 SLR_TABLES 137 SYSTEMD 154 SYSTEMDB 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 177, 178, 179, 180
T
TABLE_NAME 137 TAPESTAT 146 TSOSTAT 142
U
UNLOAD_MEMBER1 137 UNLOAD_MEMBER2 138 UNLOAD_MEMBER3 138
V
VMACCT_SESSION_M 161 VMPRF_DASD_M 163 VMPRF_PROCESSOR_M 162 VMPRF_SYSTEM_M 162 VMPRF_USER_M 163 VMPRFDASDSUM 163 VMPRFPROCSUM 162 VMPRFSYSSUM 162 VMPRFUSERSUM 163 VMSUM 161
W
WORKLOAD 145
210
ITSO Redbook Evaluation

SLR to Tivoli Performance Reporter for OS/390 Migration Cookbook SG24-5128-00 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and return it using one of the following methods: Use the online evaluation form found at http://www.redbooks.ibm.com Fax this form to: USA International Access Code + 1 914 432 8264 Send your comments in an Internet note to redbook@us.ibm.com Which of the following best describes you? _ Customer _ Business Partner _ Solution Developer _ None of the above
_ IBM employee
Please rate your overall satisfaction with this book using the scale: (1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor) Overall Satisfaction Please answer the following questions: Was this redbook published in time for your needs? If no, please explain: Yes___ No___ __________
What other redbooks would you like to see published?
Comments/Suggestions:
(THANK YOU FOR YOUR FEEDBACK!)
211
SLR to Tivoli Performance Reporter for OS/390 Migration Cookbook
SG24-5128-00
SG24-5128-00 Printed in the U.S.A.

SLR To Tivoli Performance Reporter For OS-390 Migration Cookbook Sg245128

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SLR To Tivoli Performance Reporter For OS-390 Migration Cookbook Sg245128

Uploaded by

Copyright:

Available Formats

SLR to Tivoli Performance Reporter for OS/390 Migration Cookbook

Mike Foster, Mauro Basile, Malcolm Pearse

International Technical Support Organization http://www.redbooks.ibm.com

First Edition (February 1999)

Copyright IBM Corp. 1999

. . . . . . . . . . . . . . . . . . . 99 . . . . . . . . . . . . . . . . . . 100 . . . . . . . . . . . . . . . . . . 103 . . . . . . . . . . . . . . . . . . 106