IMS Problem Analysis via Log Records - IMS UG April 2012 Victoria

1,773 views
1,585 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,773
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS Problem Analysis via Log Records - IMS UG April 2012 Victoria

  1. 1. IMS Performance AnalyzerIMS Tools – Technical Sales SupportDennis Eichelbergerdeichel@us.ibm.com 1 © 2012 IBM Corporation
  2. 2. IMS Performance Analyzer Overview Input Specification ISPF Dialog Reporting Summary2 © 2012 IBM Corporation
  3. 3. IMS Performance Analyzer HighlightsIMS Performance Analyzer processes IMSLog, Monitor, IMS Connect event data, andOMEGAMON TRF data to providecomprehensive reports for use by IMSspecialists to tune their IMS systems, andmanagers to verify service levels and predicttrends.IMS PA provides detailed information abouttransit times (actual system performancetime), and IMS resource usage andavailability. IMS PA can process logs from a 3 © 2012 IBM Corporation
  4. 4. IMS Performance Analyzer Highlights• Supports all versions of IMS • Accepts input from the IMS Logs, DC Monitor, IMS Connect Journals, and OMEGAMON TRF and ATF data.• Provides comprehensive performance analysis and tuning assistance for IMS.• Delivers end-to-end transit analysis for all types of transaction workloads, including shared-queues, by merging sysplex logfiles.• Delivers end-to-end IMS Connect and IMS Log reporting; providing a complete picture of the life-cycle of transactions as they pass through Connect and into IMS.• Offers DBRC Log selection for quick and easy log report requests.• Comprehensive IMS monitor reporting including Fast Path.• Analyze transaction response time.• Report Forms allow you to design your own reports. 4 © 2012 IBM Corporation
  5. 5. IMS Performance Analyzer Highlights• Measure usage and availability of important resources, including databases, programs, regions, buffers (including database) and queues (message and other internal queues).• Plan for IMS operational management, including scheduling database reorganizations, monitoring service level adherence, charge-back accounting and capacity planning.• Monitor significant system events that can adversely affect system performance and availability.• Boost system and application programmer productivity.• Report critical performance information -- from high-level management summaries to detailed traces for in-depth analysis.• Analyze the impact of IMS Connect on transaction performance.• Provides an ISPF dialog and batch commands to manage reporting requirements across your entire IMS enterprise. 5 © 2012 IBM Corporation
  6. 6. IMS Performance Analyzer
  7. 7. Performance Analyzer Inputs
  8. 8. IMS Logs• Transaction Transit Times• Transaction Traffic• Resource Usage• Resource Availability• Fast Path Transaction Transit• Fast Path Transaction Resource Usage• Traces
  9. 9. IMS Connect Journals • Transaction Transit – Internal and External • Resource Availability • Session ErrorsIMS DC Monitor • System Options • Region Activity • System Analysis • Program Activity • Database Activity • Monitor Trace
  10. 10. Performance Analyzer ISPF Dialog
  11. 11. IMS Performance Analyzer – Ex ipi.sipiexec(ipiexec)|| File Options Help| ----------------------------------------------------------------------------| IMS Performance Analyzer 4.2 - Primary Option Menu || Option ===> ________________________________________________________________ ||| 0 IMS PA Profile Customize your IMS PA dialog profile| 1 System Definitions Specify IMS and Connect systems and OMEGAMON files || 2 Groups Specify Groups of IMS and Connect systems (Sysplexes) || 3 Report Sets Request and submit reports and extracts || 4 Expectation Sets Define Expectation Sets (Log exception reporting) || 5 Averages Edit Averages data sets (Log exception reporting) || 6 Object Lists Define Object Lists| 7 Distributions Define Distributions| 8 Graphing & Export Graph or export Log Extract by Interval data || 9 IMS Connect Submit IMS Connect report requests| 10 Report Forms Define Report Forms| X Exit Terminate IMS PA||__________________________________________________________________________________|
  12. 12. IMS Performance Analyzer
  13. 13. IMS Performance Analyzer
  14. 14. IMS Performance Analyzer
  15. 15. Performance Analyzer Reports
  16. 16. Performance Analyzer Reports IMS PA provides an extensive suite of reports to help administrators monitor resources utilization and transaction performance of IMS TM and DB systems. There are standard reports or form based reports may be tailored to individual needs. • Log Reports • Monitor Reports • IMS Connect Reports • Omegamon TRF Reports • Omegamon ATF Reports
  17. 17. Performance Analyzer Management ReportsThe Management reports provide a high The Monitor reports provide analysts andlevel overview of the IMS system programmers complete information for programhighlighting potential items for further analysis and problem resolution.reporting.• Dashboard • Region Activity Summary Transaction Transit Graphic Region Activity Analysis Summary • System Analysis Transaction Transit extract by • Resource Usage Interval • Fast Path Analysis• Transaction Exception • Monitor Data AnalysisThe Management Exception• Detail reports provide analysts andprogrammers complete information for The Analysis reports provide IMS systemprogram analysis and problem resolution. administrators with summary information Transaction Transit Log regarding the operating IMS system. – Transit activity of each message • Transaction Transit Statistics Region Histogram Transaction Transit Analysis Transaction scheduling patterns • Transaction Resource Usage• DC Queue Manager Trace • Resource Availability – Time based list of each TM event • CPU Usage• Database Trace • Deadlocks – Before and after versions of updates • Database Update Activity by program, time • Checkpointing
  18. 18. IMS PA daily performance summary report IMS Performance Analyzer Transaction Resource Usage Data from 05.30.49 07Nov2006 to 05.45.18 07Nov2006 Page 1 Avg Avg Avg Avg <=1.0 1.0-2.0 >2.0 Avg Avg Tran InputQ Process OutputQ Total Total Total Total CPU DB Call Trancode Count Time Time Time IMS Time IMS Time IMS Time IMS Time Time Count DSN8CS 7 0.011024 0.930524 0.000000 0.941549 71.43% 0.00% 28.57% 0.024617 0 DSN8PP 7 0.009017 0.627191 0.000000 0.636208 85.71% 14.29% 0.00% 0.018776 0 DSN8PS 21 0.011219 0.427845 0.007012 0.446075 100.00% 0.00% 0.00% 0.017876 0 DSN8PT 6 0.010506 0.373590 0.035327 0.419423 100.00% 0.00% 0.00% 0.018377 0 Total 41 0.010705 0.539763 0.008761 0.559229 92.68% 2.44% 4.88% 0.019254 0 Daily report flags that 28% of DSN8CS transaction were above the 2 second SLA
  19. 19. Forms: database updates and ESAF activity by transactionIMS Tran CPU InputQ Process OutputQ TotalStart Trancode PST Time Time Time Time IMS Time . . .09.49.26.679840 MQATREQ1 1 0.026658 0.000145 1.724738 0.000000 1.72488310.37.00.753450 MQATREQ2 2 0.015126 0.000221 0.491174 0.000000 0.491395 Bad response time!10.37.41.829685 MQATREQ3 3 0.015126 0.000150 0.386636 0.000000 0.386786 What caused it?10.38.09.060759 MQATREQ4 4 0.015126 0.000265 0.404939 0.000000 0.405204 Total IO DB IO VSAMRead VSAMWrit ESAFcall Trancode . . . Count Time Count Count Count MQATREQ1 7 0.000384 2 3 267 MQATREQ2 12 0.001034 4 7 57 MQATREQ3 16 0.001287 6 11 62 MQATREQ4 18 0.001564 9 16 71 Perhaps it was an external subsystem, but which one and what happened?
  20. 20. IMS Performance Analyzer• IMS Performance Analyzer is the premier tool for: – Service Levels – Capacity planning – Response time analysis• End-to-end transit analysis for all database and transaction workloads – Provides a complete picture of the life cycle of IMS transactions – 100’s of fields can be summarized, analyzed and reported• IMS PA can use its forms-based reporting to identify specific processing deficiencies• ISPF Dialog interface 20 © 2012 IBM Corporation
  21. 21. IMS Problem InvestigatorIMS Tools – Technical Sales SupportDennis Eichelberger 21 © 2012 IBM Corporation
  22. 22. IMS Problem Investigator Overview Input Specification ISPF Dialog Reporting Benefits22 © 2012 IBM Corporation
  23. 23. IMS Problem InvestigatorIBM IMS Problem Investigator is a problem analysis tool forInformation Management System Database (IMS DB) andTransaction Manager (IMS TM). It enables IMS administratorsand programmers to interactively explore formatted,interpreted, and easily customizable views of log records.Users may identify and analyze problems quickly, withoutrequiring an expert understanding of log data structures andthe relationships between log records.IMS Problem Investigator connects log records from acrossvarious sources to create a composite view of the entiretransaction. This allows a user to walk through events in thelifecycle of the transaction, even as it spans multiple IMSsystems, IMS Connect, Websphere MQ, and DB2. As a resultyou can rapidly isolate problems in even the most complextransactions to a specific area and then solve them insignificantly less time. © 2011 IBM Corporation and ICBC
  24. 24. IMS Problem InvestigatorIMS Problem Investigator supports input from the following types ofrecorded data• IMS log records• IMS Transaction Index created by IMS Performance Analyzer• IMS DC monitor and DB monitor files• Common Queue Server (CQS) log stream• IMS Connect event data collected by IMS Connect Extensions• OMEGAMON® Transaction Reporting Facility (TRF) log• DB2 log• WebSphere® MQ log extract• SMF – IRLM Long Lock records © 2011 IBM Corporation and ICBC
  25. 25. IMS Problem Investigator ISPF Reports Extracts dialog Transaction activity merged into a single view• Modern IMS Data sources transactions affect multiple subsystems IMS PA Transaction IMS log Index• Information User records about these OMEGAMON TRF Extractor transactions is TRF records data set recorded in even more and IMS monitor disparate SMF IMS Connect sources Extensions IRLM long-lock WebSphere MQ DB2 log journal records CQS log log extract• IMS PI provides Transaction activity logged in multiple locations a unified and IMS-related subsystems logical view of transactions IMS Connect Extensions spanning all WebSphere these systems DB2 IMS Connect IMS DB/TM CQS MQ © 2011 IBM Corporation and ICBC IMS transaction
  26. 26. IMS Problem InvestigatorAnalysis of data can by performed through an ISPF dialog,batch reports, and REXX™ programming services. Filteredextracts can be created for more efficient probleminvestigation. Through the IMS Problem Investigator ISPFdialog you can:• View formatted logs with detailed field descriptions.• Navigate to an exact point in time within a log file.• Investigate specific problem areas. For example,transaction, database, security, or checkpointprocessing.• Merge log files to combine different aspects of IMSprocessing into a single view.• Track and show all events from a single transactionacross multiple subsystems or an entire IMS PLEX. © 2011 IBM Corporation and ICBC• Determine response times and latencies.
  27. 27. IMS Problem Investigator (IMS PI) Reduce time and costs associated with IMS problem Reduce time and costs associated with IMS problem determination determination• IMS PI allows you to interactively browse and analyze log records• Instantaneous view of the logs• Navigate by the time of day• Select records to drill down right to the values of individual flag bits• Gain an end-to-end picture of transactions in the Sysplex (a complex and time intensive activity)• Determine transaction times and event latencies
  28. 28. IMS Problem Investigator Start of Connect transaction Start of IMS transaction Connect resumes Connect transaction ends after 0.278 seconds
  29. 29. IMS PI Sudden jump in elapsed time indicates DB2 insert took over 2 seconds! Select the event to view details and begin analysis.
  30. 30. IMS Problem Investigator Methods• Time slicing: Process large log files with the responsiveness and convenience of a small extract file• Transaction index: Extend the insights of transaction performance recorded by IMS PA to help analyze transactions in IMS PI• Unit of work tracking: Isolate a single unit of recovery (TU) within a transaction (TX) with a long program switch sequence• Support for the DB2 and MQ logs• Extract to CSV: Import the required fields from selected log record types into a DB2 database or PC spreadsheet• OMEGAMON TRF: transaction accounting, DLI and DB2 calls• OMEGAMON ATF: transaction call trace © 2011 IBM Corporation and ICBC
  31. 31. Track and merge all types of logs We have reached end of the transaction we are tracking. Observe all the syncpoint events in the IMS and DB2 logs, as well as the OMEGAMON ATF call trace, and end of transaction events: BROWSE JCH.INDEX Record 00427560 More: < > Command ===> Scroll ===> CSR Forwards / Backwards . . HH.MM.SS.THMIJU Time of Day . . HH.MM.SS.THMIJU Code Description Date 2009-07-10 Friday Time (Relative) / ---- ------------------------------------------------------ ---------------- 05 DLI ISRT TranCode=MQATREQ1 Region=0001 +0.590831 5600 Commit Prepare starting Region=0001 SSID=CSQ6 +0.591778 87 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=CSQ6 +0.593882 87 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.593957 0020 DB2 Unit of Recovery Control - End Commit Phase 1 +0.594135 03 Output Message Response LTerm=FUNTRM07 +0.596907 35 Output Message Enqueue LTerm=FUNTRM07 Region=0001 +0.596939 37 Syncpoint Region=0001 +0.596976 37 Syncpoint message transfer Region=0001 +0.597013 33 Free Message +0.597053 31 Communications GU LTerm=FUNTRM07 +0.597269 87 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=CSQ6 +0.599075 36 Output Message Dequeue LTerm=FUNTRM07 +0.601916 33 Free Message +0.601980 5600 Commit Continue completed Region=0001 SSID=CSQ6 +0.602623 87 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.602626 05 DLI Detail TranCode=MQATREQ1 Region=0001 Func=ASRT +0.591748 0020 DB2 Unit of Recovery Control - Begin Commit Phase 2 +0.602711 0020 DB2 Unit of Recovery Control - End Commit Phase 2 +0.604407 5600 Commit Continue completed Region=0001 SSID=DB3A +0.605222 5612 End of Phase 2 Syncpoint Program=MQATPGM Region=0001 +0.605234 07 Application Terminate TranCode=MQATREQ1 Region=0001 +0.605362 F1 Transaction End TranCode=MQATREQ1 Region=0001 © 2011 +0.605699 and ICBC IBM Corporation 04 Summary Completion TranCode=MQATREQ1 Region=0001 +0.605699 ******************************** Bottom of Data *******************************
  32. 32. IMS Problem Investigator BenefitsEfficiently identify and resolve IMS transaction problems.Interactively track potential problem transactions acrossevents in several components.Quickly access the data needed at the identified timewithout scanning the entire log stream.Merge data from disparate systems in time sequence fora single point of view.Increase productivity by allowing programmers to viewthe data without spending excessive time extracting andcorrelating data.Complements IMS Performance Analyzer32 © 2012 IBM Corporation
  33. 33. IMS Performance Analyzer IMS Problem InvestigatorIMS Tools – Technical Sales SupportDennis Eichelberger 33 © 2012 IBM Corporation
  34. 34. IBM Software GroupIMS Performance Analyzer and IMS ProblemInvestigator IMS Performance Analyzer (IMS PA) is tool that uses the IMS and related logs to create performance and throughput reports. IMS Problem Investigator (IMS PI) is a log analysis tool that allows users to interactively browse IMS and related logs. These tools offer significant value to the customer independently of each other. But the greatest benefit is obtained when they are used together. © 2010 IBM Corporation and ICBC34
  35. 35. IBM Software GroupUsage scenarios In an enterprise environment, when a performance problem is identified, it could be caused by any of these subsystems: IMS Connect OTMA Shared queues IMS TM IMS DB DB2 MQSeries RACF Etc… © 2010 IBM Corporation and ICBC35
  36. 36. IBM Software GroupUsage scenario (inspired by a real use case) To analyze the problem we need to use IMS Connect Extensions, IMS Performance Analyzer, and IMS Problem Investigator The combination of these tools will help isolate a performance problem to a particular system and often identify the underlying cause of the problem All three tools are needed because: Without IMS Connect Extensions the customer will not be able to identify if OTMA or IMS Connect is causing the problem Without IMS Problem Investigator: the customer will not be able to drill-down and see exactly what events are associated with the problem the customer will not be able to correlate the transaction records with data in MQSeries and DB2 logs © 2010 IBM Corporation and ICBC36
  37. 37. IBM Software GroupScenario 1: TCP/IP reported problem © 2010 IBM Corporation and ICBC37
  38. 38. IBM Software GroupIMS Performance Analyzer report IMS Performance Analyzer 4.1 IMS is showing millisecond combined tran list ________________________________ response times while OTMA is 0LIST0001 Printed at 19:33:38 12Dec2007 Data from 13.57.52 12Dec2007 taking seconds CON Tran CON Resp PreOTMA OTMAproc IMS Tran InputQ Process Total PostOTMA Start Trancode OTMA Time Time Time Start Time Time IMS Time Time 13.57.52.714 IMSTRANS CONNECT 1.810 0.000 1.803 13.57.54.517 0.000 0.001 0.001 0.006 13.57.52.964 IMSTRANS CONNECT 1.575 0.000 1.574 13.57.54.538 0.000 0.001 0.001 0.000 13.57.52.972 IMSTRANS CONNECT 1.588 0.000 1.588 13.57.54.548 0.009 0.002 0.011 0.000 13.57.53.091 IMSTRANS CONNECT 1.716 0.002 1.714 13.57.54.806 0.000 0.001 0.001 0.000 13.57.53.567 IMSTRANS CONNECT 1.839 0.000 1.839 13.57.55.403 0.000 0.002 0.002 0.000 13.57.54.044 IMSTRANS CONNECT 1.800 0.000 1.799 13.57.55.836 0.006 0.001 0.007 0.001 13.57.53.800 IMSTRANS CONNECT 1.879 0.000 1.878 13.57.55.677 0.000 0.001 0.001 0.000 13.57.54.120 IMSTRANS CONNECT 1.851 0.000 1.850 13.57.55.903 0.006 0.001 0.007 0.000 13.57.54.213 IMSTRANS CONNECT 1.904 0.000 1.903 13.57.56.116 0.000 0.001 0.001 0.000 13.57.54.251 IMSTRANS CONNECT 1.931 0.000 1.930 13.57.56.180 0.000 0.001 0.001 0.000 13.57.54.713 IMSTRANS CONNECT 2.007 0.001 2.005 13.57.56.718 0.000 0.001 0.001 0.000 13.57.55.461 IMSTRANS CONNECT 2.207 0.000 2.206 13.57.57.665 0.000 0.002 0.002 0.000 13.57.55.632 IMSTRANS CONNECT 2.070 0.001 2.069 13.57.57.700 0.000 0.001 0.001 0.001 13.57.55.890 IMSTRANS CONNECT 2.061 0.002 2.055 13.57.57.946 0.000 0.001 0.001 0.003 13.57.56.147 IMSTRANS CONNECT 2.171 0.002 2.169 13.57.58.314 0.000 0.003 0.003 0.000 13.57.56.190 IMSTRANS CONNECT 2.158 0.001 2.157 13.57.58.347 0.000 0.001 0.001 0.000 13.57.56.559 IMSTRANS CONNECT 2.222 0.000 2.222 13.57.58.780 0.000 0.001 0.001 0.000 13.57.56.909 IMSTRANS CONNECT 2.048 0.002 2.045 13.57.58.955 0.000 0.002 0.002 0.000 13.57.56.934 IMSTRANS CONNECT 2.033 0.001 2.031 13.57.58.966 0.000 0.001 0.001 0.000 Without IMS Connect Extensions, IMS Connect and OTMA performance cannot be obtained © 2010 IBM Corporation and ICBC38
  39. 39. IBM Software GroupIMS PI View of the problem A03C Prepare READ Socket 13.57.58.037571 A049 READ Socket +0.000048IMS A03D Message Exit called for READ +0.000063Connect A03E Message Exit returned from READ TranCode=XXXXXXXXX +0.000082sends to A03F Begin SAF call +0.000097 A040 End SAF call +0.000539IMS OTMA A03F Begin SAF call +0.000548 A040 End SAF call +0.000658 A041 Message sent to OTMA Datastore=MMMMMM +0.000707 01 Input Message TranCode=XXXXXXXXX Source=Connect +2.485621 35 Input Message Enqueue TranCode=XXXXXXXXX +2.485636 08 Application Start TranCode=XXXXXXXXX Region=0184 +2.485709 5607 Start of UOR Program=XXXXXXXX Region=0184 +2.485710 31 DLI GU TranCode=XXXXXXXXX Region=0184 +2.485736 OTMA finally 03 Output Message Response LTerm=9999 Source=Connect +2.488716 logs the 01 31 DLI GU TranCode=XXXXXXXXX Region=0184 +2.488726 record 33 Free Message +2.488774 5610 Start Phase 1 Syncpoint Region=0184 +2.488784 37 Syncpoint Region=0184 +2.488807 33 Free Message +2.488849 5600 Commit found no work to do Region=0184 SSID=AAAA +2.488859 5612 End of Phase 2 Syncpoint Program=YYYYYYY +2.488864 A042 Message received from OTMA Datastore=MMMMMM +2.488917 A042 Message received from OTMA Datastore=MMMMMM +2.489037 A03D Message Exit called for XMIT +2.489926 A03E Message Exit returned from XMIT +2.489943 A04A WRITE Socket +2.489999 A048 Trigger Event +2.490032 © 2010 IBM Corporation and ICBC39
  40. 40. IBM Software GroupScenarion 2: DB2 problem © 2010 IBM Corporation and ICBC40
  41. 41. IBM Software GroupIMS PA daily performance summary report IMS Performance Analyzer Transaction Resource Usage Data from 05.30.49 07Nov2006 to 05.45.18 07Nov2006 Page 1 Avg Avg Avg Avg <=1.0 1.0-2.0 >2.0 Avg Avg Tran InputQ Process OutputQ Total Total Total Total CPU DB Call Trancode Count Time Time Time IMS Time IMS Time IMS Time IMS Time Time Count DSN8CS 7 0.011024 0.930524 0.000000 0.941549 71.43% 0.00% 28.57% 0.024617 0 DSN8PP 7 0.009017 0.627191 0.000000 0.636208 85.71% 14.29% 0.00% 0.018776 0 DSN8PS 21 0.011219 0.427845 0.007012 0.446075 100.00% 0.00% 0.00% 0.017876 0 DSN8PT 6 0.010506 0.373590 0.035327 0.419423 100.00% 0.00% 0.00% 0.018377 0 Total 41 0.010705 0.539763 0.008761 0.559229 92.68% 2.44% 4.88% 0.019254 0 Daily report flags that 28% of DSN8CS transaction were above the 2 second SLA © 2010 IBM Corporation and ICBC41
  42. 42. IBM Software GroupIMS PA Forms-based list report This form lists all the transactions that ran on the day IMS Performance Analyzer Transaction Transit Log Data from 05.30.49 07Nov2006 Page 1 Org DB Call IMS Tran CPU InputQ Process OutputQ Total LTERM Trancode Count Start Time Time Time Time IMS Time . . . FUNTRM69 DSN8PT 0 05.39.50.738060 0.023359 0.007564 0.199647 0.121131 0.328342 FUNTRM69 DSN8PS 0 05.43.38.400003 0.014557 0.020709 0.287724 0.000000 0.308433 FUNTRM69 DSN8CS 0 05.44.52.678102 0.046589 0.013049 2.037216 0.000000 2.050265 . . . We can see an offending transaction from the approximate time of day © 2010 IBM Corporation and ICBC42
  43. 43. IBM Software GroupGather the data required for the analysis Transaction DSN8CS uses DB2, which may be the cause of the problem. We need to gather the IMS log, DB2 log and SMF file for time period around when the problem occurred. IMS PI will merge all the log records and allow us to track the transaction across all these log files… © 2010 IBM Corporation and ICBC43
  44. 44. IBM Software Group Forwards / Backwards . . 00.00.00.000100 Time of Day . . 05.44.52.678102 Code Description Date 2006-11-07 Tuesday Time (Elapsed) / ---- ------------------------------------------------------ ---------------- 01 Input Message TranCode=DSN8CS 05.44.52.678102 35 Input Message Enqueue TranCode=DSN8CS 0.007919 08 Application Start TranCode=DSN8CS Region=0001 0.000807 5607 Start of UOR Program=DSN8IC0 Region=0001 0.000000 31 DLI GU TranCode=DSN8CS Region=0001 0.004315 5616 Start of protected UOW Region=0001 0.000262 5600 Sign-on to ESAF Region=0001 SSID=DB2P 0.165798 5600 Thread created for ESAF SSID=DB2P 0.000041 0020 DB2 Unit of Recovery Control - Begin UR 1.651871 0020 DB2 Exclusive Lock on Pageset Partition or DBD 0.000016 0020 DB2 Insert into a Data Page 0.000000 0020 DB2 Update Area Map/Spacemap Bit Changes or Whole Byte 0.000032 0020 DB2 Type 2 Index Update 0.001952 5600 Commit Prepare starting Region=0001 SSID=DB2P 0.009863 0020 DB2 Unit of Recovery Control - End Commit Phase 1 0.014200 03 Output Message Response LTerm=FUNTRM69 0.004067 35 Output Message Enqueue LTerm=FUNTRM69 Region=0001 0.000022 37 Syncpoint Region=0001 0.000024 37 Syncpoint message transfer Region=0001 0.000931 33 Free Message 0.003936 03 Output Message Response LTerm=FUNTRM69 0.007592 35 Output Message Enqueue LTerm=FUNTRM69 0.000037 31 Communications GU LTerm=FUNTRM69 0.000050 36 Output Message Dequeue LTerm=FUNTRM69 0.034227 33 Free Message 0.001001 101 DB2 Accounting SSID=DB2P SYSID=FTS1 0.132925 33 Free Message 0.002256 0020 DB2 Unit of Recovery Control - Begin Commit Phase 2 0.000127 0020 DB2 Unit of Recovery Control - End Commit Phase 2 0.002016 5600 Commit Continue completed Region=0001 SSID=DB2P 0.003950 5612 End of Phase 2 Syncpoint Program=DSN8IC0 0.000008 07 Application Terminate TranCode=DSN8CS Region=0001 0.000529 ******************************** Bottom of Data ******************************* © 2010 IBM Corporation and ICBC44
  45. 45. IBM Software Group Forwards / Backwards . . 00.00.00.000100 Time of Day . . 05.44.52.678102 Code Description Date 2006-11-07 Tuesday Time (Elapsed) / ---- ------------------------------------------------------ ---------------- E 01 Input Message TranCode=DSN8CS 05.44.52.678102This is a DB2 start of UOR: 35 Input Message Enqueue TranCode=DSN8CS 0.007919uniquely identifying the 08 Application Start TranCode=DSN8CS Region=0001 0.000807 5607 Start of UOR Program=DSN8IC0 Region=0001 0.000000transaction so that we can use 31 DLI GU TranCode=DSN8CS Region=0001 0.004315 5616 Start of protected UOW Region=0001 0.000262DB2 analytical tools should they 5600 Sign-on to ESAF Region=0001 SSID=DB2P 0.165798be required 5600 Thread created for ESAF SSID=DB2P 0.000041 ---------------------------------------------------------------------------- 0020 DB2 Unit of Recovery Control - Begin UR 1.651871 Userid=MKR IMSID=I9DE LUW=FTS1 /DB2PLU /BFAAB47AF91B/0001 URID=0003EC74CC34 ---------------------------------------------------------------------------- 0020 DB2 Exclusive Lock on Pageset Partition or DBD 0.000016 0020 DB2 Insert into a Data Page 0.000000 0020 DB2 Update Area Map/Spacemap Bit Changes or Whole Byte 0.000032This is an SMF accounting 0020 DB2 Type 2 Index Update 0.001952 5600 Commit Prepare starting Region=0001 SSID=DB2P 0.009863record. It shows high page fetch 0020 DB2 Unit of Recovery Control - End Commit Phase 1 0.014200and updated activity, as well as 03 Output Message Response LTerm=FUNTRM69 0.004067 …high CPU usage 36 Output Message Dequeue LTerm=FUNTRM69 0.034227 33 Free Message 0.001001 ---------------------------------------------------------------------------- 101 DB2 Accounting 0.132925 RecToken=I9DE/0000001900000000 CPU1=00.030586 CPU2=00.000000 I/O3=00.000000 SSID=DB2P SYSID=FTS1 GtPgRq=152 SyPgUp=11 Suspnd=0 DeadLk=0 TimOut=0 MxPgLk=6 Des=0 Pre=0 Ope=1 Fet=12 Clo=1 The IMS log termination event ---------------------------------------------------------------------------- 33 Free Message 0.002256 shows that most of the CPU time 0020 DB2 Unit of Recovery Control - Begin Commit Phase 2 0.000127 was spent in DB2 0020 DB2 Unit of Recovery Control - End Commit Phase 2 0.002016 5600 Commit Continue completed Region=0001 SSID=DB2P 0.003950 5612 End of Phase 2 Syncpoint Program=DSN8IC0 0.000008 ---------------------------------------------------------------------------- 07 Application Terminate 0.000529 UTC=05.44.54.728881 TranCode=DSN8CS Program=DSN8IC0 Region=0001 RecToken=I9DE/0000001900000000 RegTyp=MPP MCNT=1 DBDLI=0 DCDLI=2 CPU=00.046589 ---------------------------------------------------------------------------- © 2010 IBM Corporation and ICBC45
  46. 46. IBM Software Group : Get performance reports IMS Connect Investigate IMS Connect for IMS Connect, too Extensions problems, too Navigate IMS Connect Enhanced data online IMS Connect reports Reports from IMS log IMS Performance IMS Problem Analyzer Investigator Navigate IMS log online © 2010 IBM Corporation and ICBC46
  47. 47. IBM Software GroupCombined Benefits Isolate problems in complex interrelated components in hours instead of weeks, and so reduce down-time and lower staffing costs. Dissect IMS resource utilization to optimize hardware usage, identify unnecessary overhead and plan for future requirements. Enable less experienced staff to perform advanced analysis. Map the life-cycle of individual transactions to gain a better understanding of the IMS environment and to preemptively eliminate potential problems. © 2010 IBM Corporation and ICBC47

×