Entering coupled HOLD status

The master session enters the coupled HOLD status when one of the events in Table 1 occurs.

Table 1. Triggering events for coupled hold status
If the event is . . .	Then . . .
XRECOVER command	For the first XRECOVER command you issue for any of the coupled sessions associated with the master session, XRC places the master session in the coupled HOLD state to ensure a consistent recovery time for all sessions. The master session remains in HOLD status until the last coupled session is recovered.
Error in Session	An interlocked coupled session that detects an error suspends all duplex volumes in the session and places the master session in HOLD status.
Abnormal End or Cancel of a Session	A coupled session that abnormally ends (ABENDs) or is ended by a cancel command can cause the master session to be placed in HOLD status when the coupled session is restarted.
Sympathetic Suspend of Session	An interlocked coupled session suspends all volumes in the session if one of the following occurs: The interlocked coupled session detects that all volumes have been suspended for another interlocked coupled session, because of an error. The interlocked coupled session detects that another interlocked coupled session has not updated the master session for some time. XRC changes the master session state to coupled HOLD state when this occurs. The following are situations that will cause a sympathetic suspend: An error occurs to a volume of a duplex volume pair that was added with the ERRORLEVEL(SESSION) parameter. An error occurs to a session that forces the session's address space to be restarted, such as a session level error. A condition occurs where a session is not updating the master data set to indicate a current session consistency time. See What to do if a session is in COUPLE_FAILED status for a description of the COUPLE_FAILED status.