IT'S ALL ABOUT THE DATA.
 Follow us on Twitter! Add us on Facebook! Add our RSS feed!

Can You Control a DB2 for z/OS Client-Server Workload? Yes.

Imposing order on distributed data facility workloads

By

  • http://twitter.com/Pfitschepfeil Karl Griesser

    One of the best improvement in the past years was that WLM finally takes MAXDBAT into account in his dispatching algorithm.

    This took IBM forever to implement and is still sometimes a mess which can be painful if some members in a Data Sharing group crash and all workload is dispatched to a member that already hit MAXDBAT.

    So in my opinion IBM should put more resources in getting feature that are already in the product to a stage where they may be used instead of extending the feature list with some nice to have stuff that will only be used by a minority of customers.

    • Robert Catterall

      Thanks for speaking up, Karl. MAXDBAT limit pressure can indeed occur if, as you’ve noted, a member of a DB2 data sharing group fails (particularly if the group only has two members and processes a lot of DDF work). I believe that DB2 10 for z/OS will help to address this situation by enabling organizations to support 5 to 10 times the number of concurrently active threads on a DB2 10 subsystem versus a DB2 9 or DB2 Version 8 environment (the big increase in concurrently active threads per subsystem can be achieved when packages are bound or rebound on the DB2 10 system).