This article explores the settings that take advantage of the Db2 for z/OS continuous delivery features when dynamic SQL applications are using a JDBC type 4 connection.
Db2 Batch processing has long been considered a mainframe only domain. Many enterprise domain applications require bulk processing of large volumes of data for critical environments. But,what if we could offload some of the batch process handling of mainframe jobs to Linux servers using Java?
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.