Re: Query Question

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

We intercept any requests to run queries and use the system APIs to 
change the profile under which the query is running to "QUERYUSER" 
(just a user profile we created).  We wanted a profile that had no 
authority to change production files (as in creating an output file 
in a production library with the same name as a production file-- 
replacing it).

When the user takes a menu option to WRKQRY, the profile is swapped. 
When the user returns to the menu, the profile is swapped back to the 
user's individual profile.  We do similar things with queries 
submitted to run in batch.

Since all queries run as a single profile you can then allocate a 
maximum memory to that profile.

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx




> We had a query run by our QA department that caused our development
> system to crash on Friday night.  The query created a file of over 100
> million records and was 20% of the 1.3 terabyte of storage.
> Is there a way to limit the size of a file a query can produce?  We do
> not know at this time, if the query was run in batch or interactively.
> We can not limit the size by profile, due to group profiles.
> Any help is appreciated.
>
> Bruce Barrett