Use the XEND command to stop all XRC activity to active volumes and to end the XRC session. Issuing the XEND command stops all updates to the secondary volumes at the time specified.
In a coupled environment, you can issue the XEND command to a master session to have all sessions end with their volumes consistent to the same time.
The XEND command returns a timestamp indicating that the data on the secondary volumes of all active pairs is consistent with the corresponding data that was on the primary volumes at the specified time.
After you issue the XEND command, XRC prompts you (unless you have specified NOVERIFY) to confirm the request to end the session. You must specify either YES or GR215NO. If the XEND 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 before issuing the command. In a batch environment, you can stack the response.
An XEND command that specifies an ATTIME value overrides a time that was specified with a previous XEND command. Also, an XEND command that specifies an ATTIME value overrides a pending XSUSPEND(session_id) command function.
All secondary volumes are consistent up to the UTC timestamp that is reported by successful completion of the command. The storage control session ends after the time that is determined by the XEND command. Record updates in the journal data set are discarded and not available for a subsequent recovery. If you issue an XRECOVER command, the secondary volume serial numbers of volume pairs in the duplex or seqcheck state are changed to match ("clipped to") the primary volume serial number, but no journal updates are applied to the volumes. The secondary volume serial numbers of suspended volume pairs are also clipped, provided that the pair had completed initial volume synchronization prior to being suspended.
For information about how to end coupled sessions, refer to XEND in a coupled environment.