Ykstore Command - HP StorageWorks P9000 Reference Manual
Business continuity manager software reference guide
Hide thumbs
Also See for StorageWorks P9000:
- Manual (333 pages) ,
- User manual (322 pages) ,
- Reference manual (236 pages)
Table of Contents
Advertisement
NOTE:
Start Usage Monitor from the Remote Web Console before executing the YKSTATS command.
Set the collection interval of Usage Monitor information to 10 minutes or less.
If the specified copy group is a CAJ copy group and contains the following volumes, in order
to obtain correct information, you must start Usage Monitor for the CU containing the journal
volumes used by the copy group.
◦
HP StorageWorks XP24000/XP20000 Disk Array volumes
◦
HP StorageWorks P9500 Disk Array
If the specified copy group is a CAA copy group and contains only HP StorageWorks
XP24000/XP20000 Disk Array volumes, you do not need to start Usage Monitor.
When CAA is used, the storage system serial number that is set in the REXX variable is the
information obtained from the storage system. When CAJ is used, the storage system serial
number that is set in the REXX variable is the value specified in the configuration file.
Before using the YKSTATS command to obtain operating information, use the
YKQUERY/YKEWAIT command to check if the copy pair status has been set. If no command
is entered, a determination is made based on the copy group status for the YKQUERY/YKEWAIT
command, and N/A might be displayed for operating information.
Return Codes
Table 134 (page 249)
Table 134 YKSTATS Command Return Code List
Return Code
-4095 to -4040
-3
-1
0
32
36
40
44
48
128
YKSTORE Command
Format
YKSTORE
STEM(stem-name-1)
1
PREFIX(prefix)
1
lists the return codes to be returned when the YKSTATS 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.
Terminating due to invalid parameters.
The command terminated abnormally. The user does not have permission to execute
this command.
Command details 249
Advertisement
Table of Contents
