Re: Limiting (but not stopping) interactive query by user

Thanks Simon, that's what I thought. I don't want to use the system value,
but limiting QQRYTIMLMT for interactive sessions may do what we want (well,
close, anyway). I've downloaded the copy of CHGQRYOPT and I'm hoping to
have a look this week. I'll let you know how I go.

Thanks

Adam Driver
Technical Consultant
Kaz Technology Services
Level 7
66 Wentworth Ave
Sydney NSW 2010
Australia
Phone: +61 2 9844 0386
Fax: +61 2 9844 0333

A division of Kaz Group Limited - visit our website at www.kaz.com.au




date: Sat, 6 Dec 2003 08:42:38 +1100
from: Simon Coulter <shc@xxxxxxxxxxxxxxxxx>
subject: Re: Limiting (but not stopping) interactive query by user


On Friday, December 5, 2003, at 12:36  PM, Adam.Driver@xxxxxxxxxxxxx
wrote:

> You might be onto something! I assume the only reason CHGQRYA doesn't
> affect batch is because batch submitted queries would have a different
> job
> name etc,? This could be good for us, because we don't want to use the
> system value if it limits batch.

OK, here's how it works:

QQRYTIMLMT controls the maximum query time for all jobs on the system.
The shipped value is *NOMAX which allows all queries to run. The
initial attribute for all jobs is to use the QQRYTIMLMT value. If you
change this system value the Query Engine estimates the amount of time
taken to run a query and sends the CPA4259 enquiry message to the user
informing them that the query will likely exceed the time limit. This
message allows the user to run the query anyway by answering I to
ignore. Obviously that will defeat your efforts so you must get the
system to answer the message automatically. See below for ways to do
that.

Because QQRYTIMLMT affects all jobs the enquiry message will be sent to
the batch job and redirected to the system operators message queue.
This will probably irritate them so again the message must be answered
automatically or better not sent for batch jobs.

Some of the drawbacks associated with the QQRYTIMLMT system value can
be mitigated by the CHGQRYA command. The main advantage is that it
affects only the job in which it is run so batch jobs submitted from a
job in which CHGQRYA has been run will not be affected, however it
still suffers from the problem of allowing the user to ignore the time
limit by answering I to the CPA4259 message.

CHGQRYOPT is an interface to the QAQQINI file and provides the same
control as CHGQRYA plus some additional control values. If you use
CHGQRYOPT to create or modify a QAQQINI file in QUSRSYS this will
affect all jobs because the default query atribute is to use a QAQQINI
file in QUSRSYS if one exists. If you create QAQQINI files in different
libraries then you must also use CHGQRYA to activate the new QAQQINI
file. Since the Query Engine is responsible for checking the time limit
and sends the message you must still automatically answer the enquiry
message.