(ii) Business Continuity Manager agent 3
Because LOCK(CHECK) or LOCK(NONE) is specified, the agent does not attempt
to lock the configuration file while it is starting. As a result, the configuration file
with prefix BCM.A can be used to start this agent.
(iii) Business Continuity Manager agent 4
Because this agent is in monitor mode, it does not attempt to lock the configuration
file while it is starting. As a result, the configuration file with prefix BCM.A can be
used to start this agent.
(iv) Business Continuity Manager user (ISPF panel) and BCM Monitor
If a user attempts to start the Business Continuity Manager ISPF panel by using a
configuration file with prefix BCM.A, an error is displayed in the Set Defaults panel
and the attempt fails.
Likewise, if a user attempts to change the prefix of a configuration file to BCM.A,
an error is displayed in the Set Defaults panel and the attempt fails.
If a user attempts to start BCM Monitor by using a configuration file with prefix
BCM.A, the attempt fails.
(v) Business Continuity Manager user (CLI command)
The user can execute CLI commands. Note however that the YKH2B and YKIMPORT
commands return an error because these commands update configuration files.
If the ISPF panel or BCM Monitor has already been started
Figure 133 (page 543) illustrates what occurs when a BCM user (from the ISPF panel) or BCM
Monitor starts and locks the configuration files with prefix BCM.B. Subsequently, another user
issues a request for the locked configuration file
The Roman numerals (i) to (iv) in Figure 133 (page 543) correspond to the following descriptions.
542 Linkage with Replication Manager
To Next Page
Loading...
Need help?
General