Friday, October 10, 2008

Concurrent Request Phase and Status

The Concurrent Requests window displays a phase and status summary for each concurrent request listed
A concurrent request has a life cycle consisting of the following phases: pending, running, completed, and inactive.
During each phase, a concurrent request has a specific condition or status.
lists each phase/status combination and describes its meaning in relation to a request.
If a request is pending, you can determine when it will start by using the Concurrent Managers For the Request window from the Requests window to review the request's position in the queues of current managers that can run that request.

Phase StatusDescription
PENDING Normal Request is waiting for the next available manager
Standby Program to run request is incompatible with other program(s) currently running
Scheduled Request is scheduled to start at a future time or date.
Waiting A child request is waiting for its Parent request to mark it ready to run. For example, a request in a request set that runs sequentially must wait for a prior request to complete
RUNNING Normal Request is running normally
Paused Parent request pauses for all its child requests to finish running. For example, a request set pauses for all requests in the set to complete.
Resuming All requests submitted by the same parent request have completed running. The Parent request resumes running.
Terminating Request is terminated by choosing the Cancel Request button in Requests window
COMPLETED Normal Request completed successfully.
ErrorRequest failed to complete successfully
Warning Request completed with warnings. For example, a request is generated successfully but fails to print
Cancelled Pending or Inactive request is cancelled by choosing the Cancel Request button in the Requests window.
Terminated Request is terminated by choosing the Cancel Request button in the Requests window.
InactiveDisabled Program to run request is not enabled. Contact your system administrator.
On Hold Pending request is placed on hold by choosing the Hold Request button in the Requests window.
No Manager No manager is defined to run the request. Check with your system administrator. A status of No Manager is also given when all managers are locked by run-alone requests.

No comments: