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



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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.