By Gareth Copplestone-Jones
If you attended Gareth Copplestone-Jones' presentation at IDUG EMEA and want to learn more about Db2 Locking, here’s where to start.
This Db2 for z/OS Locking blog series is mostly targeted at Db2 for z/OS application developers, but is also appropriate for application designers, database administrators, Db2 systems programmers and other Db2 professionals who are concerned with data integrity and application performance.
You might ask, what’s that got to do with locking? It’s all too easy to assume that locking just happens and that you don’t need to worry about it. Nothing could be farther from the truth: if you don’t understand the Db2 locking mechanism and the way it is affected by BIND options, then it is very easy for your application to compromise data integrity, or to deliver poor performance – or both. This series of articles is intended as a practical guide to how and why Db2 locks data that will help you avoid the programming pitfalls that can compromise the holy grail of data integrity. If you’re already a seasoned professional, then I encourage to read on as there might be some useful pieces of information for you.
The objective of this series is to help you understand:
Why locking is important.
The concepts of Db2 for z/OS locking.
How Db2 locking behaviour is affected by BIND/REBIND options.
How to code update applications to avoid data anomalies and guarantee data integrity.
How you can improve performance by taking as few locks as possible.
Continue reading Part 1 of 10 on Db2 for z/OS Locking by Gareth Copplestone-Jones.
Comments