Doubt on TIME parameter

krbabu · New User Joined: 20 Feb 2004 Posts: 57

Hi,
I have a doubt on TIME parameter.
I was coded the jcl like the following way.

//timejob JOB ' ',..............,Time=40
//s1 EXEC PGM=p1,Time=20
//s2 EXEC PGM=p2,Timw=30
//

Can anybody tell about the execution of the above JOB.

sandip_datta · Posted: Fri Feb 20, 2004 1:01 pm

Hi Ravindra,

It means that the job will take maximum of 40 secs/mins depending on unit. If it reaches maximum time limit then it will abend with the error message "Max Time reached".

Regards,
Sandip.

krbabu · New User Joined: 20 Feb 2004 Posts: 57

that'z correct but i want know about which step is abend? Is the total job will abend are else only the second step will abend?

sandip_datta · Posted: Fri Feb 20, 2004 2:59 pm

My guess is that the currently executing setp will abend. the output from previous step will remain unaffected(for simple situation of course).

Regards,
Sandip.

mdtendulkar · Active User Joined: 29 Jul 2003 Posts: 237 Location: USA

Hello krbabu,

In the example the job is allowed 40 minutes of execution time. each step is allowed 20 minutes of execution time (even though the second step is allowed to execute for 30 mins)

Should either step try to execute beyond 20 minutes, the job will terminate beginning with that step. If STEP1 executes in 19.75 minutes and if STEP2 tries to execute beyond 20.25 minutes, the job will be terminated because of the 40-minute time limit specified on the JOB statement.

Hope this helps,

Regards
Mayuresh Tendulkar

anuradha · Posted: Fri Feb 20, 2004 9:51 pm

I had some doubt in this.If first step executes for say some 5 min and if second step need execution for some 32 min,will second step execute though the time parameter is coded as 30 min for that step???

According to me as job step time parm overrides step's time parm it shld execute right.

Thanks and regards
anu

mcmillan · Site Admin Joined: 18 May 2003 Posts: 1210 Location: India

Dear,

krbabu · New User Joined: 20 Feb 2004 Posts: 57

Thanks to one and all

rameshvaamshy · New User Joined: 19 Aug 2007 Posts: 14 Location: bangalore

check out whether this helps

For a JOB statement TIME parameter of TIME=NOLIMIT or TIME=1440, the system nullifies any TIME parameters on EXEC statements as well as the default TIME values. All steps within the job will have unlimited processor time.

For a JOB statement TIME parameter other than TIME=NOLIMIT or TIME=1440, the system sets the time limit for each step to one of the following:

The step time limit specified on the EXEC statement TIME parameter or the job time remaining after execution of previous job steps, whichever is smaller.

If no EXEC TIME parameter was specified: the default time limit, or the job time remaining after execution of previous steps, whichever is smaller.
Example 1

//FIRST JOB ,SMITH,TIME=2
//STEP1 EXEC PGM=READER,TIME=1
.
.
.
//STEP2 EXEC PGM=WRITER,TIME=1
.

In this example, the job is allowed 2 minutes for execution and each step is allowed 1 minute. If either step continues executing beyond 1 minute, the entire job abnormally terminates beginning with that step.
Example 2

//SECOND JOB ,JONES,TIME=3
//STEP1 EXEC PGM=ADDER,TIME=2
.
.
.
//STEP2 EXEC PGM=PRINT,TIME=2
.

In this example, the job is allowed 3 minutes for execution, and each step is allowed 2 minutes. If either step continues executing beyond 2 minutes, the entire job abnormally terminates beginning with that step. If STEP1 executes for 1.74 minutes and STEP2 tries to execute beyond 1.26 minutes, the job abnormally terminates because of the 3-minute limit specified on the JOB statement.

murmohk1 · Posted: Thu Oct 11, 2007 4:32 pm

ramesh,

You reply is bit late (by 3 years). The OP is of 2004 one. Im not sure Ravi still needs this or not.