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


  • Subject: Re: Inquiry : Queries and number of ODPs in programs
  • From: ywexler@xxxxxxx
  • Date: Mon, 13 Apr 1998 09:43:25 +0300

Glenn Gundermann wrote:
> 
> 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
> +---
My personal opinion is quite opposite.
We run a large AS/400 and until our Data Warehouse will work we use
Query/400 within DP department (e.g. the programmers) and by
"sofisticated" users (e.g. non programmers).
We use a 530 model (#2153, 4CPU) serving about 1200 WS most of them in
remote sites.
Giving the authorization to non-programmer users to use Query/400 has a
very good impact on the oveall satisfaction of the users and the mutual
relationship between them and our department.
To implement the Query we followed several steps:
1. Training:
   From time to time we train the users. The cours has three parts - 
   a. Introduction to AS/400 (and computers in general).
   b. Query/400.
   c. Workshop on Query/400 including the specifications of specific
      DB/Applications according to the groups of interst of the users.
   d. We prepared demo-queries.
   e. We prepared some non-normalized files which duplicates the files
      in the normalized DB for easier usage of Q/400. 
   f. We prepared a new RUNQRY command to run only in Batch and the 
      users are authorised only to this command.
   g. We limitted the Max. Storage of the users to prevent heavy disk 
      usage.

Yossi Wechsler
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.