Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
Other
•
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 amounts of
data will be output to SYSLOG when you make frequent use of BCM or issue many CLI commands.
•
BCM does not support Data Exchange volumes.
•
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.
•
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).
•
After the storage system microcode is replaced, scan the storage system.
•
Specify a different storage system serial number for P-VOL and S-VOL when you define the copy
group definition of the copy type other than Business Copy.
•
Do not specify a different DADID from the DADID in a copy group definition when you specify a
DADID in the Set Defaults panel or the YKLOAD command's operand.
•
From BCM 06-00, it is necessary to set up the resource access control facility (RACF) to use the
CLI commands or BCM agent.
•
Do not perform PPRC operations on BCM copy pairs. If you perform PPRC operations to BCM
copy pairs, dissolve and re-establish the copy pairs using BCM.
You can resynchronize copy pairs with the CESTPAIR operation with the default operands only
if you perform the CSUSPEND operation with the default operands on the BCM copy pairs of a
Cnt-Ac S copy group without the C/T group ID.
•
If there is already a configuration file generated by the YKP2A command of the Mainframe Agent
program, make sure to use the different prefix value for BCM so that it does not reference the
configuration file generated by the YKP2A command. BCM does not accept a configuration file
generated by the YKP2A command. If such a file is used for any BCM operations, it causes an
error.
•
With BCM versions earlier than version 6.1.0-00, user SVCs cannot be used to suppress output
of IOS002A messages when the I/O path between the host and the storage system is disconnected
while device scanning is being performed. Therefore, in a mixed-version environment, make sure
to always use user SVCs of BCM version 6.1.0-00 or later.
Temporary restrictions
•
In a configuration in which supported XP disk arrays, XP P9500 Storage, and XP7 Storage coexist,
BCM can manage a configuration only when it consists of devices whose serial numbers are not
duplicates. Each device in the configuration must have a unique serial number.
•
When using BCM to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync,
do not perform the resync operation on a Cnt Ac-J copy pair that was automatically suspended
after performing Reverse Resync on Cnt Ac-S copy pairs to avoid forming a 3DC Cascade
configuration.
•
When using BCM to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync,
start the business operation after Cnt Ac-S and Cnt Ac-J copy pairs are formed so the Multi-Target
configuration is established.
10
Temporary restrictions
...