Votos - 0, Puntuación media: 0
(
)
)
|
Otros manuales para este modelo:
Resumen del manual
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 the multiplatform volume.
•
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 V6.1, 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 V6.1 or later.
Temporary restrictions
Table 11 Restrictions
#
Restrictions
1
In a configuration in which supported XP and P9000 disk arrays 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.
2
If you issue the YKQUERY, YKQRYDEV, or YKEWAIT command to a BC copy group in an XP1024 disk array
immediately after executing the YKDELETE command, these commands may report the status of a copy pair to be
SIMPLEX even though the actual status is in the middle of transition to SIMPLEX (not fully becoming SIMPLEX).
Therefore, when issuing the YKMAKE command to the same BC volumes after executing the YKDELETE command,
wait for approximately 10 seconds before issuing the YKMAKE command.
3
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.
10
Temporary restrictions
...