How to capture PI (Program isolation) or IRLM lock conflicts?
Lock conflicts are usually fairly transient and disappear before they can be investigated.
However, while they exist, they do cause a delay in transaction responses.
The XCNF exception is intended to be used to automatically trap these occurrences. Using the XACB LIST=XCNF command, you can add an automatic screen space to the exception. (review the Appendix on Automating and Logging Features in the Omegamon Realtime Commands Reference manual
If the Automatic Screen Facility (ASF) is turned on, and a terminal is set up with the LXIMS command and automatic update, then Omegamon will log the information in the ASF screen for the XCNF exception for later review.
(Refer to the chapter on Screen Spaces in the Omegamon User's Guide (SC23-9709-02) for information on how to create such a screen space)
The ASF screen should contain such information as the active regions (RGND major command), the number of locks that regions holds (IHLD minor), the transaction (TRAN minor), the class of the current
transaction (CLAS), and so forth. This is the sort of information that can be used to review the scheduling algorithms to see if the lock conflicts can be avoided.
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.