HP XP Racks - Manual (Page 699)

either EDIT or MONITOR for a startup mode. To select a startup mode, assign the value
corresponding to the desired mode in the MODE initialization parameter.
•
EDIT
Starts the Business Continuity Manager agent in edit mode. When the Business Continuity
Manager agent is active in edit mode, copy groups can be defined, manipulated, and
monitored from Replication Manager.
•
MONITOR
Starts the Business Continuity Manager agent in monitor mode. After the Business Continuity
Manager agent is started in monitor mode, copy groups can only be monitored from Replication
Manager. Selecting monitor mode allows you to prevent copy groups from being defined or
manipulated from Replication Manager by users who should not be permitted to perform these
operations.
Select a startup mode, depending on which one is appropriate to the reason for using
Replication Manager.
Selecting Lock Mode
When the Business Continuity Manager agent is started in update mode, you can choose whether
configuration files are to be locked when the agent is running. Lock mode ensures that the
configuration files that the Business Continuity Manager agent shares with Business Continuity
Manager and the BCM Monitor remains consistent. If the Business Continuity Manager agent is
configured to start in update mode (because EDIT is assigned to the MODE parameter), you can
also assign one of the following values to the LOCK initialization parameter:
•
PREFIX – the Business Continuity Manager agent locks the configuration file while it is starting.
In an LPAR environment, the Business Continuity Manager agent locks the configuration file
that exists in the LPAR. Because the configuration file is locked, other users cannot update the
configuration file.
•
CHECK – the Business Continuity Manager agent does not lock the configuration file while it
is starting and, before subsequent updates, checks whether other users have updated the file.
This maintains configuration file consistency among the Business Continuity Manager agent,
Business Continuity Manager, and the BCM Monitor even when they are all running
concurrently.
If the Business Continuity Manager agent detects a previous update, the response to a
subsequent update attempt depends on the origin:
◦ Update request from Replication Manager: An error occurs and the configuration file
cannot be updated.
◦ Update request from the Business Continuity Manager ISPF panel: The Update Warning
panel appears, allowing the user to specify whether to update the configuration file.
NOTE: If the YKH2B or YKIMPORT command in Business Continuity Manager is used,
configuration files are also updated when an update is performed from a Business Continuity
Manager agent.
•
NONE – the Business Continuity Manager agent does not lock the configuration file or check
for updates by other users. Therefore, the consistency of the configuration file cannot be
assured.
NOTE: Before you assign NONE to the LOCK parameter, carefully consider how the
configuration file will be accessed and changed by other users.
Configuring a Business Continuity Manager agent 699