Forum

Hi Klaus,

das Manual sagt dazu:

Explanation:
DB2 received an SQL CALL statement for a stored procedure or an SQL statement containing an invocation of a user-defined function. The statement was not accepted because the procedure could not be scheduled before the installation-defined time limit expired. This can happen for any of the following reasons:

The DB2 STOP PROCEDURE(name) or STOP FUNCTION SPECIFIC command was in effect. When this command is in effect, a user-written routine cannot be scheduled until a DB2 START PROCEDURE or START FUNCTION SPECIFIC command is issued.
The user-written routine could not be assigned to a TCB in the DB2-established stored procedures address space in the required time interval, because all available stored procedure TCBs were in use.
The DB2-established stored procedures address space dispatching priority is low, resulting in delays when processing stored procedure requests. If the delays become excessive, the TCBs in the stored procedure address space do not become available to process new SQL CALL statements in a timely manner.
The dispatching priority assigned by WLM to the caller of the user-written routine was low, which resulted in WLM not assigning the request to a TCB in a WLM-established stored procedure address space before the installation-defined time limit expired.
The WLM application environment is quiesced so WLM will not assign the request to a WLM-established stored procedure address space.
WLM is being used in compatibility mode, and the needed stored procedure address space has not been started using the MVS START command.

Da gibt es einige Möglichkeiten, die für das Auftreten des Fehlers beim ersten Aufruf ursächlich sein können. Was ist denn mit den verfügbaren TCBs? Alle belegt beim Erstaufruf?

MfG

AxelP