HP StorageWorks P9000 Reference Manual page 234

DKC
Out of the logical paths within the path set stored in the path set structure specified by the STEM
parameter, the status is acquired for the logical paths that have DKC set for
stem-name-specified-in-STEM-parameterPATH.n.type.
NOTE:
Before executing the command, create and load the path set definition file.
If a message that contains sense information for the storage system is output, see the list of
error codes in the HP StorageWorks P9000 for Business Continuity Manager Software
Messages and then eliminate the cause of the error. Alternatively, in the Edit Logical Path
Definition panel, specify a different, valid volume on which a device scan has been performed,
in CU, SSID, and CCA in the path set definition file for the command execution target.
When you execute the YKQRYPTH, YKBLDPTH, or YKDELPTH command after executing the
YKQRYPTH command with the RESTRUCT parameter specified, use the information obtained
from the storage system.
Return Codes
Table 126 (page 234)
Table 126 YKQRYPTH Command Return Code List
Return Code
-4095 to -4040
-3
-1
0
4
8
12
32
36
40
44
48
234 CLI Commands
lists the return codes to be returned when the YKQRYPTH 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. All paths are established.
Successful completion. A logical path exists for which not all of the corresponding
physical paths are established.
The port information stored in the REXX variable of the detected logical path
does not match the port information that is set on the storage system.
The port information recorded in the REXX variable was updated.
The command terminated normally, but detected a logical path whose corresponding
physical paths include a path with abnormal status.
One or more I/O errors were encountered. None or only some of the logical
paths was acquired.
A change in an I/O configuration definition was detected.
No target path was found.
An error occurred while a REXX variable was being read or written.
Command execution terminated abnormally due to insufficient capacity or some
other internal cause. None or only some of the logical paths were acquired.
Command execution terminated because of an invalid parameter. Acquisition of
the status of all logical paths was not successful.