text: **Path Offline for the source Volume**
  If a FlashCopy mapping is in the copying state and the source volume goes path offline, this 
  path offline state is propagated to all target volumes up to, but not including, the target volume 
  for the newest mapping that is 100% copied but remains in the copying state. If no mappings 
  are 100% copied, all of the target volumes are taken offline. Path offline is a state that 
  exists on a per-node basis. Other nodes might not be affected. If the source volume comes 
  online, the target and source volumes are brought back online. 
  
  **Path Offline for the target Volume**
  If a target volume goes path offline but the source volume is still online, and if any dependent 
  mappings exist, those target volumes also go path offline. The source volume remains online. 
  
  **11.1.18 Asynchronous notifications**
  
  FlashCopy raises informational event log entries for certain mapping and Consistency Group 
  state transitions. These state transitions occur as a result of configuration events that 
  complete asynchronously. The informational events can be used to generate Simple Network 
  Management Protocol (SNMP) traps to notify the user. 
  
  Other configuration events complete synchronously, and no informational events are logged 
  as a result of the following events: 
  
  (cid:2) PREPARE_COMPLETED 
  
  This state transition is logged when the FlashCopy mapping or Consistency Group enters 
  the prepared state as a result of a user request to prepare. The user can now start (or 
  stop) the mapping or Consistency Group. 
  
  (cid:2) COPY_COMPLETED 
  
  This state transition is logged when the FlashCopy mapping or Consistency Group enters 
  the idle_or_copied state when it was in the copying or stopping state. This state 
  transition indicates that the target disk now contains a complete copy and no longer 
  depends on the source. 
  
  (cid:2) STOP_COMPLETED 
  
  This state transition is logged when the FlashCopy mapping or Consistency Group enters 
  the stopped state as a result of a user request to stop. It is logged after the automatic copy 
  process completes. This state transition includes mappings where no copying needed to 
  be performed. This state transition differs from the event that is logged when a mapping or 
  group enters the stopped state as a result of an I/O error. 