Setting your Db2 zParms to the right values can be a never ending task, but luckily the previous article from Emil Kotrc (found here), gave a structure on what you’ll find, and several pointers so you can study some recommendations from other Db2 users and see how that fits to your site.
The other side of the picture, as it is also mentioned there, is that we live in a big world of “it depends” situations. zParms will take an effect over the entire Db2 subsystem and its applications, therefore it means that in most cases you’ll need to take the following steps:
- Study your environment over time.
- Study the zParms that can bring the best optimal conditions to your Db2.
- Find a theoretical value you wish to set for your zParms.
- Negotiate with the application owners for this value, the impact, and a time frame so you can execute the change. (And yes, ideally you should test with them if the new values brought the expected benefit).
The problem is quite clear, as in many cases, you’ll reach situations where the ideal value of a zParm doesn’t match your application’s point of view. In this article, we’ll take a look at one such scenario and how you can take advantage of other Db2 features to accomplish the task without any zParm change.
