>So each step no more than 3 minutes. 3 mins 1 sec it fails on that step.
Think of it as there being a big CPU time bucket for *the job*. There is a limited amount of CPU time in it when TIME= *is* specified on the JOB statement, or an unlimited amount, when TIME= *is not* specified on the JOB statement. Then, there is another CPU time bucket for *the step*. At step initiation each step gets the bucket replenished from the job level bucket. The amount the system *tries* to fill in is the value of the TIME= parameter on the EXEC, if present, or the value from the JOBCLASS (JES2, don't know about JES3) otherwise. If the job bucket does *not* have unlimited amounts, the step can only get the amount assigned if there is enought left in the job bucket. So a step might not get as much as it was assigned. At step end, the system puts back into the job bucket whatever the step has *not* used. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
