Phase and Status for a Concurrent Request

Phase and Status for a Concurrent Request

The Concurrent Requests Summary window displays a phase and status summary for each concurrent request listed in the window.

A concurrent request has a life cycle consisting of the following phases:

•Pending: The request is waiting to be run.

•Running: The request is running.

•Completed: The request has finished execution.

•Inactive: The request cannot yet be run.

During each phase, a concurrent request has a specific condition or status. The table lists each phase/status combination and describes its meaning in relation to a request.

Pending Phase

A program in the Pending phase can be in one of four statuses:

•Normal: The program is waiting for an available manager.

•Waiting: A child program is waiting for a parent to mark it ready to run.

•Standby: A program is waiting for another incompatible program in the same logical database to complete.

•Scheduled: A program’s scheduled start time has not yet elapsed.

Running Phase

A program in the Running phase can be in one of four statuses:

•Normal: Program is in progress.

•Paused: A parent program is waiting for one or more child programs to complete.

•Resuming: A parent program is continuing after the completion of one or more child programs.

•Terminating: The program is being terminated.

Completed Phase

A program in the Completed phase can be in one of five statuses:

•Normal: Program completed successfully.

•Warning: Program completed successfully but with warning messages.

•Error: Program failed to complete successfully.

•Terminated: A running program was terminated.

•Canceled: A pending or inactive program was canceled before it started.

Inactive Phase

A program in the Inactive phase can be in one of three statuses:

•Disabled: The requested program has not been enabled for execution.

•On Hold: The requested program has been placed on hold.

•No Manager: There is no manager defined to run this type of request.