text: (cid:2) Step 2: 
  
  a. When an MM/GM relationship is started in the ConsistentStopped state, the MM/GM 
  relationship enters the ConsistentSynchronized state. Therefore, no updates (write 
  I/O) were performed on the master volume while in the ConsistentStopped state. 
  Otherwise, the**-force**option must be specified, and the MM/GM relationship then 
  enters the InconsistentCopying state while the background copy is started. 
  
  b. When an MM/GM relationship is started in the InconsistentStopped state, the MM/GM 
  
  relationship enters the InconsistentCopying state while the background copy is 
  started. 
  
  (cid:2) Step 3: 
  
  When the background copy completes, the MM/GM relationship changes from the 
  InconsistentCopying state to the ConsistentSynchronized state. 
  
  (cid:2) Step 4: 
  
  a. When a MM/GM relationship is stopped in the ConsistentSynchronized state, the 
  
  MM/GM relationship enters the Idling state when you specify the**-access**option, 
  which enables write I/O on the auxiliary volume. 
  
  b. When an MM/GM relationship is stopped in the ConsistentSynchronized state without 
  an**-access**parameter, the auxiliary volumes remain read-only and the state of the 
  relationship changes to ConsistentStopped. 
  
  c. To enable write I/O on the auxiliary volume, when the MM/GM relationship is in the 
  ConsistentStopped state, issue the**svctask stoprcrelationship**command, which 
  specifies the**-access**option, and the MM/GM relationship enters the Idling state. 
  
  (cid:2) Step 5: 
  
  a. When an MM/GM relationship is started from the Idling state, you must specify the 
  **-primary**argument to set the copy direction. If no write I/O was performed (to the 
  master or auxiliary volume) while in the Idling state, the MM/GM relationship enters 
  the ConsistentSynchronized state. 
  
  If write I/O was performed to the master or auxiliary volume, the**-force**option must be 
  specified and the MM/GM relationship then enters the InconsistentCopying state 
  while the background copy is started. The background process copies only the data 
  that changed on the primary volume while the relationship was stopped. 
  
  b. 