Académique Documents
Professionnel Documents
Culture Documents
Wayne Slomiany
January 29, 2008
Agenda
2
Targeted DB2 Data for Testing
Testing Audit
Reports
3
Less Data, Less Resources
• Referential Integrity
• Application Relationships
5
Data Relationships
Production
Subset
Extract
Distributed
6
z/OS Relationships
Production
AR/RI
z/OS
7
Efficient Coding Practices
8
Pro-Active Application Relationship
Management
9
Pro-Active Application Relationship
Management
10
Create a Baseline of the Application
11
Benefits of DB2 Stored Procedures
Browser Middleware
Data
Servers
S390
Servers
12
DB2 Stored Procedures
13
DB2 Stored Procedures
14
DB2 Stored Procedures
15
DB2 Stored Procedures Challenges
Added Complexity
Analysis
Programmer Familiarity
Debugging Project Deadlines
- PLUS -
Testing Prevent Problems
16
XPEDITER for DB2 Stored Procedures
-------------------- XPEDITER/TSO - Process DB2 Store Procedures --------------
COMMAND ===>
Jobcard Information:
===> //PFHRAS0 JOB (#ACCONT),CLASS=A,MSGCLASS=X,
===> // MSGLEVEL=(1,1)
17
XPEDITER for DB2 Stored Procedures
----------------------- XPEDITER/TSO - SELECT JOB STEP ----- Row 1 to 1 of 1
COMMAND ===> SCROLL ===> PAGE
Dataset: 'SYS1.PROCLIB(D61WLM2)'
18
XPEDITER for DB2 Stored Procedures
------------------------- XPEDITER/TSO - SOURCE ------------------------------
COMMAND ===> SCROLL ===> CSR
BEFORE BREAKPOINT ENCOUNTERED
** END **
19
Resolving DB2 Application Abends
20
CICS Application Abend
• Locate the task interface element (TIE) for “DSNCSQL”.
• Locate the CICS Life of Task (CLOT) in the TIE for DSNCSQL. Locate the
SQL-PLIST using the pointer (CLOTPARM) from the CLOT.
• Validate the SQL-PLIST by locating the DBRM name once the SQL-PLIST is
verified, the statement number, type, APARM (INPUT Host Variables)
address, VPARM (OUTPUT Host variables) address, timestamp and pointer
to the SQLCA have been located.
• To locate the SQLCODE, use the SQLCA pointer from the SQL-PLIST.
• Once located, the SQLCODE must be converted from HEX to DECIMAL
before it can be used. For example, A -302 displays as “FFFFFED2” in the
SQLCA.
• Look up the SQLCODE in the DB2 message and codes manual. The
message text does not offer much more than an explanation.
• There are seldom any suggestions as to the cause of the problem.
• The statement number is used to locate the SQL statement in the
precompile listing.
21
Using Correlation
22
23
24
25
Application Management Solution
Reduce excessive resource consumption at the root cause
through a proactive and systemic approach.
26
External Influences
Database
Utilization
Delivery Stats
Server Performance
Database
Servers
Application
Servers
Web Servers J2EE and .NET Analyzer
Service Dashboard
Top Server Traffic
WAN Utilization
Response Times
Performance Overview
27
Distributed MQ Application
Reply 1
1. Web application
3. Traced the MQ message
Request 2
was occasionally
flow and saw that the 2033 4. Analyzed the
failing.
was due to sluggish Reply 2 performance of the
response from the mainframe application –
2. Became aware of and saw a significant
mainframe application.
problem in real time Request3
issue with MQ system-
(without any user level tracing during
interaction). Also got Reply 3
bursts of activity.
background information:
unexpected 2033.
Request 4
Pdarep2
Pdaaggr.exe
Reply 4
Answer
28
MQ Performance Impact
29
Environment Tuning
• Evolving applications • Reactive, fire-fighting
introduce more potential mindset
points of failure
• Limited expertise and
• Environmental skills
complexity contributes to
resource growth • Mainframe costs
(hardware and software)
• Gradual MIPS are driven by MIPS
consumption can go
undetected
30
Dynamic SQL Queries
31
DB2 Environment Considerations
32
Current Application Performance Metrics
33