Operations after the configuration file is locked
A Business Continuity Manager agent with the LOCK(PREFIX) parameter specified, the ISPF
panel of Business Continuity Manager, and BCM Monitor all lock the configuration files during
startup. This prevents other users from updating the same configuration files.
BCM Monitor and the ISPF panel use the same method to lock the Business Continuity Manager
agents.
If the Business Continuity Manager agent has already been started
Figure 132 (page 541) shows operation in the following situation: A Business Continuity Manager
agent starts and locks the configuration files with prefix BCM.A. After that, another user issues a
request for the locked configuration file.
The Roman numerals (i) to (v) in Figure 132 (page 541) correspond to the following descriptions.
Figure 132 If the Business Continuity Manager (BC Manager) agent has already been started
(i) Business Continuity Manager agent 2
Because LOCK(PREFIX) is specified, the agent attempts to lock the configuration
file while it is starting. However, the attempt will fail because the configuration file
with prefix BCM.A has already been locked. As a result, this agent fails to start.
Configuring a Business Continuity Manager agent 541
To Next Page
Loading...
