×
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 Ron
I once messed with this value to stop pesky developers from running queries
interactively ;)
My advice would be not to set it system wise; this would affect every query
on the system including OPNQRYF queries in my original experimentation and
probably SQL these days. It's been a while so you may want to see if this
is still true but obviously tread warily as it could have quite an impact.
What I used it for was to limit access to interactive query and simply
prevented queries running. If the query optimizer determined that the query
would take longer than the time limit it issued a message offering the
opportunity to cancel or continue. This was obviously not ideal in batch
jobs :) I overrode the message with a message reply to cancel the
operation. Couldn't be monitored as I recall but things may have changed
and I am no message guru anyway.
I guess how you set this value depends on what you want to achieve so I
don't think I can offer you any other advice.
Regards
Evan Harris
At 02:56 a.m. 3/05/2005, you wrote:
Does anybody have a System Value set other than *NOMAX? If so, what did
you set it to?
What is the general consensus on setting this value, job-wise, and-or
system-wise?
Ron Adams
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
