Will ""PROCOPT = A"" make deadlock??

VarunJ1991 · New User Joined: 01 Oct 2012 Posts: 2 Location: INDIA

HI ALL.

Just a quick clarification i can see in detail tat PROCOPT = A wil lock the region till update or read. Since if someone uses PROCOPT=A in PSB for a PCB which is used only for read it will lock obviously. Suddenly to clear this doubt i took one PSB and i referred which it got deadlock recently i can see tat PCB is used with PROCOPT = A.. Almost all the PCB is used in tat PSB used with PROCOPT = A. Can someone please explain this if modification the PSB with correct PROCOPT option will correct the issue? Means read procopt for the read calls write for write and delete for the same(Just for clear explanation).....we are facing deadlock issues often. (DON't teast me if me clarification is childish

Gary McDowell · Active User Joined: 15 Oct 2012 Posts: 139 Location: USA

IMS locking is tricky. It can be a database or application design problem, or the amount of syncpoints. There is a Deadlock report which your IMS DBA should be able to review with you.

But to answer your question I do not think Proc Option 'A' is "thee" answer but it could be a factor. You need to look at the whole picture which your DBA can help you with.

Good luck.

Anuj Dhawan · Posted: Tue Mar 12, 2013 8:18 pm

Procopt 'A' may lock IMS database blocks - this means that you may well lock out other applications that are trying to read segments in the same physical block if you are just issuing GN or GU calls with procopt 'A'. But yes, there can be more to the situation and working with your IMS DBA is a good choice, as Gary has said.