Chat now with support
Chat with Support

Spotlight on DB2 6.10 - Getting Started Guide

State

The current state of the activity:

State

Description

CANCEL_PENDING

The WLM_CANCEL_ACTIVITY has canceled the activity because no agent was working on a request for the activity. The activity is actually canceled the next time a user issues a request as part of the activity.

EXECUTING

Agents are currently working on a request for the activity.

IDLE

No agent is currently processing a request for the activity.

INITIALIZING

A user has issued a request for the activity, but the activity has not started execution. At this point, predictive thresholds determine whether execution should proceed.

QP_CANCEL_PENDING

The query patroller has canceled the activity because no agent was working on a request for the activity. The activity is actually cancel the next time a user issues a request as part of the activity.

QP_QUEUED

The query patroller has placed the activity in a queue to await execution.

QUEUED

The Workload Manager has placed the activity in a threshold queue to await execution; or, in a PDF (database partitioning feature) environment, the activity is in the process of obtaining threshold tickets via a remote procedure call from the coordinator agent.

TERMINATING

Activity execution has just completed. DB2 is in the process of removing the activity.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating