In answer to your first question :

You can use the ";TIME=cpusecs" parameter in the JOB command, if you know how many CPU seconds the job usually needs

or, if you're really adventurous read on,

create a command file or job or program to do the following:

-Capture the output of SHOWJOB JOB=@J;EXEC to a dummy file,
-Read the file and issue a SHOWPROC command for each executing job and capture that output to another dummy file
-Read the second file and check the CPUTIME as reported by the SHOWPROC command and ABORTJOB if need be.
-Place all the above in a loop PAUSEing for 3600 seconds

sound a bit like an exotic recipe but it will work. I've got a little TRANSACT/iX program that does something similar to ABORT idle sessions.

Now once you start capturing command outputs, there's not much you can't (eventually :)  ) do. You could capture the SHOWJOB JOB=@J;EXEC and compare the system time to the INTRODUCED time and decide if a job has had enough.


Costas Anastassiades
Information Systems and Internal Communications Department
INTRACOM SA,
Athens - Greece