Identify the correct concurrent request phase and status for a request being evaluated by the Conflict Resolution Manager.

Identify the correct concurrent request phase and status for a request being evaluated by the
Conflict Resolution Manager.

A.
Pending–Normal

B.
Running–Normal

C.
Running–Paused

D.
Pending–Standby

E.
Pending –Scheduled

Explanation:
The daily scheduled request set did not run and status for which remained at
“Pending Scheduled”. Concurrent Manager did not pick up this and status remained:
“
This request is waiting to be processed by the Conflict Resolution Manager.
This request cannot yet begin execution because other requests may conflict with it. The Conflict
Resolution Manager will determine when this request may begin execution.
User <user_ name> submitted this request on 06-MAR-2011 23:17:33.
No action required. This is a normal condition.
This request may have to wait on one or more of the following requests to complete before it can

begin execution:
“
Note:
The Conflict Resolution Manager (CRM) functions to check concurrent program definitions for
incompatibility rules.
Concurrent managers read request to start concurrent programs running. The Conflict Resolution
Manager checks concurrent program definitions for incompatibility rules. If a program is identified
as Run Alone, then the Conflict Resolution Manager prevents the concurrent managers from
starting other programs in the same conflict domain. When a program lists other programs as
being incompatible with it, the Conflict Resolution Manager prevents the program from starting
until any incompatible programs in the same domain have completed running.If the Conflict
Resolution Manager fails, the Internal Manager will restart the Conflict Resolution Manager, or will
process incompatibilities if the profile option Concurrent: Use ICM is set to Yes.