On Fri, 9 Jan 2015 09:58:03 -0500, Ted MacNEIL <[email protected]> wrote:
>I'm one of those types. >The governor pretty well guarantees a re-submission. >Which means twice the resources (or more) spent to do nothing! > >How can they debug/tune something if we don't let complete? > That does seem to be a prevailing thought. And it's not an inherently bad one. To me the decision to use the governor in production is a matter of risk management. I should have mentioned that the governor limit in production should likely be very high. My point with it is to stop those things that individual users have submitted that have run for hours. How many hours is acceptable? That depends on the shop and your philosophy for how many hours you're willing to let something run that either may never complete or may not have a user sitting behind it waiting anymore. I have seen queries run all weekend. I've seen queries run all night. Such cases can have an impact on the R4H. As well as other work that needs the DB2 resources it's consuming. I'm not in favor of allowing things that aren't pre-approved to run for days, or even a substantial portion of a day. Note that the governor is controllable by authid. IIRC, you can have an overall default limit and specific limits for specific ids. So if you have that one process that really needs to run a 36 hour query, then you could make sure that they're running in their own process id and give that id a limit that allows such. Best of course is to have your DBAs actively watching for DDF queries that have been on the system for more than an hour (or two or whatever) and have them investigate them to see if there really still is a user waiting at the other end and if the query has a chance of completing. But such a manual process will not catch everything. Of course, having an IDAA in the mix can help avoid utilization on z/OS as well as improve response time to the business users. But that's not free, nor something you can turn on in a day. Scott ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
