Ykconmsg Command - HP StorageWorks P9000 Reference Manual

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 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.
If all of the volumes in the CU are Non Gen'ed volumes, load the route list before executing
the command.
Return Codes
Table 103 (page 195)
Table 103 YKBLDPTH Command Return Code List
Return Code
-4095 to -4040
-3
-1
0
32
36
40
44
48
128

YKCONMSG Command

Applies to Business Copy for Mainframe, Continuous Access Synchronous for Mainframe, Continuous
Access Synchronous for Mainframe with the HyperSwap attribute, and Continuous Access
Asynchronous for Mainframe.
Format
YKCONMSG
{ OP(OPEN) [
1
OP(GET) HANDLE(X'handle')|
1 1
OP(CLOSE)
1
lists the return codes to be returned when the YKBLDPTH 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. None or only some of the logical paths were
established.
A change to an I/O configuration definition was detected.
Processing was interrupted because a REXX variable with an invalid value was
encountered. No logical paths were established.
No path to be established 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 established.
Command execution terminated because of an invalid parameter. No logical paths
were established.
The command terminated abnormally. The user does not have permission to execute
this command.
MSGID({IEA494|IOSHM0414I|user-specified-message-ID})][
1
HANDLE(X'handle')}
1
TIMEOUT(timeout-value)]|
1
Command details 195