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

[Adam.Driver@xxxxxxxxxxxxx]

Jim,

Yes, I think you're right. Besides, as I've said, we don't want to limit
all queries, only the ones that become a problem for interactive CPU. As
for using proper access paths, unfortunately the customer manages the
database themselves, and they do do stupid things like create indexes on
the fly or query huge physical files. We are working with them to hopefully
get these practises changed.

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: Fri, 5 Dec 2003 09:59:13 -0600
from: Jim Damato <jdamato@xxxxxxxxxxxxxxxxx>
subject: RE: Limiting (but not stopping) interactive query by user

Is CHGQRYA really going to address the problem?

The Change Query Attributes (CHGQRYA) command specifies attributes
for database queries and database file keyed access path builds,
rebuilds, and maintenance that are run in a job.  Database queries
include the open of a SQL view and the running of SQL data
manipulation statements.

You're talking about AS/400 Query objects generated by WRKQRY, right?
Isn't
there a potential difference between a query executed by RUNQRY (regardless
of interactive vs. batch) and the database queries and database file keyed
access path builds covered by CHGQRYA?  You could potentially (and should
ideally) be running queries using existing access paths and just performing
normal i/o.  I think this type of query execution is outside the scope of
CHGQRYA.

I think CHGQRYA will only cover certain RUNQRY scenarios.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@xxxxxxxxxxxxxxxxx>