HP XP Array Manager Software - Manual (Page 91)

Specify a term within Short Range From XXX To XXX which is output by the show
subcommand.
• The longrange subcommand is valid for monitoring data in long range. You can use this
subcommand only when you specify the PhyPG, PhyLDEV, PhyProc, or PhyCSW 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 Auto LUN window
with selecting longrange.)
Specify a term within Long Range From XXX To XXX which is output by the show
subcommand.
In Figure 38 on page 89, the script shortrange 200610010850:200610010910 specifies
the term 8:50-9:10 on Oct. 1, 2006. 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 and TrueCopy for Mainframe in the term specified
by the shortrange subcommand.
Also, in Figure 38 on page 89, the script longrange 200609301430:200610011430
specifies the term from Sep. 30, 2006, 14:30 to Oct. 1, 2006, 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 longrange subcommand.
If you run the Export Tool without specifying the shortrange or longrange 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 shortrange subcommand, see
“ shortrange Subcommand ” on page 112.
For detailed information about the longrange subcommand, see
“ longrange Subcommand ” on page 114.
• 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 “ outpath Subcommand ” on page 116.
• 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 “ option Subcommand ” on page 117.
.
• apply
The apply subcommand saves monitoring data in files. For detailed information about the
apply command, see “ apply Subcommand ” on page 117.
When you install the Export Tool, the file command.txt will be stored in the export directory. The
command.txt file contains sample scripts for your command file. It is recommended that you customize
scripts in command.txt according to your needs. For detailed information about subcommand syntax, see
“ Command Reference ” on page 96.
Preparing a Batch File
To run the Export Tool, you need a batch file. The Export Tool starts and saves monitoring data in
files when you execute the batch file.
The installation directory for the Export Tool (that is, the export directory) contains two batch files:
runWin.bat and runUnix.bat. If your computer runs Windows, use runWin.bat. If your computer runs
UNIX, use runUnix.bat.
Figure 39 on page 92 illustrates scripts in runWin.bat and runUnix.bat. These batch files include a
command line that executes a java command. When you execute your batch file, the java command
executes subcommands specified in your command file and then saves monitoring data in files.
XP24000 Performance Monitor User's Guide 91