Performing User Tasks › How Moving an Element Between Inventory Locations Works › How Move Requests Are Processed

How Move Requests Are Processed

When you move an element from one inventory location (environment, stage) to the next location on a map route, CA Endevor SCM performs as many of the following processes as necessary.

• Source management, which involves the actual move of the element and the Master Control File (MCF) updates.
• Processor management, which involves executing (at the target location) either the Move processor of the source processor group or the Generate processor at the target processor group. This is determined by the processor group setting at the source location. Move processing includes invocation of appropriate Natural or Predict utilities to move objects between the FUSER/Library locations or FDIC locations associated with the source and target stages.
• Delete processing, which involves executing the Delete processor and deleting the element at the source location of the move.

Note: If a Move action fails, you should first respond to the error, and then resubmit your request. When you restart a Move action after a source management failure, CA Endevor SCM performs source management, processor management, and delete processing. After a processor management failure, CA Endevor SCM performs processor management and delete processing. After a delete failure, CA Endevor SCM performs delete processing.