Example: applying software maintenance in a coupled environment

The commands that are listed allow you to suspend coupled sessions so that you can perform maintenance on individual sessions, and then add the individual sessions back to the master session after maintenance has been completed.

The following scenario describes how to perform software maintenance operations in a coupled environment:

  1. Suspend all sessions coupled to the master session, which is named CXRC and has a default master high-level qualifier of SYS1, on the day and time indicated by the ATTIME parameter by entering:
    XSUSPEND CXRC ATTIME(2004.145 18:00:00) TIMEOUT(04.00.00)

    All sessions are suspended with their active duplex volumes at a consistent time across the coupled sessions. You can now apply whatever maintenance processes you want. It is assumed that maintenance will take no more than four hours to complete.

  2. Issue the following command to restart the XRC session named TUCSON. After software maintenance operations have completed, take copies of secondary volumes, if needed, to maintain consistency during the resynchronization process.
    XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(SESSION)
  3. Issue the following command to restart the XRC session named PHOENIX:
    XSTART PHOENIX SESSIONTYPE(XRC) ERRORLEVEL(SESSION)
  4. Take copies of secondary volumes, if needed, after software maintenance operations have completed. Taking copies maintains consistency during the resynchronization process.
Note: Doing things in the order described in the example allows XRC to start tracking changes to volumes that are not on a 2105 controller.