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
ABEND=S322
-
- Posts: 61
- Joined: Tue Jul 20, 2010 4:27 pm
- Skillset: Everythings on Mainframe
- Referer: Search on internet
-
- Global moderator
- Posts: 3006
- Joined: Fri Apr 18, 2008 11:25 pm
- Skillset: tso,rexx,assembler,pl/i,storage,mvs,os/390,z/os,
- Referer: www.ibmmainframes.com
Re: ABEND=S322
what does the manual say about it ?
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
-
- Global moderator
- Posts: 3025
- Joined: Sun Jul 04, 2010 12:13 am
- Skillset: JCL, PL/1, Rexx, Utilities and to a lesser extent (i.e. I have programmed using them) COBOL,DB2,IMS
- Referer: Google
- Location: Pushing up the daisies (almost)
Re: ABEND=S322
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.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
Regards
Nic
-
- Global moderator
- Posts: 3720
- Joined: Sat Dec 19, 2009 8:32 pm
- Skillset: Systems programming, SAS, COBOL, CICS, JCL, SMS, VSAM, etc.
- Referer: other forum
- Location: Dubuque, Iowa, USA
Re: ABEND=S322
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.I guess, there is a deadlock somewhere.
-
- Similar Topics
- Replies
- Views
- Last post
-
- 0
- 2117
-
by MainframeCoder
View the latest post
Thu Oct 14, 2021 6:13 am
-
- 0
- 1788
-
by bwissink
View the latest post
Thu Sep 02, 2021 10:04 pm
-
- 3
- 1782
-
by Blackthorn
View the latest post
Fri Mar 05, 2021 9:34 pm