valutazioni - 0, GPA: 0
(
)
)
|
da questo dispositivo ha anche altre istruzioni :
Facilità d'uso
configurations are XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or P9500
disk arrays. N:1 configuration and a configuration that consists of 4 or more DCs are not
supported.
3.
BCM supports 4x4 and 4x4x4 Multi-Target configurations. Note that the configuration should
consist entirely of XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or P9500
disk arrays.
4.
BCM supports 4x4x4 Cascade configurations. Note that the configuration should consist entirely
of XP12000/XP10000 disk arrays or XP24000/XP20000 disk arrays.
Remote DKC control function
1.
When using Remote DKC control function, use Fibre link for connection between DKCs. ESCON
link is not supported. When you define the logical path between CUs for Remote DKC control
function, you must define the path between CUs that belong to the command device volumes.
2.
To share a command device among multiple operating systems, ensure that the &YKCMDIF variable
is either defined in the IEASYM member or set by the START YKSETENV command.
3.
When allocating a command device, note the following items:
•
Parity group cannot be moved if a command device is defined within the parity group.
•
Parity group type cannot be changed if the command device is defined within the parity
group.
•
The command device between LCUs cannot be moved.
•
The volume size of the command device cannot be changed (550 cylinders are required for
XP128 or XP1024 disk arrays).
Copy types
There should not be mix of copy types within a single copy group. Ensure that all volumes are SIMPLEX
in the initial state. BCM does not display the pair status correctly in the following conditions:
•
Copy group definition is changed when not all pairs are SIMPLEX.
•
Pair configuration in copy group definition differs from the actual pair configuration.
Other
1.
From BCM 04-00, CLI Command-Execution Logs are output to SYSLOG. This applies to the CLI
commands that are executed from within the ISPF panels of BCM. Therefore, large amount of
data will be output to SYSLOG when you make frequent operation of BCM or issue many CLI
commands.
2.
BCM does not support the multiplatform volume.
3.
From z/OS V1R8, a console ID cannot be specified to the CN operand of the TSO/E SEND
command. Because of this, a console ID cannot be specified for the CN operand of the YKWATCH
command when using it on z/OS V1R8 or later. If the console ID is specified, the TSO/E SEND
command that is used in the YKWATCH command will fail and the YKWATCH does not return the
expected message.
4.
From BCM 06-00, it becomes impossible to use the configuration file made by versions earlier
than 02-00. (APIInfo Level in the configuration file is “1.1.0” or earlier).
5.
After the DKC microcode is replaced, scan the DKC.
6.
Specify a different DKC serial number for P-VOL and S-VOL when you define the copy group
definition of the copy type other than Business Copy.
7.
Not to specify the different DADID from the DADID in copy group definition when you specify a
DADID in the Set Defaults panel or the YKLOAD command's operand.
8.
From BCM 06-00, it is necessary to set up the resource access control facility (RACF) to use the
CLI commands or BCM agent.
Compatibility/Interoperability
15
...