The third episode of our series deals with distributed access to DB2 for z/OS. In order to answer the questions from this section, you should be familiar with JDBC, ODBC, .NET and you should understand how to configure them and how to connect to DB2 using these technologies.
What’s the main difference between single-row and multi-row inserts? Simply the performance. If you are inserting many rows in a loop via a single-row insert, you call DB2 for every single row, which means you spend some time for the communication with the DB2.
We hope that you’ve enjoyed this month’s articles on DB2 performance on z/OS.
We talked about the new performance possibilities in DB2 11, about performance hints and tips for framework development, about explaining tuning to C-level and about efficient ways of replication.
This month’s theme is DB2 for z/OS performance, to start us of is an article by Ludovic Janssens of Infocura. In his article “JAVA frameworks for JDBC access”, he talks about the different performance choices and pitfalls that come into play when developing using frameworks.
Rodney Krick has made available an analyzer for the DB2 JCC Trace on the IDUG Codeplace here -
He has written a tutorial on how to use it, which we are delighted to share with the IDUG Community -