|
View previous topic :: View next topic
|
| Author |
Message |
Souparno
New User
Joined: 09 Sep 2008
Posts: 7
Location: India
|
|
|
|
Hi,
In my system I have few VSAM files which are updated by online users and also batch processes at the same time. This is resulting in contention / deadlock with multiple processes (between concurrent online users and / or batch processes). The net effect is either delay processing or, online users not able to do processing.
I am not very comfortable with VSAM. Would like to know whether there is any way to capture the VSAM contention exception which will help in handling the scenario by application programming (something which I could have done in case of DB2). |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| In my system I have few VSAM files which are updated by online users and also batch processes at the same time. |
Bad application design -- it can easily result in contention and deadlocks.
As far as I know, there is no "VSAM contention exception" that you can capture. There is system data about contention but it's not a trappable exception -- more a notification about the contention. |
|
| Back to top |
|
|
|
|
