Iseries object lock monitor and report
Posted on 2009-07-01
Is there a way to setup a collection service and/or report that will provide object lock information for objects that generate contention errors? We have a program that runs unattended that periodically encounters an allocation issue for a variety of files, typically due to an end user's exclusive access. By the time we see the error in the joblog, the contention no longer exists and we have no way of following up with the party that caused the problem. We use WRKOBJLCK to investigate issues presented during our attended monitoring, but there is no way to go back in time to see what caused the contention for an event that happened during our unattended hours.