00E79002

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 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.

System action

The statement cannot be executed.

Programmer response

If the routine was stopped, use the Db2 -START PROCEDURE or -START FUNCTION command to activate the user-written routine.

The cause of the timeout condition might be one of the following situations:
  • If goal mode is being used to manage the number of WLM-established stored procedure address spaces, the dispatching priority assigned to the caller of the stored procedure might be too low. If the work is of low priority, WLM might leave it queued for a longer period of time.
  • The WLM application environment is quiesced. Issue MVS DISPLAY WLM,APPLENV=wlmenv command to verify the status of the application environment. The MVS VARY WLM,APPLENV=wlmenv command can be used to activate the environment if it is quiesced.