-DISPLAY FUNCTION SPECIFIC command (Db2)

DSNX975I csect-name - DISPLAY FUNCTION SPECIFIC REPORT FOLLOWS-

------ SCHEMA = schema
FUNCTION STATUS ACTIVE QUED  MAXQ TIMEOUT FAIL WLM_ENV
function status active qued maxq timeout fail wlm_env
function status active qued maxq timeout fail wlm_env
function status active qued maxq timeout fail wlm_env


------ SCHEMA = schema
csect-name ALL FUNCTIONS STARTED FOR THIS SCHEMA.
FUNCTION STATUS ACTIVE QUED  MAXQ TIMEOUT FAIL WLM_ENV
function status active qued maxq timeout fail wlm_env
function status active qued maxq timeout fail wlm_env
function status active qued maxq timeout fail wlm_env


------ SCHEMA = schema
FUNCTION STATUS ACTIVE QUED  MAXQ TIMEOUT FAIL WLM_ENV
function status active qued maxq timeout fail wlm_env
function status active qued maxq timeout fail wlm_env
function status active qued maxq timeout fail wlm_env
 FUNCTIONS begin - end STOP (act)
...

csect-name ALL OTHER FUNCTIONS IN OTHER SCHEMAS STOPPED act

DISPLAY FUNCTION SPECIFIC REPORT COMPLETE

The output that is displayed varies depending on the qualifying external user-defined functions. Error messages might also be included in the output.

The following information can be provided in the output:

csect-name

The name of the control section that issued the message.

SCHEMA = schema

The schema name for the functions that are included in the output.

The schema name and lines that follow are repeated as many times as needed to satisfy the DISPLAY FUNCTION SPECIFIC request.

FUNCTION function

The name of the external function.

One line of output is included for each requested function.

STATUS status

The status of the function. The status can be any of the following values:

STARTED

The function can accept SQL statement requests.

STOPABN

The function was stopped because of a previous abnormal termination of the function application. SQL statement requests for the function are rejected.

STOPQUE

The function was stopped. SQL statement requests for the function are queued until the function is started or the timeout interval that is defined by the STORTIME subsystem parameter expires.

STOPREJ

The function was placed in this status by the STOP SPECIFIC FUNCTION command with the ACTION(REJECT) option. SQL statement requests for the function are rejected.

If the function is in any of the stopped states, you can use the START SPECIFIC FUNCTION command to start the function.

ACTIVE active

The number of Db2 agents that are currently running this function.

QUED qued

The number of Db2 agents that are currently waiting for this function to be scheduled.

MAXQ maxq

The maximum number of Db2 agents that have waited for this function to be scheduled since the last START SPECIFIC FUNCTION command was issued for this function.

TIMEOUT timeout

The number of times that an SQL statement timed out while waiting for the function to be scheduled since the last START SPECIFIC FUNCTION command was issued for this function.

An SQL statement can time out if the function is stopped by the STOP SPECIFIC FUNCTION command with the ACTION(QUEUE) option. This specification causes requests for the function to time out after the interval that is defined by the STORTIME subsystem parameter is exceeded.

FAIL fail

The number of times that this function has abended since it was last started.

WLM_ENV wlm_env

The MVS Workload Manager environment name for this function.

ALL FUNCTIONS STARTED FOR THIS SCHEMA.

This line is displayed when both of the following conditions are true:

• A STOP FUNCTION SPECIFIC(*.*) command operation was in effect when DISPLAY FUNCTION SPECIFIC was issued.
• All of the functions are started for the schema that is identified in a preceding line in the output.

FUNCTIONS begin - end STOP (act)

This line is displayed when a STOP SPECIFIC FUNCTION command caused a range of functions to be stopped. This situation can occur when the command was issued with an asterisk (*) in the function name.

begin

The first function name in the range of functions that are currently stopped.

end

The last function name in the range of functions that are currently stopped.

act

The action that was specified on the STOP SPECIFIC FUNCTION command.

ALL OTHER FUNCTIONS IN OTHER SCHEMAS STOPPED act

This line is displayed when both of the following conditions are true:

• A STOP FUNCTION SPECIFIC(*.*) command operation was in effect when the DISPLAY FUNCTION SPECIFIC command was issued.
• Any functions that are not already listed in this DISPLAY FUNCTION SPECIFIC output are stopped.

act indicates the action that was specified on the STOP FUNCTION command.

DISPLAY FUNCTION SPECIFIC REPORT COMPLETE

The report completed successfully.

The following messages in the DISPLAY FUNCTION SPECIFIC output indicate that an error occurred:

csect-name FUNCTION HAS NOT BEEN ACCESSED OR IS NOT DEFINED

The routine name that was supplied on the DISPLAY FUNCTION SPECIFIC command either does not exist or has not been accessed since Db2 started. The specific function name might not be in the SYSIBM.SYSROUTINES catalog table.

Processing continues for any additional routine names that were supplied on the command.

DISPLAY TERMINATED WITH MAX LINES

The DISPLAY FUNCTION SPECIFIC report was truncated. The report was generated in response to a command from an MVS console, and more than 254 messages were generated. Only 254 messages are returned.

Command processing completes. The truncated report is written to the MVS console.

Reissue the DISPLAY FUNCTION SPECIFIC command and specify a smaller number of routines. Specify a list of routines, a schema qualifier, or a partial routine name in the DISPLAY command rather than the default (*.*). Alternatively, reissue the command from the DB2 Commands panel of DB2I or from a batch job rather than from the MVS console.

DSNX994I SCOPE(GROUP) COMMAND CANNOT BE PROCESSED DUE TO COMMAND ALREADY IN PROGRESS

See DSNX994I.