Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
Quote:
These are the messages its giving in DFSMSG. No chance for a timeout since I used to run job which are much longer than this.
The S322 does indicate the job took longer than allowed. I don't know what you're looking for here. "No chance for a timeout" seems to be an incorrect conclusion. The new job may be running longer than the jobs you used to run for many reasons. Try giving the job more time to run.
If you think DFSORT is looping or working incorrectly, this bulletin board is NOT the place to report that. Instead, you need to open a PMR with IBM service so they can collect the needed doc and investigate the situation.
The job hardly ran for 3 mnts and abended. I used to sun jobs longer than this so i dont think it can be time issue.
Can it be a problem since the number of records is very high and the temp dataset cannot hold that much.
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
Quote:
Can it be a problem since the number of records is very high and the temp dataset cannot hold that much.
If data set space was the issue, you would get some kind of capacity error (Sx37 ABEND), not a S322 ABEND.
Quote:
The job hardly ran for 3 mnts and abended. I used to sun jobs longer than this so i dont think it can be time issue.
The S322 abend means the job exceeded the time ALLOWED for it. For example, if you had TIME=2 on the JOB statement and it ran over 2 minutes, you'd get a S322 ABEND. I don't know what you mean when you say you used to "run jobs longer than this so I don't think it can be a time issue". For all I know, you ran those jobs with TIME=15 and you're running with TIME=2 now, or your site changed the default time to be lower than it used to be.
I think you're chasing the problem from the wrong end. Try using TIME=x where x gives the job sufficient time to run. If you have your old runs, look to see how long they actually took (elapsed time) and set your TIME parameter for that or above. Of course, that's assuming the old jobs are really comparable in filesize, memory, resource usage, etc to the new job and that nothing has changed in your system.
Maybe somebody who knows more about the TIME parameter and relevant defaults relative to the S322 ABEND can say more about this.