RE: Limiting max cpu per User

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Linda

If you run a job interactively that does SQL and it's estimate exceeds this 
value, you get an inquiry message yourself. If it's an ODBC connection and 
the estimate is greater than this value, it just aborts without doing 
anything. I think the ODBC setting is QueryTimeOut.

What is the client? ODBC would normally be a QZDASOINIT job, not this 
RWTSRVR job - that's another access method.

Cheers

Vern

At 12:26 PM 7/22/2003 -0400, you wrote:
> So does it just  sit there waiting on a reply from the operator before it
> dies?
> Our opts barly looks at the  system now, I would hate to think what would
> happen if we did this and then nothing moved because she does not watch the
> system.
> Thanks Linda
>
> -----Original Message-----
> From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Tuesday, July 22, 2003 12:11 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Limiting max cpu per User
>
>
> This looks like some kind of SQL query - is that right? There is a
> QRYTIMLMT that can be set that will cause a query not to run if it is
> estimated that it will take longer than that limit. It doesn't run until
> that limit, it actually prompts whether to continue, based on the
> optimizer's estimated runtime.
>
> HTH
>
> Vern
>
> At 10:03 AM 7/22/2003 -0400, you wrote:
>
> >
> >
> > > Is it possible to set MAXCPU for a user Id  to quit after 100
> > > seconds of CPU time?  Please let me know.
> > >
> >  ****************************************************************
> >                                                              Syst
> >  Job:   QRWTSRVR       User:   QUSER          Number:   310831
> >
> >  Status of job . . . . . . . . . . . . . . . :   ACTIVE
> >  Current user profile  . . . . . . . . . . . :   WEBBINI
> >  Job user identity . . . . . . . . . . . . . :   WEBBINI
> >********************************************************
> >                                                        System:
> >  Job:   QRWTSRVR       User:   QUSER          Number:   310831
> >
> >  Run priority  . . . . . . . . . . . . . . . . . . :   20
> >  Time slice in milliseconds  . . . . . . . . . . . :   2000
> >  Eligible for purge  . . . . . . . . . . . . . . . :   *YES
> >  Default wait time in seconds  . . . . . . . . . . :   30
> >  Maximum CPU time in milliseconds  . . . . . . . . :   *NOMAX
> (where
> >can we change this at??)
> >    CPU time used . . . . . . . . . . . . . . . . . :     53597
> >  Maximum temporary storage in megabytes  . . . . . :   *NOMAX
> >    Temporary storage used  . . . . . . . . . . . . :     8
> >  Maximum threads . . . . . . . . . . . . . . . . . :   *NOMAX
> >    Threads . . . . . . . . . . . . . . . . . . . . :     1
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
> or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.