Infinite loop Error S322

grem · Posted: Mon Aug 17, 2009 4:34 pm

Hi,

Im running job G586476 on our test environment unfortunately i encountered S322 Which is it exceed the CPU Time limit for this job, so i tried to indicate a time parameter on its jcl but unfortunately this job runs for almost 4 hours it did not end its having an infinite loop.

Can somebody know what the best thing to do?

Thanks

dejunzhu · Active User Joined: 08 May 2008 Posts: 390 Location: China

use command "P" to cancel the job that is running.

Then check the job logic twice.

grem · Posted: Mon Aug 17, 2009 4:56 pm

ive checked the job and its only producing a report by reading the records on several tables.

does this have a connection on a Database connection problem?

Pankaj Shrivastava · New User Joined: 24 Jul 2009 Posts: 51 Location: Pune

dejunzhu · Active User Joined: 08 May 2008 Posts: 390 Location: China

Not clearly, but if you can put your jcl and log here, it will be more helpful.

grem · Posted: Mon Aug 17, 2009 8:08 pm

here's my sample jcl:

Terry Heinze · Posted: Mon Aug 17, 2009 8:41 pm

If you have a monitoring tool like Xpediter or Strobe, use it to determine where your loop is. If no monitoring tool, place DISPLAY statements at strategic locations to help determine the loop. If it's a simple and small program, you might be able to determine the problem simply by thoroughly examining the logic. Suwertihín ka nawâ!

mike duff · New User Joined: 05 Mar 2009 Posts: 4 Location: halifax

Terry Heinze · Posted: Sat Nov 28, 2009 5:46 am

mike duff · New User Joined: 05 Mar 2009 Posts: 4 Location: halifax

Terry Heinze · Posted: Sat Nov 28, 2009 9:14 pm

I don't have access to a mainframe, but as far as I recall, you cannot attach Expediter to an executing program.

Robert Sample · Posted: Sat Nov 28, 2009 9:29 pm

Xpediter makes JCL changes when preparing the batch job for submission; since production jobs are generally scheduled using fixed JCL, it would be difficult to use it on a production job.