1 / 48

Introducing IBM Transaction Analysis Workbench for z

2. Agenda. Introduction. Overview of the ISPF dialog. Scenario: IMS DB2 problem. Batch SMF and OPERLOG reports. 3. It's all about evolution. . 1980: in-house users only; simple data, single data store. 2011: users are customers; data is complex, often distributed. Transaction Manager: IMS DC or CICS.

Patman
Download Presentation

Introducing IBM Transaction Analysis Workbench for z

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. 1 Introducing IBM Transaction Analysis Workbench for z/OS Pittsburgh and Philadelphia Users groups Jim Martin US Representative, Fundi Software

    2. 2 Agenda

    3. 3 It’s all about evolution

    4. 4 Analysis tools have not kept pace

    5. 5 Product overview A transaction analysis framework for System z Not transaction manager specific Leverages current IBM tools for transaction analysis Not IMS or CICS specific, but first release provides more synergy with the existing tools for those transaction managers Automates collection of data needed for problem analysis Provides a session manager to manage problem analysis through its lifecycle In this presentation, it might look like the Workbench is IMS or CICS centric but that is not the case The tools for IMS and CICS are the first to be engaged

    6. 6 Product goals Enable higher productivity by lower skilled staff, reduce problem analysis time, and serve as a training tool for new support staff Allow the “first responder” to determine the most likely source of the problem so that the right subject matter expert can work on the problem Allow for “deep dive” problem determination via synergy with other IBM tools Create a “common” approach to transaction problem resolution Increase the degree and ease of collaboration in problem resolution

    7. 7 Session manager (ISPF dialog) Session manager approach to problem management: Register the problem Locate the files required to diagnose the problem: IMS, DB2, CICS, SMF, OPERLOG etc. Resume from where you left off, or from a previous save-point Write reminder notes and information as you go Re-assign the problem to the appropriate subject-matter expert Use PI-style interactive analysis to look at related logs and other subsystem events via SMF, OPERLOG etc. Run reports that are specific to the problem

    8. 8 Components Automated file selection utility currently works with: DB2 log files IMS log files IMS Connect Extensions journalsAutomated file selection utility currently works with: DB2 log files IMS log files IMS Connect Extensions journals

    9. 9 Overview of the ISPF dialog: main menu Option 0 Profile contains settings for the current user. Option 1 Sessions provides a structured framework for analyzing problems (each session has its own list of log files; an alternative to option 4) Option 2 Controls defines “controls”, including: Filters: which records you are interested in Forms: which fields you are interested in IMS user log records Option 3 Systems defines systems (such as IMS and DB2) that you can use to automatically select the appropriate log files for a problem Option 4 Process provides an ad-hoc list of log files for analyzing problems (an alternative to option 1)Option 0 Profile contains settings for the current user. Option 1 Sessions provides a structured framework for analyzing problems (each session has its own list of log files; an alternative to option 4) Option 2 Controls defines “controls”, including: Filters: which records you are interested in Forms: which fields you are interested in IMS user log records Option 3 Systems defines systems (such as IMS and DB2) that you can use to automatically select the appropriate log files for a problem Option 4 Process provides an ad-hoc list of log files for analyzing problems (an alternative to option 1)

    10. 10 Scenario: IMS DB2 problem On the following slides, we present an example scenario: a user has reported a long transaction response time for an IMS transaction performing DB2 updates

    11. 11 IMS DB2 problem: creating a session

    12. 12 IMS DB2 problem: adding log files

    13. 13 IMS DB2 problem: batch reporting

    14. 14 IMS DB2 problem: IMS PA reporting

    15. 15 IMS DB2 problem: IMS PA reporting

    16. 16 IMS DB2 problem: SMF reporting

    17. 17 IMS DB2 problem: SMF reporting

    18. 18 IMS DB2 problem: SMF reporting WebSphere MQ

    19. 19 IMS DB2 problem: creating an IMS transaction index An IMS transaction index is a specialized extract file that IMS Performance Analyzer creates from an IMS log (such as an SLDS). Each record in the index represents an IMS transaction and contains cumulative information from the IMS log about that transaction. IMS transaction indexes are especially useful in Workbench for identifying problematic IMS transactions, because they contain fields that offer cumulative information about an IMS transaction that are not available in any single IMS log record. For example, the Process field in an IMS transaction index record contains the total processing time for an IMS transaction. The order of the log files in this list is significant: the IMS transaction index appears first, so that, when we browse the files, each IMS transaction index is displayed before its corresponding IMS log records. (To reorder log files in the list, enter M next to the log file that you want to move, and then enter A next to the file that you want to move the selected file after, or enter B next to the file that you want to move the selected file before.)An IMS transaction index is a specialized extract file that IMS Performance Analyzer creates from an IMS log (such as an SLDS). Each record in the index represents an IMS transaction and contains cumulative information from the IMS log about that transaction. IMS transaction indexes are especially useful in Workbench for identifying problematic IMS transactions, because they contain fields that offer cumulative information about an IMS transaction that are not available in any single IMS log record. For example, the Process field in an IMS transaction index record contains the total processing time for an IMS transaction. The order of the log files in this list is significant: the IMS transaction index appears first, so that, when we browse the files, each IMS transaction index is displayed before its corresponding IMS log records. (To reorder log files in the list, enter M next to the log file that you want to move, and then enter A next to the file that you want to move the selected file after, or enter B next to the file that you want to move the selected file before.)

    20. 20 IMS DB2 problem: interactive investigation

    21. 21 IMS DB2 problem: interactive investigation

    22. 22 IMS DB2 problem: defining a filter

    23. 23 IMS DB2 problem: defining a filter

    24. 24 IMS DB2 problem: interactive investigation

    25. 25 IMS DB2 problem: transaction tracking

    26. 26 IMS DB2 problem: tracking (with relative elapsed time)

    27. 27 IMS DB2 problem: interactive investigation

    28. 28 IMS DB2 problem: interactive investigation

    29. 29 IMS DB2 problem: interactive investigation

    30. 30 IMS DB2 problem: interactive investigation

    31. 31 IMS DB2 problem: interactive investigation

    32. 32 IMS DB2 problem: interactive investigation

    33. 33 IMS DB2 problem: tagging a specific log record Users can resume browsing at a tagged record by selecting the tag in the session history. Users can resume browsing at a tagged record by selecting the tag in the session history.

    34. 34 IMS DB2 problem: DB2 Log Analysis Tool

    35. 35 IMS DB2 problem: interactive investigation

    36. 36 IMS DB2 problem: interactive investigation

    37. 37 IMS DB2 problem: interactive investigation

    38. 38 IMS DB2 problem: interactive investigation

    39. 39 Scenario 2: The end The cause of the IMS transaction problem has been narrowed down to a slowdown in DB2 Sufficient information about the DB2 update activity has been collected and can be passed on to the DB2 DBA for further investigation

    40. 40 OPERLOG report: JCL

    41. 41 OPERLOG report: output

    42. 42 SMF 33-2: APPC/MVS Conversation List report

    43. 43 SMF 79-15: IRLM Long Lock Detection report

    44. 44 SMF 101: DB2 Thread Accounting Summary report

    45. 45 SMF 116: WebSphere MQ Accounting reports Workbench provides WebSphere MQ Accounting reports for SMF 116-0 (accounting class 1 records) and SMF 116-1 (accounting class 3 records), in list and summary formats, in a variety of sort orders.Workbench provides WebSphere MQ Accounting reports for SMF 116-0 (accounting class 1 records) and SMF 116-1 (accounting class 3 records), in list and summary formats, in a variety of sort orders.

    46. 46 SMF 30: Address Space Activity report

    47. 47 SMF 70-1: RMF Processor Activity report

    48. 48 Summary: Transaction Analysis Workbench Companion to the popular IMS and CICS Performance Analyzer tools, allowing systems programmers to look outside of IMS and CICS for the source of problems Exploits the wealth of system performance and activity information available in SMF, OPERLOG, and event traces Allows medium-skilled analysts to perform expert analysis of their enterprise

    49. 49 More information IBM DB2 and IMS Tools website: www.ibm.com/software/data/db2imstools/ IBM Transaction Analysis Workbench for z/OS: www.ibm.com/software/data/db2imstools/imstools/trans-analysis/ Jim Martin, US Representative, Fundi Software: jim_martin@fundi.com.au

More Related