Editing timetables globally to change server ownership

Last Updated : Apr 05, 2024 |
Prolog information
Metadata
Keywords:
Use this procedure if the primary CMS server fails and you would like to globally edit timetables to ensure that they will all run on the secondary server.
The following procedure assumes that:
  • Timetables exist on both your primary and secondary CMS servers
  • The timetables are owned by more than one user
Important:
If you make administration changes on the secondary server during the interval in which the primary server is not operational, and you wish to transfer those changes to the primary server after it is restored, you must restore timetables to their normal run state on the two HA servers (see steps 8 through 13, below). If the primary server outage is not anticipated to be extensive in duration, it is recommended that no administration changes be made on the secondary server while the primary server is out of service.
  1. Log into the secondary CMS server as “cms”, so you have permission to globally edit all users’ timetables.
  2. Enter the timetable screen.
  3. Clear the timetable screen (Ctrl+Z) and use the List all function to determine all users who own timetables, and record their user IDs.
  4. Enter an individual user ID.
  5. Using the Global edit function, enter the Global edit screen for that user ID.
    ADDITIONAL INFORMATION:
    You will see the following:
    For all timetables owned by User ID XXXXXX
    Select one:
    < > Run timetables only on this CMS server
    < > Run timetables on this or another CMS server
    where XXXXXX is the user ID.
  6. Select one of the options listed in Step 5. Either option will immediately schedule all timetables for that user ID.
    ADDITIONAL INFORMATION:
    Important:
    Once the global edit has been performed on the secondary CMS server, it cannot be undone. The only way to undo a global edit to these timetables is to once again restore the timetables from the primary CMS server to the secondary CMS server.
  7. When the primary server is returned to service, choose between the following options:
    • If you have not made any CMS administration changes on the secondary server (including timetable modifications or revisions) that you wish to transfer to the primary server, return the timetables on the secondary server to their normal run state by using the most recent CMS administration backup created on the primary server and restoring it onto the secondary server. You can disregard the remaining steps.
    • If you have made any CMS administration changes on the secondary server and wish to transfer them to the primary server after it is brought back to service, continue with the additional steps listed below to return all timetables to their normal run state on the two HA servers.
  8. Do a CMS system administration backup of the secondary CMS server.
  9. On the primary server, change CMS to single-user mode.
  10. Restore system administration data to the primary CMS.
  11. Return CMS to multi-user mode on the primary server.
    ADDITIONAL INFORMATION:
    Now, all timetables on the primary CMS server are duplicates of the timetables on the secondary. However, since the “Run timetables only on this CMS server” global edit on all timetables occurred on the secondary CMS server, none of the timetables will run on the primary server.
  12. Repeat Steps 1 through 6 of this procedure on the primary server to globally edit the timetables to run only on the CMS server.
  13. Do a CMS system administration backup on the primary server and restore it onto the secondary server.