Improving performance for multiple users: Locking and concurrency
DB2 uses locks on user data. The main reason for using locks is to ensure the integrity, or accuracy, of the data. Without locks, one user might be retrieving a specific data item while another user might be changing that data. The result is that the first user retrieves inaccurate data. In the DB2 UDB for z/OS environment, which includes vast amounts of data and large numbers of users and transactions, the prospect of inaccurate data is unacceptable. Therefore, DB2 UDB for z/OS provides comprehensive locking to ensure data integrity.
Despite the importance of data integrity, locking can sometimes be too restrictive. If an application process locks too much data, other users, utilities, ...
Get Official Introduction to DB2® for z/OS®, The, 2nd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
