The final instalment - DB2 for z/OS Locking for Application Developers Part 10

This is the last article in the series by Gareth Copplestone-Jones on locking for developers, and is a wrap up of miscellaneous points arising from previous articles.


Row level locking

The first item under discussion is row-level locking. I mentioned previously that the design default lock size should be page-level, with row-level locking only being used where justified. This is to reduce the CPU and elapsed time overhead typically incurred by row-level locking, and especially to avoid the data sharing overhead involved. The DB2 for z/OS documentation has further information about locking in a data sharing environment, but for the purposes of this article it’s important to stress that row level locking in a data sharing environment can and typically does introduce significant overheads.

Continue reading the final instalment in Gareth Copplestone-Jones series of blogs on DB2 for z/OS Locking for Application Developers. 


Views: 11

Add a Comment

You need to be a member of The World of DB2 to add comments!

Join The World of DB2

Bringing Db2 enthusiasts together virtually. Expert or novice, distributed or mainframe, this is the place for everything DB2.


Register Now IBM Data Tech Summit virtual event October 6th!

Started by Surekha in What's hot ? Sep 24. 0 Replies

Data Tech Summit Virtual Event - The Latest News on Enterprise Data & AIDate:  Tuesday, October 06, 2020Time: 11:00 AM Eastern Daylight TimeRegister NowBusiness cycles are…Continue

Introducing IBM Db2 for z/OS Developer Extension for Microsoft Visual Studio Code

Started by Calene Janacek in Application Development and DB2 Jul 30. 0 Replies

We are excited to announce that the first iteration of IBM Db2 for z/OS Developer Extension is available now as a free downloadable extension in the…Continue

© 2020   Created by Surekha Parekh.   Powered by

Badges  |  Report an Issue  |  Terms of Service