Ykbldpth Command; Ykbldcmd Command - HP StorageWorks P9000 Reference Manual

Parameters
SN(storage system-serial-number) ~ <from 5 to 12 alphanumeric characters>
Specify the storage system serial number. Only the command device with the specified storage
system serial number is created.
MSG(stem-name- 1 ) ~ <REXX prefix of 64 or fewer characters>
Specify an optional prefix for the name of the message structure used to store the messages to be
generated by this command. You must also include a trailing period character.
The message structure is initialized when the CLI command with the same name as the MSG
parameter is specified.
NOTE:
Execute the YKBLDCMD command only once after turning on the storage system. Even if this
command is entered multiple times, only the first time is effective, and entry after the first time
does not take effect. However, before this command is entered, make sure that storage system
control with the corresponding command device did not take place.
For the YKBLDCMD command, you need to input the storage system for the primary site and
secondary site, according to the site order defined in the route list. Enter for the primary site
first, and then for the secondary site.
Do not delete paths (inter-CU logical paths or inter-DKC logical paths) among storage systems
when a command device is registered.
The corresponding command device should be offline before the YKBLDCMD command is
executed.
Return Codes
Table 102 (page 192)
Table 102 YKBLDCMD Command Return Code List
Return Code
-4095 to -4040
-3
-1
0
32
40
44
48
128

YKBLDPTH Command

Applies to PTH.
192 CLI Commands
lists the return codes to be returned when the YKBLDCMD command terminates.
Meaning
The command terminated abnormally, possibly because the user SVC routine has
not been included properly.
The module cannot be loaded. Possible causes are as follows:
The library dataset has not been linked.
The module is protected by the RACF program control function.
An interruption occurred during execution.
The command completed normally.
I/O errors were encountered.
A change to an I/O configuration definition was detected.
An error occurred while a REXX variable was being written.
Terminating due to processing errors.
Terminating due to invalid parameters.
The command terminated abnormally. The user does not have permission to execute
this command.