Batch DB2 And MQ The Easy Way
MartinPacker 11000094DH Visits (4436)
Here are are two questions people would like easy answers to:
This post shows you how to answer both these questions without DB2- or MQ-specific instrumentation.
The “without DB2- or MQ-specific instrumentation” phrase is important: I’m working with a customer with something like 50 DB2 subsystems and many MQ subsystems. You can’t really take product-specific SMF from all of those.
But most installations collect SMF 30 data, which is what this method relies on.
In fact I’ve just enhanced our tools to make these two questions easy to answer - with single table queries.
The key to this is the SMF 30 Usage Data Section:
With these simple rules it’s easy to write the queries that answer the questions at the top of the post.
You can also use this method with IMS, with only very minor modifications. My current customer engagement, though, doesn’t include IMS.
We usually detect dependencies between jobs by examining the access to data sets:
This is fine for data-set-driven dependencies.
You can’t use these records for DB2- or MQ-driven dependencies. The bad news is you can’t get dependency information from SMF 30 either. For this you have to examine the appropriate Accounting Trace records:
And neither of these tell you what other job (step) this one is dependent on. You just get evidence of write and read activity, which helps.
In the study that inspired this post we can readily see which DB2 subsystems support the “big CPU” jobs and we needed that to direct our DB2 specialist to focus his attention on just these of the many subsystems this customer has (even on a single system) .