I just now tested your suggestion with command: CHGUSRPRF
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 . . . . . . :
Message . . . . : Query definition is larger than allowed by user
Cause . . . . . : The storage needed to save the query definition
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
Change User Profile (CHGUSRPRF) command to increase the amount of
storage on the system that can be allocated to your user profile for
your query definitions.
I had this problem once with users that were prone to write badqueries. We used the MAXSTG parameter on all their user profiles.
This way they could continue to execute valid long running querieshowever 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
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact