At 18:41 -0500 on 04/07/2009, John McKown wrote about Re: $HASP308 message:
On Tue, 7 Apr 2009, Staller, Allan wrote:
Code/install IEFUSI to limit *ALL* test jobs to (e.g.) 5 min of cpu
time. Code/install IEFUTL to calc elapsed time and extend (or not) as
required. IIRC, All of the required info needed should be available to
the exit
Adjust CPU time limit to desired granularity based on your shop. Not too
precise but it should come close to your needs.
HTH,
Problem: I must restict WALL CLOCK or ELAPSED time, not CPU used time.
It's a weird political thing.
IOW: If a user is unlucky enough to submit their job when the machine
is very busy and gets dispatched infrequently (or sits waiting for
devices to be allocated or volumes mounted) then even though it gets
minimal CPU time it gets kicked off due to being in the machine for 2
hours. What is the political reason for wanting Elapsed as opposed to
Run Time? I assume that it must be something to do with Occupying an
Initiator or something like that.
--
Trying to write with a pencils that is dull is pointless.
Maranatha!
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
