Your SlideShare is downloading. ×
  • Like
mehr
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
152
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This is the agenda for my short presentation I am sure you are very familiar with the Distributed Relational Database Architecture and i don‘t have to explain all the pitfalls for a DRDA transaction After a very short warm up i want to explain the design and the targets of the SPEEDGAIN Gateway Monitor And I‘ll give you an impression of the benefits and costs
  • This is the management picture of a DRDA communication. As you can see there are 5 major components: The client application The Network DB2 connect also known as the DB2 gateway The Network again And the Mainframe DB2 Server
  • When we look a little bit deeper into these components we discover modules for the communication protocol, driver modules and some more subsystems especially on the mainframe The client request has to pass all these components and is answered by the DB2 Master Address Space If you have a performance problem - saying you have a long response time - please tell me which component is responsible! Where is the bottleneck? One very important feature is not shown in this slide. Do you have any idea? It is running within z/OS. Yes, it is the Workload Manager. The Workload Manager is responsible for the allocation of system resources and assigns the a DB2 subsystem when you are running data sharing
  • I don‘t know your organization. We know a lot of companies With an UDB administration responsible for DB2 connect With a DB2 administration responsible for the mainframe databases And with a network administration responsible for the client server communication The problem is: Please find out who is responsible for the performance problem
  • If you have a performance problem there are a lot of activities you can do to determine the reason for the problem
  • You can use 11 data sources to get performance data. You can start and evaluate traces and you can use commands for all involved components But … You have to synchronize these activities And If you have all traces active for a fairly long time you consume a lot of cpu time and disk space Or You use the SPEEDGAIN Gateway Monitor
  • NOTES:

Transcript

  • 1. Gateway Monitor Speedgain for DB2 - being able to look into the past October 7th, 2008 Florian Boldt, itgain, Product Manager
  • 2.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 3. The way to the DB2 z/OS DB2 Gateway (DB2-Connect) DB2 Server (DB2 for z/OS) DB2 Client (DB2-Runtime-Client) Client Network Server Network
  • 4. The way to the DB2 z/OS - in detail D B 2 C O N N E C T Client DB2 - Connect z/OS A P P L I C A T I O N C L I D R I V E R C O M M D R I V E R D E V D R I V E R T C P / I P U S S D D F D B 2 M S T R C L I E N T C O M M S E R V E R C O M M D R D A C O M M
  • 5. The Problem
  • 6.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 7. Available data sources from IBM
    • Command Level Interface Trace (Application)
    • JDBC Trace (Application)
    • DB2PD (memory settings and sysplex information from DB2 connect )
    • GET SNAPSHOT for DCS databases/applications (DB2 connect)
    • DRDA trace (DB2 connect)
    • DB2 PING (DB2 connect, Network, DB2 server)
    • NETSTAT (TCP/IP)
    • DIS DDF DETAIL (DDF)
    • DIS THREAD DETAIL (DB2 z/OS)
    • DIS DB LOCKS (DB2 z/OS)
    • Accounting Trace (DB2 z/OS)
    11 data sources! Collect at the same time and join the information
  • 8.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 9. The Speedgain for DB2 Gateway Monitor targets
      • Use all existing data sources to collect performance relevant data.
      • Collect within one snapshot and create a consistent view.
      • Store the data in a relational model to make analyzing for varying criteria easy (via SQL).
      • Keep the performance data available for days or weeks to make trend analysis possible.
    Locate the bottleneck of a DRDA transaction and show the facts for each involved component
  • 10. The Speedgain for DB2 Gateway Monitor Design
      • Take a snapshot of all in a DRDA transaction involved components at the same time and store the performance data with an unique key/timestamp.
      • Store the performance data into a DB2 LUW database to support flexible visualization and reporting.
      • Speedgain for DB2 Gateway Monitor is a tool for DB2 administrators and uses DB2 access, query and communication Techniques for internal processing
    It is too expensive and too difficult to monitor a running system via permanent traces
  • 11.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 12. Speedgain for DB2 Gateway Monitor (DB2 Connect)
  • 13. The monitoring system – Speedgain for DB2 Collect 24/7 Store / compare Analyze / compute / alert / report Speedgain collector Speedgain performance database (PDB) Speedgain GUI
  • 14. Universal Driver Support (JDBC Type 4) Application Server DB2 z/OS DDF DBM1 Application Threads DB2 Clients Aktive Connections Inaktive Connections Pooled DBATs Aktive DBATs Application Connection Pooling Thread Pooling PDB (DB2) LUW-ID JRE Speedgain UDF Speedgain JDBC Type 4 Collector
  • 15. Data Sources (DB2 z/OS)
    • IFI Records (z/OS)
        • 0001 System Statistics (DDF)
        • 0148 Data Base Access Threads (DBAT)
        • 0148 Accounting (DBAT)
        • 0148 Lock statistics (DBAT)
        • 0316 Dynamic Statement Cache
        • 0124 Active Stements
    • TCP/IP (netstat)
    • USS (Thread information, BPXPARMS)
    • MVS (RMF, CPU, SIO)
    • MVS Enclaves (WLM-API, SMF type 30 und 72)
  • 16. Data Sources (DB2 connect, Network, Application)
    • DCS Snapshot Data
        • DCS Gateway Database Data
        • DCS Application Data
        • DCS Statement Data
        • DCS Transmission Data
    • DB2 PING
    • Native Ping
    • Universal Driver (JDBC Type 4)
  • 17.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 18. Cost of operation
    • Hardware for collector and Performance Data Base
    • DB2 connect resources (snapshots) / JDBC exits and fetch process
    • Network traffic
    • Mainframe CPU time (DB2 trace and UDF)
  • 19. Cost of operation
  • 20.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 21. Benefits
    • Easy to install and easy to maintain
    • 24 x 7
    • Threshold Control Center (threshold violations)
    • User Exit for threshold violations
    • Historic Mode
    • High Level Monitoring (DCS information only)
    • Data Sharing support
    • Workload Graphs
    • Hitratios
  • 22. Gateway Monitor Screenshots
  • 23. Gateway Monitor Screenshots
  • 24.
    • Speedgain for DB2 Gateway Monitor
        • DRDA – The way to the DB2 for z/OS
        • Conventional Problem Determination
        • Speedgain targets and design
        • Speedgain architecture and data sources
        • Cost of operation
        • Benefits
        • Recommendations for collector settings
    Agenda
  • 25. Recommendations for collector settings Problem determination
  • 26. Recommendations for collector settings Monitor a well running system (save resources)
  • 27. Speedgain Gateway Monitor Trial is available
  • 28.
    • Questions, Trial Request, Comments?
    • European Sales:
    • Nils Kaden
    • [email_address]
    • US Sales:
    • Stephen Rubin
    • [email_address]
    • further information: http://www.itgain.de
  • 29. Questions