S322 Error even after specifying the maximum time

murugan_mf

HI ALL,
I am getting the abend S322 feven though i have mentioned the maximum allowable time in the job card.
Can any one suggest me what could be the root causes for this abend?
so that I can sort it out.

expat · Posted: Tue Jul 22, 2008 4:56 pm Post subject:

Talk with your systems people, S322 is a CPU time exceeded abend, based on your job class.

Even though you code a different time parameter on your jobcard, the system may well be configured to ignore that override and only use job class parameters for allocating CPU time.

gcicchet · Senior Member Joined: 28 Jul 2006 Posts: 648

Hi,
you may not be allowed to put the maximum amount of time on your jobcard. The time may be site specific based on the job class.

Check with your SYSPROG.

Gerry

Prasanthhere · Active User Joined: 03 Aug 2005 Posts: 277

Try using some other CLASS parameter . Most of the shop have been set like IF it coded in say CLASS A the pgm will run for 15 minutes in another class for say 30 minutes so on...

Even though u give time=1440 the default setting will overide what u specify in the JOB.

Check with your sysadmin

karthikr44

Hi,

It may also occur if indefinite loop occurs in ur program.

Regards
R KARTHIK

gcicchet · Senior Member Joined: 28 Jul 2006 Posts: 648

Hi,

if time of 1440 or NOLIMIT is allowable it exempts the job from all CPU and wait time limit checking - the job can execute as long as it needs to. No S322 abend will occur for the job, so a loop will not abend the job.

Gerry

Prasanthhere · Active User Joined: 03 Aug 2005 Posts: 277

Hi gcicchet,

Craq Giegerich · Posted: Tue Jul 22, 2008 5:29 pm Post subject:

I would look at the programs involved and try to understand why they are taking so long instead of just blindly giving them more time!

Anuj D. · Posted: Tue Jul 22, 2008 5:33 pm Post subject:

Hi,

I second to Gerry...

Again, please search the forum, there had been quite a lots of discussion on smilar topics, here is one describing The CLASS in JCL and JCL execution time.

further, this

Terry Heinze · Posted: Tue Jul 22, 2008 8:54 pm Post subject:

Many shops will slap your hand (or worse) for attempting to use TIME=1440/NOLIMIT, and rightfully so!

dick scherrer · Posted: Tue Jul 22, 2008 9:39 pm Post subject:

Hello,

Better managed systems will not allow developers to submit a job with time=1440. They are automatically flushed as a jcl error.

There is never an acceptable reason for a developer to use time=1440. . . Even if the system is so poorly administered as to allow it.

Terry Heinze · Posted: Tue Jul 22, 2008 10:04 pm Post subject:

The only legitimate use of TIME=1440 I've ever run across was for a production CICS region.

dick scherrer

Hi Terry,

Yup,

Or other system tasks - i.e. database, tape management, scheduler, etc. . .

d

dbzTHEdinosauer · Posted: Tue Jul 22, 2008 10:40 pm Post subject:

permenant batch jobs, submitted as a started task.