CA Datacom/AD supports use of a secondary or shadow MUF on another system in the sysplex. The Shadow MUF can take over in the event of a primary MUF outage, thus minimizing loss of functionality.
The shadow MUF users must consider that the order in which the MUF is started relative to the others in the sysplex determines the role that the MUF plays. The MUF that is started first acts as the primary MUF. The second MUF becomes the Shadow MUF.
If you are using a dormant copy of CA7ONL (TYPE=DORM), you can start the Shadow MUF on the LPAR where the dormant copy executes.
If you use the IBM Automatic Restart Manager (ARM) policy to redirect CA7ONL to a different LPAR in the event of an outage, consider executing a Shadow MUF on that target LPAR. Refer to your ARM policy information.
Note: For more information, see the CA Datacom/AD documentation and the Systems Programming Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|