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).