×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Brad,
Thanks.
I just now tested your suggestion with command: CHGUSRPRF
USRPRF(TRAINING) MAXSTG(30)
Logged on as TRAINING and created a Cartesian join Query/400 against a
couple large files.
Got this message. Your recommendation has definite possibilities.
Message ID . . . . . . : QRY6011 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 02/11/13 Time sent . . . . . . :
16:47:43
Message . . . . : Query definition is larger than allowed by user
profile.
Cause . . . . . : The storage needed to save the query definition
exceeds
the storage limit specified for your user profile.
Recovery . . . : To save this query definition, ask the security
administrator or the security officer to use the MAXSTG parameter on
the
Change User Profile (CHGUSRPRF) command to increase the amount of
auxiliary
storage on the system that can be allocated to your user profile for
storing
your query definitions.
+++++++++++++++++++++++++++++++
I had this problem once with users that were prone to write bad
queries. We used the MAXSTG parameter on all their user profiles.
This way they could continue to execute valid long running queries
however it would blow up if a temporary file or something else got out
of hand (which is usually the result of a run-away query
midrange.com
