Our mainframe stored procedure is accessed by a java application (web screen).
When there are more number of records ( more than 8000 records) to retrieve from DB2, the system takes more time and in the process we get timed out and then System Exception error occurs. We are not able to find out the exact threshold value as we see that sometimes it works for more than 8000 records also and sometime it fails for around 7000 records also.
The main problem here is when we perform a search which will fetch more records, system exception occurs and at the back end the Stored Procedure stops working. Once the SP stops, we are not able to perform even a simple search as we will get only system exception error till the time the SP is restarted.
Can anyone guide me why the SP is behaving this manner?
Is there anything that needs to be done in the SP definition or DB2 environment setup to avoid SP getting stopped.
Joined: 06 Jul 2010 Posts: 658 Location: Whitby, ON, Canada
Check with your DBA or other site support personnel. Stored Procedures are often set up with a parameter that sets a limit on the number of times it abends before the procedure is stopped. You can ask them to change that limit (they will probably say no) but that will not address the cause of the "system error".