Making the switch manager permanent

About this task

In the procedure Switching the master domain manager to the new backup master, you switched your master domain manager promoting your new version backup master domain manager to the role of master domain manager.

To make this configuration fully operational and persistent through JnextPlan, you must complete the following procedure:

On the new master domain manager, referred to as new_mgr_cpu:
  1. Edit the localopts file and modify the following entry as shown: 
    DEFAULTWS=new_mgr_cpu
    where new_mgr_cpu is the workstation name of the new master domain manager. For more information about localopts file, see Setting local options.
  2. Change the workstation definition of the back-level master by running: 
    composer modify cpu=old_mgr_cpu
    and in the definition substitute type=manager with type=fta
  3. Change the workstation definition of the new master by running: 
    composer modify cpu=new_mgr_cpu
    and in the definition substitute type=fta with type=manager.
  4. Ensure that the optman cf option is set to all.
  5. Rebuild the plan to activate the changes to the database: 
    JnextPlan -for 0000
  6. Switch the event processor to the new master domain manager by running the following command:
    switcheventprocessor new_mgr_cpu
  7. Restore the previous setting of the optman cf option, if necessary.
  8. Edit the TWA_DATA_DIR/mozart/globalopts file and modify the master=old_mgr_cpu entry as shown: 
    master=new_mgr_cpu
    where new_mgr_cpu is the workstation name of the new master. For more information about optman, see Setting global options.

    In this way the reports reptr-pre and reptr-post can run when you run JnextPlan.

What to do next

Once you have made the switch manager permanent, you must run the FINAL job stream on the new master domain manager.

You can now proceed to Customizing and submitting the optional FINAL job stream.