Errors that cause a PPRC pair to become suspended

A PPRC pair may become suspended for any of the following reasons:

Primary device write failure
Secondary device write failure
Secondary subsystem failure
Communications to secondary failure
Secondary not ready, intervention required

Either the I/O currently in process or the next I/O to the primary device of that PPRC pair is unit checked. The I/O that triggers the error may come from any attached system; therefore, the IEA49xx message can appear on any attached system’s console. An operating system issues an IEA49xx console message, indicating one of the previously listed suspension reasons, based on how the system detected this failure. It does not necessarily relate to the true cause of the failure.

If you originally established the suspended PPRC pair with CRIT(YES), the system unit checks the device when the Disk ERP reissues the I/O order. You then receive an IOS message similar to the following example:

 
  IOS000I 164,5D,CMD,47,0E00,00160000,VOLXXX,JOBNAME,
  800000005400000F57 .....
 
    Sense Byte 0 '80' - command reject
    Sense Bytes 7-8 '0F57' - Device 164 in Critical State

An application-related error message might follow the above message.