cferlan

Deadlocks Nearly OOAK records

Discussion created by cferlan on Apr 26, 2011
Latest reply on May 1, 2011 by Gary_Cherlet
Gentlemen, ladies,

We have a situation here where we are getting a lot of deadlocks.
Recently, a lot more users have gained access to our mainframe systems, internal and external users (via WWW).
Years ago, this application was not designed for managing that kind of volume of transactions. What we have is very few records used to log users activity by type (not many types so not exactly OOAK). That means all users, and that log constitutes a real bottleneck.
We are looking for a solution to at least alleviate the problem, if not eliminate it, short of a redesign because that would imply hundreds of COBOL compiles, more hundresds of dialog regenerations, not to mention the TEST time required for DEV and QA.
Do you have any recommendations/ideas/alternatives about avoiding/eliminating deadlocks as much as possible when so many users access so few records ?
Thank you, Claude Ferland.

Outcomes