Page 1 of 1

ABEND=S322

PostPosted: Thu Jan 14, 2016 3:10 pm
by vegafacundodaniel
Hello.
Could anyone help please?
I get an ABEND=S322 (timeout abend) executing a big program that reads, updates, inserts and deletes on several DB2 tables.

Does anyone knows a way to find what is problem ? I guess, there is a deadlock somewhere. How to find it ? Could Detector of Platinum helps me? how?

Thanks in advance

Re: ABEND=S322

PostPosted: Thu Jan 14, 2016 3:27 pm
by enrico-sorichetti
what does the manual say about it ?

Re: ABEND=S322

PostPosted: Thu Jan 14, 2016 4:59 pm
by NicC
Nothing to do with DB2 in itself, you have simplty spent all the time permitted by the system for your task. Presumably this is in a test region as production should not have time constraints, You could give yourelf more time using the TIME parameter on the job cards but check around first as this may not be allowed. If it isn't then you will have to split the job into smaller tasks.

Re: ABEND=S322

PostPosted: Thu Jan 14, 2016 6:26 pm
by Robert Sample
I guess, there is a deadlock somewhere.
You are guessing wrong. It is entirely possible that the program is running normally but just ran out of time. You need to talk to someone AT YOUR SITE -- coworkers, team leader, manager, or site support group -- to find out how to resolve this issue. Many sites put time restrictions on certain job classes, and if your job is running in a job class that has such a restriction, you will NOT be able to run the program to normal completion without changing the job class. And only someone working at your site can tell you the rules for your site.