On Tuesday, March 09, 1999 08:29, Mike Kapsak [mailto:[log in to unmask]] asks,

>  Is there a calculation to determine <cpusecs> if  I want a job to run
> no more than 120 seconds? I tried using ;TIME=120 in my
> jobcard but the
> job logs off immediately after being streamed. Any help is
> appreciated.

According to docs for both 5.5 and 6.0 (I wanted to doublecheck) - a value
of 120 should have given you 120 CPU Seconds before the job logged off.

A logon takes about 2, which leaves about 118 to use up.

If it logged off immediately, what was the reason printed in the $STDLIST?
Was the logoff caused due to running out of CPU time?  Does the group have
enough Connect or CPU time?  File space? (:REPORT will tell you this).

If out of CPU time (and not the group, but the job itself, exhausted all of
its CPU time), then raise it, or delete the parameter altogether from the
!JOB record in the jobstream - and you'll get all you need, up to any
possible Group or Account limitations.

Regards,
Joe Geiser

====================================================
Joe Geiser, President and Senior Partner
CSI Business Solutions, LLC
Phone: +1(215) 945.8100   Fax: +1(215) 943.8408
Toll Free (US/Canada): (877) 945.8100
====================================================