Fix s322 Timeout Abend in JCL

Mayos · New User Joined: 11 Apr 2005 Posts: 16

Hello,

Any suggestions on how to fix an s322 Abend Code in JCL?

Thanks.

David P · Posted: Tue Apr 12, 2005 5:06 pm

Hi,
Please check the time parameter coded in your Job or step level.

Reason for S322:
The CPU time limit specified in the JCL has been exceeded.
The default CPU time limit set by the system has been exceeded.

Common Scenarios
Long-running programs: Programs that process a large amount of data or have inefficient code.
Infinite loops: Logic errors in the program that cause it to run indefinitely.

How to Resolve S322 Abend

Increase CPU Time Limit:
If the job genuinely requires more CPU time, increase the time limit on the JOB or EXEC statement.
Example:

aishwarya_singh · New User Joined: 06 Apr 2005 Posts: 21

This Abend occurs whenever there is Time spent in running the job is out of the CPU Time whichin which actually the job should have run.

Mayos · New User Joined: 11 Apr 2005 Posts: 16

Does this mean that I have to increase my time parameter?

Thanks again.

radhakrishnan82 · Posted: Tue Apr 12, 2005 5:48 pm

If the time parameter provided in the job or in step is correct then the reason can be due to improper compilation.
Find out in which program the job gave s322 error.
Try to recompile the program and make the job run.

learnmf · Active User Joined: 14 Mar 2005 Posts: 123

S322
The system took a longer time to run a job, job step, or procedure than the time specified in one of the following:
- The TIME parameter of the EXEC or JOB statement
- The standard time limit specified in the job entry subsystem

/references/a29.html

somasundaran_k · Active User Joined: 03 Jun 2003 Posts: 134

Mayos
If it's not the problem with the TIME parameter check whether your program is running in an infinite loop, for example a PERFORM UNTIL condition.

Regds
-Som

andycool · New User Joined: 12 Apr 2005 Posts: 63

Hi,
Jus to ad to the info...Is the TIME parameter mandatory...wht does it signify exactly

uma · New User Joined: 18 Mar 2005 Posts: 8

hi...

I guesst time parameter is not mandatory.But sometimes when the job runs for a longer period then this problem occurs.This can be corrected by coding TIME=1440 in the job card area.

cheers,
Uma

learnmf · Active User Joined: 14 Mar 2005 Posts: 123

[quoteHi,
Jus to ad to the info...Is the TIME parameter mandatory...wht does it signify exactly[/quote]

Hi Friend The time parameter is not mandatory.If you can't give it takes the default.
thanks
Chandra

khamarutheen · Active Member Joined: 23 Aug 2005 Posts: 677 Location: NJ

hi frnd,
S322 error is caused when CPU time assigned to the job, job step or procedure has been exceeded..

so to fix the error u can just go for some looping or u can go for some mismatching time parameter.. to solve go in reverse order.

Kavitha Palani · New User Joined: 16 Nov 2005 Posts: 8

Indicates a time out abend. Your program has taken more CPU time than the default limit for the job class. Could indicate an infinite loop.

kanak · Moderator Joined: 12 Mar 2005 Posts: 252 Location: India

As per my manual:
One of the following occurred:
1. The system took a longer time to run a job, job step, or procedure than the time specified in one of the following:
- The TIME parameter of the EXEC or JOB statement
- The standard time limit specified in the job entry subsystem
2. For a started task under the master subsystem, the TIME parameter was not specified on the PROC statement of the catalogued procedure, and the PPT entry did not indicate a system task.

System Action: The system abnormally ends the job, job step, or procedure.

Programmer Response: If the TIME parameter was not specified on the PROC statement of the catalogued procedure, add the TIME parameter or add a PPT entry for the PGM parameter. Otherwise, check for program errors. If none exist, specify a longer time in the TIME parameter. Then run the job again.

Phantom · New User Joined: 04 Sep 2005 Posts: 25

Pals,

I am consolidating everyone's note here.

1. S322 - Time out Abend - program exceeds the CPU time limit provided to your job. This could be due to various reasons.

Balasubramanian · New User Joined: 23 Apr 2005 Posts: 13 Location: Bangalore

Hi,

Try to change CLASS parameter at JOB card, that might help some time.

Regards,
Balasubramanian S

mandyamj · New User Joined: 22 Nov 2005 Posts: 7

Reason: Caused when CPU time assigned to the job, job step or procedure has been exceeded

JOB OR STEP TIME EXCEEDED THE SPECIFIED LIMIT PROGRAM IS IN A LOOP INSUFFICIENT TIME PARAMETER ON JOB OR EXEC CARD

1.check this job is depend on any previous job if so check that job
2.program may be running in infinite loop
3.give the maxium time limit

tspr52 · Posted: Thu Mar 29, 2007 5:14 pm

expat · Posted: Thu Mar 29, 2007 5:27 pm

I think the point which many people are trying to make here is - What is happening in the program, rather than let's give it infinite resource.

The OP has not bothered to respond to much in this thread.

In my view, giving him/her the code to use infinite resource is a gross error of judgement until the OP has confirmed that the program is working as expected.

I have experienced one user who submitted a looping program on Friday afternoon, who on return to work the next Tuesday found his job was still running and had produced zero results.

dick scherrer · Posted: Thu Mar 29, 2007 10:30 pm

Hello,

Even if it might be gotten away with, 1440 should NOT used.

NO 'application code' should ever specify 1440. Fortunately, many data centers automatically flush application jobs with 1440 in the jcl.

tspr52 · Posted: Fri Mar 30, 2007 12:30 pm

You are right.

This example is just to be used only if you are sure your program is running ok, and only is "exhausted"

For example, if you are running ISRSUPC with a lot of parameters.

My excuses,

Jose Luis

pavanbolla · New User Joined: 25 Mar 2007 Posts: 7 Location: Canada

Hi,

Check whether the COBOL program is in infinite loop, if it is not increase the TIME parameter.

dick scherrer · Posted: Fri Mar 30, 2007 9:51 pm

Hello,

To repeat - SUPERC or your own program or a sort or anything else that is a submitted batch job should not specify 1440.

It does not matter if the job is "running OK". 1440 is a bad option.

If there is a business requirement to use a very large amount of cpu cycles, most sites have some number of initiators/classes that are defined with sufficient time.

If this is a test, needing 1440 is just sloppy or lazy or both. There are ways to cut down the size of the "compare" or other test. Unfortunately, for some, they require a little bit of work and/or planning.

shagnwrx · Posted: Fri Mar 30, 2007 11:43 pm

I'd first check to see how many cpu seconds you are consuming. As the others have said either infinite loop, or you have this job in the wrong jobclass (Sys Progs set CPU time limits per class).

Chances are, there is a list around your shop that shows the time limits for each class.

For right now, do not run unlimited timed initiators, as you've not determined if you have a hard loop yet. Maybe go to a class that is another 30 seconds to a minute longer than the class you are running in now.

sril.krishy · Posted: Fri Mar 30, 2007 11:58 pm

A small note on S322 error:

If the problem is repeating after the increase of the TIME parm,please check the EXCEPTION count,If the count is not increasing ,it means that job is in loop.Try to fix the loop problem,then your problem is solved.
We generally check the Exception count for longer running jobs during the production support to make sure that cycle won't run much time which in turn helps to keep the onlines up at the given time.

Thank you
Krishy.

S0C7 · New User Joined: 19 May 2006 Posts: 26

All,

Just curious on why we are specifying 1440. There is an option call NOLIMIT. Is 1440 same as NOLIMIT..?