Ykrecver Command - HP StorageWorks P9000 Reference Manual

that depending on the status of the primary site, the status of the volumes in the primary site do
not change even after the copy pair is dissolved.
The site names are for cases when the copy direction of copy pair configuration and the copy
direction which is actually recognized on the storage system are the same. For the opposite copy
direction, replace the primary site and secondary site with the secondary site and primary site
respectively. However, do not dissolve copy pairs during a planned outage.
When dissolving copy pairs in a CG container specified by EXCTG ID, if all copy pairs are dissolved
from a journal group, that journal group will be deleted from the EXCTG. In addition, if all journal
groups are deleted from the EXCTG, the EXCTG data will be deleted.
Parameters
STEM(stem-name- 1 ) ~ <REXX prefix of 64 or fewer characters>
Specify the prefix of the name of the copy group structure that stores information about the copy
group for which you want to dissolve the copy pairs. Specify the same character string as the one
specified in the STEM parameter of the YKLOAD command that loaded the corresponding copy
group. You must also include a trailing period character.
MSG(stem-name-2) ~ <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.
DEVN(p-vol-device-number,s-vol-device-number) ~ <4-digit hexadecimal number, 4-digit
hexadecimal number>
Specify the device number of the copy pair (P-VOL and S-VOL) to operate.
NOTE: Do not dissolve copy pairs during a planned outage.
Return Codes
Table 128 (page 238)
Table 128 YKRECVER Command Return Code List
Return Code
-4095 to -4040
-3
-1
0
32
36
40
44
238 CLI Commands
lists the return codes to be returned when the YKRECVER 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 in an I/O configuration definition was detected.
Invalid or missing data in a REXX variable.
An error occurred while a REXX variable was being written.
Terminating due to processing errors.