If your environment uses commit cycle processing, it is possible for commit cycles that are open for an extended time to cause a deadlock condition for database apply processes. If MIMIX cannot automatically resolve the deadlock, the condition is reported. The value *DLK is displayed in the Open Commit column on view 1 of the Data Group Database Status display (Figure 18) and a message in the database reader (or send) process job log identifies the job that started the long commit cycle. The condition also triggers email notification for users who have a subscription configured within the Assure Unified Interface that includes this event.
To resolve the deadlock condition, do the following:
From the target system, use the WRKMGLOG command to display the message log.
Look for message LVE311D. The message identifies the job started the long commit cycle.
Take the appropriate action for the job holding the commit cycle open to either commit or rollback the commit cycle.
Once the commit cycle has been resolved, MIMIX will be able to automatically clear the deadlock condition.