View previous topic :: View next topic
|
Author |
Message |
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
I just started working for a group that is using mainframe DB2 as their backend for a distributed system.
This morning, there was a question like "what is locked up?"
I remember being able to use system tables to track down a deadlock on a server DB years ago. I never really kept up with the system side of DB2, so I I don't know if we can do that.
Everything I find talks about the snapshot_ functions, which I think are only for UDB.
So, how does an application programmer track down a deadlock? I'm not an admin. |
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
Many years ago, I think I used to look in SDSF at the MSGUSR DDNAME of the region involved to see what was deadlocked with what. Very rusty in that area though. |
|
Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008 Posts: 1020 Location: India
|
|
|
|
Hi Ed,
If related to deadlocks and timeouts, you can find the related information like who was holding it in the DB2 MSTR(ssidMSTR) log in spool.
If you have DB2-Insight, you can also check Current Contention(Main Menu, Active Threads --> Option 3(Curr Contn)
Thanks,
Sushanth |
|
Back to top |
|
|
|