XSUSPEND of all coupled XRC sessions

In a coupled environment, you can issue the XSUSPEND command to a master session. All sessions are suspended with their active duplex volumes at a consistent time across the coupled sessions.

You can issue the XSUSPEND command to an individual XRC session only: If you issue an XSUSPEND command with TIMEOUT(hh.mm.ss) to an XRC session that is part of a coupled session, the command is rejected. A return code is returned that indicates that the session is coupled.
To uncouple and suspend an XRC session that is part of a coupled session, you can use one of the following methods:

If you issue an XSUSPEND command for one or more volume pairs in a session, the command operates in the same manner in a coupled or noncoupled environment. The system suspends the specified volume or set of volumes and manages the remainder normally. If the last volume in a coupled session is suspended, the status of the session changes to NON-INTERLOCKED and the session is not kept consistent to the same time as the other coupled sessions.

The IMMEDIATE, ATTIME, and DRAIN parameters allow you to control when the suspension of the master session or an uncoupled XRC session occurs.

After you issue the XSUSPEND command to the master session, XRC prompts you (unless you have specified NOVERIFY) to confirm the request to suspend the master session or set of specified volumes. You must specify either YES or NO. If the XSUSPEND command is invoked through a CLIST written in REXX, you should either specify NOVERIFY or place your response to the prompt in the data stack prior to issuing the command. In a batch environment, you can stack the response.