NOTE:
•
The
YKLOAD
command is an REXX subroutine, so it should be called from REXX script by the
REXX CALL key word instruction.
•
When you execute the
YKLOAD
command more than once using the same stem-name, the
system overwrites the REXX variables.
•
The invoked script executed from CALL statement or
EXEC
command should not read a
configuration file with the same stem-name as the one read by the invoking script.
•
When operating without a route list, to execute the
YKLOAD
command several times, specify
the same DAD ID for all the instances of the
YKLOAD
command. The specified DAD ID should
be the DAD ID assigned to the storage system connected to the host where Business Continuity
Manager is running.
•
When operating with a route list, to execute the
YKLOAD
command several times, specify the
ROUTE
parameter for only the first executed instance of the
YKLOAD
command. For the
succeeding instances of the
YKLOAD
command, do not specify
ROUTE
parameter, but specify
the same DAD ID as for the first instance of the
YKLOAD
command. Note that if you drop the
route list structure, and then execute the
YKLOAD
command, you need to specify the
ROUTE
parameter.
•
Do not drop only some of the REXX variable structures created by the
YKLOAD
command. If
you do this, Business Continuity Manager might not operate properly. If you want to drop
some of the REXX variable structures, make sure that you drop all of them.
•
When you issue a command that requires a copy group stem-name as the input condition,
execute the
YKLOAD
command before executing that command.
•
Even if the
GROUP
parameter is not specified, the
YKL007E
message is not displayed if the
ROUTE
or
PATH
parameter is specified. If none of the
GROUP
,
ROUTE
and
PATH
parameters
are specified, the
YKL201E
message will be displayed.
•
Do not execute the
YKLOAD
command by specifying the DAD ID that was specified for the
remote scan or NG scan using the DAD parameter. Doing so will cause an error. This could
occur when, for example, a planned switch is made from the primary site to the secondary
site and the disk configuration definition file of the storage system on the secondary site (as
created by the remote scan) is copied to the secondary host.
Return Codes
Table 122 (page 225)
lists the return codes to be returned when the
YKLOAD
command terminates.
Table 122 YKLOAD Command Return Code List
Meaning
Return Code
The command completed normally.
0
Unknown XML attributes or elements encountered in input file.
4
Unable to resolve device number for S-VOL in copy pair.
8
Unable to resolve volume serial number for P-VOL in copy pair.
12
Unable to resolve device number for P-VOL in copy pair.
16
Terminating due to invalid XML structure encountered in input file, or system symbols
are not defined correctly.
Termination due to an error during license processing.
36
An error occurred when reading a file.
40
Terminating due to invalid processing.
44
Command details 225
Содержание P9000
Страница 302: ...YKDEMO12 302 CLI Commands ...