You are getting a -805 I assume.

In this case it means that no more large cursors are available for the
package. The default is 3 large cursors (SYSLN300, SYSLN301, and SYSLN302)
but since it cannot find (-805) cursor 31 (1E is 30 and the first package is
SYSLN300) then that means some has already rebound that package with the
maximum number of large cursors that can be defined (30).

If this is a production server, the cause of this is sloppy programming. Too
many cursors are open at one time. Since most programmers rely on java or
some java tool to create their SQL, that means they are not closing their
transactions and/or not committing frequently enough. The DB2 Application
Development Guide has examples of how to close a transaction in java.

Send it back to the programmers and tell them they need to learn how to
write programs properly.

If this is happening on a development server where you are using RAD, etc in
debug mode (which may not close transactions in debug mode) ask the
programmers to reboot their workstations at least daily and to shut down RAD
when they are not using it.

I had a smiliar situation.  This means the app is not closing the
dynamic sql cursors properly. Its either left at a hanging state and
not released or not closed proplerly. Its an application problem.
DB2PD can help you identify how many cursors are open at the time of
error.  If its a prod app and its erroring out with -805 increase the
CLIPKG to a higher number. This is a band aid to the problem to get
you out of the problem. You can also db2 a DB2JDBCBIND to increase the
number of cursor handles too.
Basically the above two temporarily solutions are to get you out of
the problem for time being, but the application dev. needs to fix the
code.

HTH

Roger