
Operand
Window of
Performance
Monitor
Monitoring Data
Saved in the File
Saved ZIP File
See
Universal-
Replicator
Statistics about
remote copy
operations by
Continuous Access
Journal and
Universal Replicator
for Mainframe (in
the whole storage
system)
UniversalReplica-
tor.ZIP
Table 23 on page 85.
URJNL
Continuous
Access Journal
Monitor
window and
Universal
Statistics about
remote copy
operations by
Continuous Access
Journal and
Universal Replicator
for Mainframe (at
journal groups)
URJNL_dat.ZIP Table 24 on page 86.
URLU
Replicator for
Mainframe
Monitor
window
Statist
ics about
remote c
opy
operat
ions by
Contin
uous Access
Journa
land
Unive
rsal Replicator
for Ma
inframe (at
LU pat
hs)
URLU_dat.ZIP Table 25 on page 87.
URLDEV
Statistics about
remote copy
operations by
Continuous Access
Journal and
Universal Replicator
for Mainframe (at
volumes controlled
by a particular CU)
URLDEV_XXXXX.ZIP
(*4)
Table 26 on page 87.
*1: When you specify the PhyPG, PhyLDEV, PhyProc,or PhyCSW operand, you can select the storing
period of the monitoring data to be exported from short range or long range. When you specify other
operands, the monitoring data in short range is exported.
*2: A ZIP file whose name is beginning with LDEV_.
*3: A ZIP file whose name is beginning with RCLDEV_.
*4: A ZIP file whose name is beginning with URLDEV_.
You can use the group subcommand more than one time in a command file. For example, you can
write the following script:
grou
p PortWWN CL1-A:CL1-B
group PPCG spmg01:spmg02
group RemoteCopy
If an operand is used more than one time in a command file, the last operand takes effect. In the example
below, the first group subcommand does not take effect, but the second group subcommand takes effect:
group PortWWN CL1-A:CL1-B
gr
oup PortWWN CL2-A:CL2-B
104
Using the Export Tool
Commenti su questo manuale