|
View previous topic :: View next topic
|
| Author |
Message |
Arun6578
New User
Joined: 23 Jul 2007
Posts: 9
Location: CBE
|
|
|
|
Hi,
I have a problem in my mainframe jobs. I am getting deadlock very often because of jrun.exe contention. I was left blank what can be done to prevent this deadlock issue. |
|
| Back to top |
|
 |
stodolas
Active Member
Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin
|
|
|
|
| jrun.exe sounds like a PC problem. |
|
| Back to top |
|
|
Arun6578
New User
Joined: 23 Jul 2007
Posts: 9
Location: CBE
|
|
|
|
| I have a store proc which will fetch records from this Database from Java server(Jrun.exe). When my job is trying to update the data in that particular database i am getting deadlock error. I am not sure how to prevent this issue. |
|
| Back to top |
|
|
Arun6578
New User
Joined: 23 Jul 2007
Posts: 9
Location: CBE
|
|
|
|
Even i have faced a problem like, When my job is updating the database when any online customer logged and access this database again my job will be abended with contention.
) PLAN=DISTSERV WITH 449
CORRELATION-ID=jrun.exe
CONNECTION-ID=SERVER
LUW-ID=GA9E139B.N708.14F413155933=11804
THREAD-INFO=INDAPPP:*:INDAPPP:jrun.exe
IS DEADLOCKED WITH PLAN=INDPBTC0 WITH
CORRELATION-ID=INDSSERU
CONNECTION-ID=BATCH
LUW-ID=NETAUN.ADPRD7.C1CB49D2B63C=39976
THREAD-INFO=INDJOBS:*:*:*
ON MEMBER PRD7 |
|
| Back to top |
|
|
rashmi.ranjan75
New User
Joined: 20 Feb 2006
Posts: 34
|
|
|
|
| depending on the functionality performed by the online user...changing isolation level of select can help.. |
|
| Back to top |
|
|
|
|
