Re: Job hangs after processing 220 records.

On 02/07/2014 14:33, Marie O'Rourke wrote:

Ok, Let's see if I can answer all the questions asked in one go.

I don't think record lock is the problem, this job hangs consistently when it has more than 220 records, so it is not the data on any single record.
And the data it has to process changes every time the job completes, the job will complete when run manually.

Calling IBM support will be the last option, once I have investigated it to my full potential, I will pass to the ISeries team to investigate and then it might go to IBM...

When I say hang, it does no more processing, the job has been left for 2-3 days... admittedly not on purpose, it happens almost every weekend.
The job still has an ACTIVE status, the IO count is not changing and the call stack is not changing.

The only differences between the User profile JOBD and the JOBD used for submitting is the Job Queue and the Library list.
The library list is correct and both Job Queues are in the same subsystem.
The SQL statements use unqualified references, so the same code can work in our four test environments and our live system.

All three errors occur in both the /hangs/ request and the successful requests? Or just the MCH3603 errors happen in both?