Re: Inquiry : Queries and number of ODPs in programs

In my personal opinion;

I think your programmers have found a crutch in using Query.  You must
take that crutch away by the sounds of it.  I use it a LOT and it does
take 5 or more queries to do a single report if it's complicated
enough.  I don't have the luxury to take the time of doing it right but
at least I know what the right way is.  Nothing in production should be
query and absolutely NO interactive query for any reasons.  Make them
write the CL, RPG, SQL, whatever it takes.

Glenn Gundermann

Spirinckx Chris wrote:
> 
> Fellow-midrangers,
> 
> A colleague and I are responsible for 2 AS/400 ( 620/600 ).
> One of our tasks is of course the tuning of those systems.
> 
> Currently we're having 2 "hot" discussions with the programmers :
> 
> 1) Usage of RUNQRY-command.
> ---------------------------
> We think that this command should mainly be used by the DP-staff itself
> (testing purposes ) or for ad-hoc reports.
> The programmers on the otherhand are using this command in practicly 50 %
> of the applications
> (including interactive ones ).
> Some of the batchjobs are 5 or more RUNQRY-commands that run after each
> other in order to produce one single query-report.
> They say : "its easy to use and with minimum on effort".
> The course about SQL has just finished, we're shaking already.
<snip>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---