Parameters

PORT(port-number) ~ <numeric characters> ((1-65535)) <<24042>>: Specifies the Business Continuity Manager agent port for TCP/IP communication with Replication Manager. You cannot specify a port number that is being used by another job. Specify a port number that is not being used in the system.

RECVWAITTIME(reception-wait-time) ~ <numeric characters> ((0-65535)) <<180>>: When TCP/IP communication with Replication Manager is performed, this parameter specifies the wait time (in seconds) from when a receive request is initiated to when data is received. A value of 0 means that the Business Continuity Manager agent is to wait for data indefinitely.

HOSTNAME('host-identification-name') ~ <1 to 50 alphanumeric characters> <<value specified for the &SYSNAME system symbol>>

Specify this parameter when Replication Manager needs to identify the Business Continuity Manager agent. When the Business Continuity Manager agent is running on more than one host, and a HOSTNAME (host identification name) value is duplicated in these hosts, Replication Manager cannot identify the host on which the target Business Continuity Manager agent is running. To ensure that Replication Manager can identify the host on which the Business Continuity Manager agent is running, specify a unique HOSTNAME value for each host.

When this parameter is omitted, the value of the &SYSNAME system symbol is assumed. For details about the &SYSNAME system symbol, see the IBM manual MVS Initialization and Tuning Reference.

When the Business Continuity Manager agent runs on more than one host and an &SYSNAME system symbol value is duplicated in these hosts, Replication Manager cannot distinguish between the hosts. When the &SYSNAME system symbol value is duplicated, make sure that HOSTNAME values are unique among the hosts.

PREFIX('prefix','local-site's-DAD-ID'[,'route-list-ID[,{route-label|*}'[,['local-site's-Non-Gen'ed-DAD-ID'][,'remote-site's-DAD-ID']]])

To enable Replication Manager to manipulate the Business Continuity Manager agent, the prefix of the configuration files managed by Business Continuity Manager must be specified.

You can specify multiple PREFIX parameters. Specify multiple PREFIX parameters when the storage information to be acquired is information registered in multiple configuration files that have different prefixes, in an environment where Replication Manager and the Business Continuity Manager agent are one-to-one.

prefix ~ <PREFIX string consisting of 1 to 16 characters>: Specifies the prefix of the Business Continuity Manager configuration files that are used by Replication Manager. Specify the value that was specified in Configuration File Prefix in Business Continuity Manager's Set Defaults panel when the configuration file was created. Replication Manager can use the disk configuration definition file and the copy group definition file with the prefix specified here. For details about the Set Defaults panel in Business Continuity Manager, see the Hitachi Business Continuity Manager Reference Guide.

local-site's-DAD-ID ~ <DAD string consisting of 1 to 28 characters>

Specifies the device address domain ID of the local site on which the Business Continuity Manager agent is operating. When monitoring PPRC copy pairs, specify the value that was specified in Device Address Domain, Primary or Device Address Domain, Secondary in the Scan Copy Pair Inside Storage System panel when the copy group definition file for PPRC copy pairs was created. For details about the Scan Copy Pair Inside Storage System panel in Business Continuity Manager, see the Hitachi Business Continuity Manager Reference Guide.

If you specify multiple PREFIX parameters, we recommend that you use the same device address domain ID for all of the device address domain IDs on the local site.

Note: Do not specify the local site's Non Gen'ed device address domain ID or the remote site's device address domain ID.

route-list-ID ~ <ROUTE string consisting of 1 to 8 characters>

Specifies the route list ID for the Business Continuity Manager agent when the Remote DKC Control function is used.

You must specify a route list ID in order to use the Remote DKC Control function.

{route-label|*} ~ <ROUTELABEL string consisting of 1 to 8 characters>

If you specify a route label, command devices that have the specified route label are used.

If you specify *, all command devices are used regardless of whether they have a route label.

If you specify neither a route label nor *, command devices that have no route label are used.

local-site's-Non-Gen'ed-DAD-ID ~ <DAD string consisting of from 1 to 28 characters>

Specifies the Non Gen'ed device address domain ID used by the local site on which the Business Continuity Manager is operating.

