Resolving some common problems while debugging Db2 stored procedures

This topic describes the messages you might receive and resolution to the problem described by those messages. This topic covers common problems.

Table 1. Common problems while debugging stored procedures and resolutions to those problems
Error code	Error message	Resolution
`SQLCODE = 471, SQLERRMC = 00E79001`	Stored procedure was stopped.	Start the stored procedure using Db2® Start Procedure command.
`SQLCODE = 471, SQLERRMC = 00E79002`	Stored procedure could not be started because of a scheduling problem.	Try using the Db2 Start Procedure command. If this does not work, contact the Db2 Administrator to raise the dispatching priority of the procedure.
`SQLCODE = 471, SQLERRMC = 00E7900C`	WLM application environment name is not defined or available.	Activate the WLM address space using the MVS `WLM VARY` command, for example: `WLM VARY APPLENV=applenv,RESUME` where applenv is the name of the WLM address space.
`SQLCODE = 444, SQLERRMC (none)`	Program not found.	Verify that the `LOADLIB` is in the `STEPLIB` for the WLM or Db2 address space JCL and has the appropriate RACF® Read authorization for other applications to access it.
`SQLCODE = 430, SQLERRMC (none)`	Abnormal termination in stored procedure	This can occur for many reasons. If the stored procedure abends without calling z/OS® Debugger, analyze the Procedure for any logic errors. If the Procedure runs successfully without z/OS Debugger, there may a problem with how the stored procedure was compiled and linked. Be sure that the Procedure data set has the proper RACF authorizations. There may be a problem with the address space. Verify that the WLM or Db2 Address Space is correct. If there are any modifications, be sure the region is recycled.