IBM Db2 - The Ultimate Database for Cloud, Analytics & Mobile
By Gareth Copplestone-Jones, Triton Consulting
This is the third article in the series on locking for DB2 for z/OS developers. To recap, data integrity and application performance are dependent on application programs being designed and coded to take into account the locking strategy used and working in collaboration with the DBMS. The previous article concentrated on lock size and discussed gross locks and intent locks at the tablespace level; in this article I go into more detail about lock modes, and discuss incompatible locks.
Add a Comment