×
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.
Hello All. I've been off of the list for
a while and recently
re-subscribed now that I've once again had additional AS/400
responsibilities thrown at me - but it's nice to be back.
Recently an old ongoing problem has reared it's ugly head and caused
me
fits - that of rogue users running queries interactively during
normal
business hours. This of course results in numerous complaints
about
response time, etc. As I recall from way back then, there really
wasn't
a whole lot one could do to stop or restrict these miscreants.
However
quite some time has passed (since I've been involved or concerned
about
the issue anyway), and I wondered if there has been any new light shed
on
the matter. Also, we've since upgraded from V3r1 to V3r2 - any
changes
there that might help?
I hope I'm not beating a dead horse here - my apologies if that's
the
case. Either way, I'd appreciate any feedback (short of
anything
resulting in insult or injury, that is). Thanks in
advance!
Here's the page from my system values presentation. Note that the
inquiry message could be dealt with the system reply list. Also
note that this limit can be changed for any job with the CHGQRYA
command. (These functions should have been included in the CHGJOB
command. Only God knows why they were'nt.)
Al
Name:
QQRYTIMLMT
V3 R7.0
Description: Query processing time limit
IBM Initial Value: '*NOMAX'
Length & Type: Character: 10
Valid Values and their Meanings:
'*NOMAX' There is no time limit.
'seconds' The number of estimated seconds under which the query is predicted to run. The query will not start if the estimated number of seconds exceeds the number specified.
Display Program Messages Job 151623/DAVE/DSP004 started on 03/10/99 at 08:42:49 in subsystem QINTER Estimated query processing time 9193 exceeds limit 999 (C I) Type reply, press Enter. Reply . . . F3=Exit F12=Cancel
Additional Message Information Message ID . . . . . . : CPA4259 Severity . . . . . . . : 99 Message type . . . . . : Inquiry Date sent . . . . . . : 03/10/99 Time sent . . . . . . : 10:22:22 Message . . . . : Estimated query processing time 9193 exceeds limit 999 (C I) Cause . . . . . : The database query time limit attribute has been specified by the CHGQRYA CL command. The query time limit specified is 999 seconds. A database query was about to be started which was estimated to require a longer time to run than that allowed by the query time limit attribute. The estimated time is 9193 seconds. Recovery . . . : Type a C to cancel processing of this query, or type an I to continue processing the query. Possible choices for replying to message . . . . . . . . . . . . . . . : C -- Cancel the running of the query. I -- Ignore the query time limit and run the query. Technical description . . . . . . . . : The following information explains the type of access plan used by the query. This information is similar to that which can be printed using the PRTSQLINF CL command. DSP004 DAVE 151623 Access plan last saved on 03/10/99 at 10:22:21. Access plan was saved with DB2 Symmetric Multiprocessing installed on the system. Access path created for file 1. Press Enter to continue. F3=Exit F6=Print F9=Display message details F10=Display messages in job log F12=Cancel F21=Select assistance level
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
