HP XP Array Manager Software User Manual
Page 110

For example, you can specify RCLU CL1-C.01:CL2-A.01, but you cannot specify
RCLU CL2-A.01:CL1-C.01. Also, you can specify RCLU CL1-C.01:CL1-C.03, but you
cannot specify RCLU CL1-C.03:CL1-C.01.
If port-name.host-group-id is not specified, the monitoring data of all the LU paths will be exported.
RCLDEVU[[LDKC-CU-id]:[LDKC-CU-id]][U…]|
Use this operand when you want to export statistics about remote copy operations which are
displayed in the Continuous Access Monitor window and the TrueCopy for Mainframe Monitor
window. By using this operand, you can export monitoring data about remote copy operations
performed by Continuous Access and TrueCopy for Mainframe at volumes controlled by each
CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning
with RCLDEV_ will be output. For details on the statistics exported by this operand, see
on page 84 in “
When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the
volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of an LDKC:CU. The
colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05.
Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on
the right of the colon. For example, you can specify RCLDEV 105:000.
If LDKC-CU-id is not specified, the monitoring data of all the volumes will be exported.
RCCLPR
Use this operand when you want to export statistics about remote copy operations which are
displayed in the Continuous Access Monitor window and the TrueCopy for Mainframe Monitor
window. By using this operand, you can export monitoring data about remote copy operations
performed by Continuous Access and TrueCopy for Mainframe at each CLPR. When statistics are
exported to a ZIP file, the file name will be RCCLPR_dat.ZIP. For details on the statistics exported
by this operand, see
Note
: Monitoring data are grouped by SLPR, and are exported per CLPR. If there are two SLPRs
that are SLPR0 (corresponding to CLPR0, and CLPR2) and SLPR1 (corresponding to CLPR1),
those CLPRs are arranged as follows: CLPR0,CLPR2,CLPR1.
UniversalReplicator
Use this operand when you want to export statistics about remote copy operations which are
displayed in the Continuous Access Journal Monitor window and the Universal Replicator for
Mainframe Monitor window. By using this operand, you can export monitoring data about
remote copy operations performed by Continuous Access Journal and Universal Replicator for
Mainframe in the whole storage system. When statistics are exported to a ZIP file, the file
name will be UniversalReplicator.ZIP. For details on the statistics exported by this operand, see
on page 85 in “
URJNLU[[JNL-group-id]:[JNL-group-id]][U…]
Use this operand when you want to export statistics about remote copy operations which are
displayed in the Continuous Access Journal Monitor window and the Universal Replicator for
Mainframe Monitor window. By using this operand, you can export monitoring data about
remote copy operations performed by Continuous Access Journal and Universal Replicator for
Mainframe at each journal group. When statistics are exported to a ZIP file, the file name will be
URJNL_dat.ZIP. For details on the statistics exported by this operand, see
on page 86 in
When you specify variables JNL-group-id, you can narrow the range of journal groups whose
monitoring data are to be exported. JNL-group-id is a journal group number. The colon (:)
indicates a range. For example, 00:05 indicates journal groups from 00 to 05.
Ensure that the JNL-group-id value on the left of the colon is smaller than the JNL-group-id value
on the right of the colon. For example, you can specify URJNL 00:05, but you cannot specify
URJNL 05:00.
If JNL-group-id is not specified, the monitoring data of all the journal volumes will be exported.
110
Using the Export Tool