|
View previous topic :: View next topic
|
| Author |
Message |
pingte
Active User
Joined: 03 Dec 2005
Posts: 120
Location: india
|
|
|
|
Hi,
In my System one job failed with U0777 abend (Which is IMS deadlock).
From the spool is it possible to identify which job was locking the database and which database was locked out leading to U0777.
(I don't have the spool with me ... it is lost). |
|
| Back to top |
|
 |
nuthan
Active User
Joined: 26 Sep 2005
Posts: 146
Location: Bangalore
|
|
|
|
| When DB2 detects a deadlock, the ESAF enhanced message handler module (DFSESPR0) directs the IMS ILOG macro to log an exceptional condition x’67FF’ SNAP trace record to identify the problem, and the application abends with the U0777 code. |
|
| Back to top |
|
|
pingte
Active User
Joined: 03 Dec 2005
Posts: 120
Location: india
|
|
|
|
| nuthan, as per ur answer, i need to look in the IMS log to c which job is causing the deadlock? |
|
| Back to top |
|
|
nuthan
Active User
Joined: 26 Sep 2005
Posts: 146
Location: Bangalore
|
|
|
|
| yes, look in to the log |
|
| Back to top |
|
|
pingte
Active User
Joined: 03 Dec 2005
Posts: 120
Location: india
|
|
|
|
| Appreciate the reponse.. it was helpfull! |
|
| Back to top |
|
|
|
|
