Optional parameters

MHLQ(mhlq): Specifies the high-level qualifier of the master session control data set. The default is SYS1. If you specify the MHLQ parameter on the XSUSPEND command, and the session_id specified is an XRC session name, the MHLQ parameter will be ignored.
ATTIME: When XSUSPEND is issued using a master session name, the ATTIME parameter is processed as global ATTIME if no component session consistency time has passed the requested timestamp. If any session has passed the time, the command is rejected.
DRAIN: All sessions in a coupled master session determine a ‘drain time’. When XSUSPEND is issued using a master session name, the DRAIN parameter is processed as ATTIME by using the latest component drain time.
CANCEL: Specifies that XRC cancel the previous master XSUSPEND command that has not yet processed. The CANCEL option cancels a pending XSUSPEND command that was issued to the master session, but not yet processed. If the XSUSPEND command has started processing on any session, the CANCEL request fails.
A pending XSUSPEND VOLUME(ALL) to a master session cannot be canceled from the master session. Instead, you must issue an XSUSPEND CANCEL VOL(volser_list) from each individual coupled session to specify all volumes in that session by primary volume serial number.
IMMEDIATE: When you issue the XSUSPEND command by using a master session name, the command will be processed on all XRC sessions that are coupled to the master session. In this instance, the IMMEDIATE parameter is processed as ATTIME equal to a time that permits all coupled sessions to be ended at the same consistency time.
NOVERIFY: Specifies that XRC not issue message ANTT0028A, which prompts the user to confirm that XRC should continue to process the command. If you select this option, XRC immediately processes the command without waiting for verification.
MSGROUTEID: Specifies the user ID to which XRC messages associated with the processing of this command are routed. If the specified user ID is not logged on, TSO saves messages in the TSO BRODCAST data set and displays them after the next logon.
Note: Messages issued by the initial command parser routine are sent to the user ID that issues the TSO command.