Re: Interactive Queries - again!

Rob,

You are correct. CHGQRYA will affect imbedded SQL etc. So, to make sure that it
only affects interactive queries you write a little CL program that

  CHGQRYA (To whatever the limit for interactive queries is)
  WRKQRY
  CHGQRYA (Back to the System Value or *NOMAX)

Just ensure that this CL program is called from the menu option that users use 
to
Work with Queries.

And how did the system analyst know that the battery in your pager was about to
die?

Paul Tuohy

Rob Berendt wrote:

> Wouldn't the CHGQRYA have the chance of affecting imbedded SQL,
> imbedded Queries, OPNQRYF, etc.  Stuff that you know is 'right'?
> But, if you just wanted to limit interactive Query/400 then you
> should look at the RUNQRY trick?
>
> Talk about 'just knowing'.  We had a long time system analyst
> fill up 50Gb of disk and crash a 400 by running a Query in
> batch and going home.  That was 50Gb of a 100Gb system.
> Happened to be the same day the battery died in my pager.
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---