× 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.



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>



-----Original Message-----
From: Mark S. Waterbury [mailto:mark.s.waterbury@xxxxxxx]
Sent: Thursday, December 04, 2003 7:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Limiting (but not stopping) interactive query by user


Hello, all:

It might be done even simpler than that... if you have an initial program
(specified in the *USRPRF) when those users sign on, perhaps you
could issue the CHGQRYA there?

To quote Albert Einstein: "Make it as simple as possible, but not simpler."

Regards,

Mark S. Waterbury


----- Original Message -----
From: <Adam.Driver@xxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, December 04, 2003 6:36 PM
Subject: Re: Limiting (but not stopping) interactive query by user


> Hi Simon,
>
> 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.
>
> I'm also downloading the trial version of CHGQRYOPT, so I'll let you know
> what I think.
>
>
> 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
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.