Re: Limiting max cpu per User

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

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