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

the stored data. You can specify both the short-range and long-range subcommands
at the same time. The difference between these subcommands is as follows:
◦ The short-range subcommand is valid for monitoring data in short range. You can
use this subcommand to narrow the export-target term for all the monitoring items you
can specify by the group subcommand.
Specify a term within "Short Range From XXX To XXX" which is output by the show
subcommand.
◦ The long-range subcommand is valid for monitoring data in long range. You can use
this subcommand only when you specify the PhyPG, PhyLDEV, PhyProc, or PhyESW
operand with the Long option in the group subcommand. (The items that can be saved
by these operands are the monitoring data displayed in the Physical tab of the Performance
Management window with selecting longrange.)
Specify a term within "Long Range From XXX To XXX" which is output by the show
subcommand.
In the sample file in (page 88) , the script short-range 201210010850:201210010910
specifies the term 8:50-9:10 on Oct. 1, 2012. This script is applied to the group RemoteCopy
subcommand in this example. When you run the Export Tool, it will export the statistics about
remote copy operations by Continuous Access Synchronous and Continuous Access
Synchronous Z in the term specified by the short-range subcommand.
Also, in
(page 88) , the script long-range 201209301430:201210011430 specifies the
term from Sep. 30, 2012, 14:30 to Oct. 1, 2012, 14:30. This script is applied to the group
PhyPG Long
subcommand in this example. When you run the Export Tool, it will export the
usage statistics about parity groups in the term specified by the long-range subcommand.
If you run the Export Tool without specifying the short-range or long-range subcommand,
the monitoring data in the whole storing period (data in the period displayed by the show
subcommand) will be exported.
◦ For detailed information about the short-range subcommand, see (page 109) .
◦ For detailed information about the long-range subcommand, see (page 111) .
•
outpath out
This script specifies that files should be saved in the directory named out in the current
directory.
The outpath subcommand specifies the directory in which files should be saved. For detailed
information about the outpath subcommand, see
(page 113) .
•
option compress
This script specifies that the Export Tool should compress monitoring data in ZIP files.
The option subcommand specifies whether to save files in ZIP format or in CSV format. For
detailed information about the option subcommand, see
(page 113) .
•
apply
The apply subcommand saves monitoring data in files. For detailed information about the
apply
command, see (page 114) .
When you install the Export Tool, the command.txt file is stored in the installation directory. This
file contains sample scripts for your command file. It is recommended that you customize scripts
in command.txt according to your needs. For details about subcommand syntax, see
(page 95) .
Preparing a batch file
A batch file is used to run the Export Tool. The Export Tool starts and saves monitoring data in files
when you execute the batch file.
90 Export Tool