Specify an asterisk (*) in place of the local site's Non Gen'ed device address domain ID to omit it while specifying the following value (remote site's device address domain ID).

Note also that to acquire information about Non Gen'ed volumes, you must specify the local site's Non Gen'ed device address domain ID.

Note:

Do not specify the local site's device address domain ID or the remote site's device address domain ID.
If you specify multiple PREFIX parameters, specify the same device address domain ID for all of the local site's Non Gen'ed device address domain IDs.

remote-site's-DAD-ID ~ <DAD string consisting of from 1 to 28 characters...>

Specifies the device address domain ID of the remote site on which the Business Continuity Manager agent performs remote scans.

To specify multiple device address domain IDs, separate consecutive device address domain IDs with a colon (:), as shown in the following example:

Example: DAD1:DAD2:...

Note also that to acquire information about volumes at the remote site, you must specify the remote site's device address domain ID.

Note:

Do not specify the local site's device address domain ID or the local site's Non Gen'ed device address domain ID.
If a site is being used as a local site by another Business Continuity Manager agent, you cannot specify it for use as a remote site.

Note: Notes about specifying the PREFIX parameter

Do not specify a nonexistent prefix or device address domain ID in the PREFIX parameter. Even though specifying a nonexistent prefix or device address domain ID does not result in an error during Business Continuity Manager agent startup, an error will occur during a Replication Manager request.
In the PREFIX parameter, do not specify any value other than the prefix of the configuration file. If multiple datasets correspond to the specified prefix (such as the SYS1 prefix), Business Continuity Manager agent processing might slow down.
If you specify the same prefix multiple times for MODE(MONITOR), the monitoring processing of Replication Manager might slow down. If you specify the same prefix multiple times for MODE(EDIT), an error will occur and you will be unable to start the Business Continuity Manager agent.
If you specify multiple PREFIX parameters, it will take time to switch the configuration files for each prefix during a Replication Manager request. Therefore, if there are many configuration files, we recommend that you aggregate prefixes in the configuration files so that there is only one PREFIX parameter, to shorten the access time for a request from or a response to Replication Manager.
If you want to modify a configuration file that has a prefix specified in the PREFIX parameter, make sure you use the ISPF panel or Replication Manager. If you use another method, information might not be displayed on Replication Manager, or an error might occur.
The access time for a Replication Manager request or response becomes longer according to the number of copy pairs defined in the copy group definition file that has the specified prefix. Therefore, specify the monitoring interval of Replication Manager to fit the environment (the host capability corresponding to the number of copy pairs).

DEVN(start-device-number,end-device-number) ~ <4 hexadecimal characters>: Specifies a range of devices from which to collect information when filtering the host volume information to be passed to Replication Manager. Specify the start-device-number and end-device-number in the ascending order of hexadecimal characters. If the DEVN parameter has not been specified before, DEVN(0000,FFFF) is assumed.

Note: Notes about specifying the DEVN parameter

To reduce the access time required for requests and replies from Replication Manager, we recommend that you specify a range of target devices from which information is collected.
When you specify more than one DEVN parameter, even if there are duplicate devices, they are not eliminated, so make sure you avoid specifying such duplications.

LOGLEVEL(output-level) ~ <numeric character> ((0-3)) <<2>>

Specifies the log output level.

0: Logs are not output. If 0 is specified, it is difficult to determine the cause of a communication failure or an error that occurs during execution of a Business Continuity Manager agent command.

1: Communication-related messages (YKY300I, YKY301I, YKY304I, and YKY307I) are output.

2: In addition to the messages that are output when LOGLEVEL(1) is specified, both the YKY680I and YKY500I messages are output. The YKY680I message is output when an error occurs during an update request for a copy pair configuration or a copy pair status. The YKY500I message displays the results of updated configuration files.

3: In addition to the information output with LOGLEVEL(2), BCM logs are output.

The following table shows the LOGLEVEL specification and the messages that are output.

Table. LOGLEVEL specification and the output messages
LOGLEVEL	Output messages
`0`	No output
`1`	`YKY300I`, `YKY301I`, `YKY304I`, and `YKY307I`
`2`	`YKY300I`, `YKY301I`, `YKY304I`, `YKY307I`, `YKY500I`, and `YKY680I`
`3`	`YKY300I`, `YKY301I`, `YKY304I`, `YKY307I`, `YKY500I`, and `YKY680I`

AUDITLOG(SYSLOG)

Specifies whether to output audit logs. When specified, the following additional information will be output to SYSLOG:

Name and return code of CLI commands that end with an error
Name and return code of CLI commands that end successfully (only for operational commands)

Audit logs are not output if the AUDITLOG parameter is not specified.

If the AUDITLOG parameter is specified, operations are performed as if LOGLEVEL(2) or later was specified.

MODE(startup-mode) ~ ({EDIT|MONITOR}) <<MONITOR>>

Specifies the permission level at which the Business Continuity Manager agent starts.

EDIT: Allows definition, processing, and monitoring of copy groups.

MONITOR: Allows monitoring of copy groups.

LOCK(lock-mode) ~ ({PREFIX|CHECK|NONE}) <<PREFIX>>

Specifies the lock mode of the configuration files. The LOCK parameter is valid only when MODE(EDIT) is specified. An error occurs if the LOCK parameter is specified when MODE(MONITOR) is specified.

PREFIX: Locks configuration files based on file name prefixes when the Business Continuity Manager agent starts. Other users cannot update configuration files that are locked.

CHECK: Does not lock configuration files when the Business Continuity Manager agent starts. When the Business Continuity Manager agent updates a definition, it verifies that no other user has updated the configuration file that it is about to update.

NONE: Does not lock the configuration files when the Business Continuity Manager agent starts.