Making the switch manager permanent
In the procedure Switching the master domain manager to the new backup master, you switched your master domain managermaster 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, perform the following steps:
- Edit the localopts file and modify the following entry as shown:
where new_mgr_cpu is the workstation name of the new master domain manager. For more information about localopts file, see Setting local options.DEFAULTWS=new_mgr_cpu
- Change the workstation definition of the back-level master by running:
and in the definition substitute type=manager with type=ftacomposer modify cpu=old_mgr_cpu
- Change the workstation definition of the new master by running:
and in the definition substitute type=fta with type=manager.composer modify cpu=new_mgr_cpu
- Ensure that the optman cf option is set to all.
- Rebuild the plan to activate the changes to the database:
JnextPlan -for 0000
- Switch the event processor to the new master domain manager by running the following
command:
switcheventprocessor new_mgr_cpu
- Restore the previous setting of the optman cf option, if necessary.
- Edit the
TWA_DATA_DIR/mozart/globalopts file and modify the
master=old_mgr_cpu entry as shown:
where new_mgr_cpu is the workstation name of the new master. For more information about optman, see Setting global options.master=new_mgr_cpu
In this way the reports reptr-pre and reptr-post can run when you run JnextPlan.
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.