July 24, 2008 at 6:21 am
Hi,
I have report that calls a SP (SP1) that executes a SP (SP2) on DB2/400. This SP is very resource intensive an runs for a couple of minutes after optimisation. The report can not be scheduled as the user(s) of the report need up-to-date-information i.e. they make modifications and want to see the effects immediatly on the report. In order to avoid unnecessary load on the iSeries, I want to secure that the SP is only called by one report at a time. I considered using a control table with an active/inactive flag managed by SP1 but would prefer a solution based on built-in functionality if possible.
Thanks for any good suggestions.
July 24, 2008 at 8:22 am
I don't think that there is a builtin way to restrict the # of users that run a report concurrently. I think you will have to go with checking a flag value before calling the DB2 procedure.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 24, 2008 at 9:17 am
Thanks Jack,
Seems to confirm what my colleagues and I found out.
I do believe however that it would be a nice add-on to Report properties in a future version/SP. I find it hard to believe that we are the only ones who want to secure that resource-intensive reports are not executed in parallel.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply