S322 despite TIME being maximum

ravichella · New User Joined: 19 Jan 2006 Posts: 1

Hi All,

How is that we could get a S3222 despite time being maximum?

Rupesh.Kothari · Member of the Month Joined: 27 Apr 2005 Posts: 463

HI,

senthils · Posted: Thu Jan 19, 2006 12:33 pm

I think he means S322. It can happen if the the job class is wrongly given.
For example assume for CLASS A the shop has set a time limit of 10 Sec. If your job runs for more than 10 Sec then you will get S322. This can happen even though you have specified more amount of time in TIME parameter.

Rupesh.Kothari · Member of the Month Joined: 27 Apr 2005 Posts: 463

HI,

If It is S322
Then reason for this will be

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 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

To overcome this increase the Time parameter or use NOLIMIT.

Hope this helps

Regards
Rupesh

saithvis2 · Posted: Thu Jan 19, 2006 2:52 pm

Hi,

If in case there is still problem persisting with nolimit with the specified Class then better use a different class , like in our shop if class X gives a S322 abend along with time=1440 paramter we shift our class to L and though the job takes longer time to finish , it passes of successfully , so better change the class if no limit doesnt work.

Correct me if i am wrong .

Regards
Vishal

priyesh.agrawal · Posted: Thu Jan 19, 2006 5:06 pm

It is always suggestable to look out the step involved in abend for S322, if maximum time is also not working.

Check for a never ending loop or the step program to get the reason behind the long execution time.

Regards,

Priyesh.