JDBC "How to" series part 1: How to use WLM with the DataDirect Connect for JDBC DB2 driver

Welcome to the new DataDirect JDBC Blog! This is my first post; however, rather than spending the first post exchanging pleasantries I would instead like to dive right into something with some real substance: a “How to” series highlighting answers to some of the questions I encounter on a regular basis. In Part 1, I will answer the question: “How do I use WLM on zOS with our DataDirect Connect for JDBC DB2 driver?”

WLM is the Work Load Manager for zOS. The purpose of WLM is to allow a user to specify performance goals and assign business importance to each goal. For instance, if you want to ensure that 70% of the transactions using the Connect for JDBC driver complete within 1 second, you would use WLM to configure a rule to do so. WLM keeps track of the work running on the system and configures system resources to try and meet these goals in the most efficient manner possible.

In order to create such a rule for the DataDirect Connect for JDBC DB2 drivers, you must set the subsystem type to DDF. You can then use any of the following 5 qualifier types to custom tailor your rule:

Armed with this knowledge, you can use WLM to create performance goals on zOS for the Connect for JDBC DB2 driver today. I would like to give many thanks to Gregg Willhoit, Chief Software Architect for our Shadow products, for expanding my zOS and WLM education as well as providing insight and guidance to this post.

Tech Tags: WLM JDBC DB2 correlation+information plan+name user+id collection+name packagecollection work+load+manager mainframe zOS performance