Life cycle of a concurrent request

A concurrent request proceeds through three, possibly four, life cycle stages or phases:

Variable	Description
Pending	Request is waiting to be run
Running	Request is running
Completed	Request has finished
Inactive	Request cannot be run

Within each phase, a request's condition or status may change. The following table shows a listing of each phase and the various states that a concurrent request can go through.

Phase	Status	Description
PENDING	Normal	Request is waiting for the next available manager.
PENDING	Standby	Program to run request is incompatible with other program(s) currently running.
PENDING	Scheduled	Request is scheduled to start at a future time or date.
PENDING	Waiting	A child request is waiting for its Parent request to mark it ready to run. For example, a report in a report set that runs sequentially must wait for a prior report to complete.
RUNNING	Normal	Request is running normally.
RUNNING	Paused	Parent request pauses for all its child requests to complete. For example, a report set pauses for all reports in the set to complete.
RUNNING	Resuming	All requests submitted by the same parent request have completed running. The Parent request is waiting to be restarted.
RUNNING	Terminating	Running request is terminated, by selecting Terminate in the Status field of the Request Details zone.
COMPLETED	Normal	Request completes normally.
COMPLETED	Error	Request failed to complete successfully.
COMPLETED	Warning	Request completes with warnings. For example, a report is generated successfully but fails to print.
COMPLETED	Cancelled	Pending or Inactive request is cancelled, by selecting Cancel in the Status field of the Request Details zone.
COMPLETED	Terminated	Running request is terminated, by selecting Terminate in the Status field of the Request Details zone.
INACTIVE	Disabled	Program to run request is not enabled. Contact your system administrator.
INACTIVE	On Hold	Pending request is placed on hold, by selecting Hold in the Status field of the Request Details zone.
INACTIVE	No Manager	No manager is defined to run the request. Check with your system administrator.