HP XP P9000 for Compatible High Perf FICON Connectivity Software - Manual (Page 132)

Table 27 Files with statistics about remote copy operations by Cnt Ac-J and Cnt Ac-J Z (at Volumes
controlled by a particular CU) (continued)
Data saved in the file CSV file ZIP file
The amount of data that are read per
second (KB/sec) URLDEV_Read_Transfer_xx.csv URLDEV_dat/URLDEV_Read_Transfer.ZIP
The amount of data that are written per
second (KB/sec) URLDEV_Write_Transfer_xx.csv URLDEV_dat/URLDEV_Write_Transfer.ZIP
The initial copy hit rate (percent) URLDEV_Initial_Copy_Hit_xx.csv URLDEV_dat/URLDEV_Initial_Copy_Hit.ZIP
The average transfer rate (KB/sec) for
initial copy operations URLDEV_Initial_Copy_Transfer_xx.csv URLDEV_dat/URLDEV_Initial_Copy_Transfer.ZIP
Note: The letters "xx" in CSV filenames indicate a CU image number. For example, if the filename is
URLDEV_Read_Record_10.csv
, the file contains the number of read I/Os (per second) of the volumes controlled
by the CU whose image number is 10.
Causes of Invalid Monitoring Data
If the value of monitoring data in CSV files is less than 0 (zero), consider the following causes:
Probable causes Invalid values of monitoring
data
The value (-1) indicates that Performance Monitor failed to obtain monitoring data.
Probable reasons are: The monitoring data in the CSV
file includes (-1).
• Performance Monitor attempted to obtain statistics when an operation for rebooting
the disk array is in progress.
•
Performance Monitor attempted to obtain statistics when a heavy workload is
imposed on the disk array.
• There is no volume in a parity group.
•
Just after the CUs to be monitored were added, the Export Tool failed to save files
that contain monitoring data for all volumes or journal volumes used by remote
copy software (for example, Continuous Access Synchronous, Continuous Access
Synchronous Z, Continuous Access Journal, or Continuous Access Journal Z). For
details about the files, see
Table 21 (page 127) , Table 24 (page 130) ,
and Table 25 (page 130) .
•
If Disable is selected to stop monitoring in the Monitoring Switch field on the
Monitoring Options window and longrange is specified as the gathering interval,
the monitoring data for the period when Performance Monitor stops monitoring
is (-1).
•
If you added the CU during monitoring, specified longrange as the gathering
interval, and collected monitoring data, the value (-1) is displayed as the monitoring
data before the CU was added.
• If the CU number is not the monitoring target object, Performance Monitor cannot
obtain monitoring data from the CU. However, when the RemoteCopy,
UniversalReplicator, or URJNL operand is specified for the group subcommand,
the value (-1) is not displayed as the monitoring data even if the CU number is
not the monitoring target object. In that case, data on the monitored CU is added
up and output into the CSV file.
•
If no CU is specified as monitoring target, the value (-1) is displayed as the
monitoring data.
The value (-3) indicates that Performance Monitor failed to obtain monitoring data
for the following reason: The monitoring data in the CSV
file includes (-3).
If IOPS is 0 (zero), the Response Time that is included in the monitoring data for LUs,
LDEVs, ports, WWNs, or external volumes is (-3). Because IOPS is 0 (zero), the
average response time becomes invalid.
The value (-4) indicates that Performance Monitor failed to obtain monitoring data
for the following reason: The monitoring data in the CSV
file includes (-4).
132 Export Tool