Log Files; Error Handling - HPE XP7 User Manual

java -classpath "./lib/JSanExportLoader.jar"
-Del.tool.Xmx=536870912 -Dmd.command=command.txt
-Dmd.logpath=log sanproject.getexptool.RJElMain<CR+LF>
if %errorlevel%==1 echo THE SET SUBCOMMAND FAILED<CR+LF>
if %errorlevel%==3 echo THE SET SUBCOMMAND FAILED<CR+LF>
pause<CR+LF>
In the previous script, <CR+LF> indicates the end of a command line.

Log files

When Export Tool runs, it creates a log file on your computer. Therefore, if you run Export Tool
repeatedly, the size of free space on your computer will be reduced. To secure free space on
your computer, it is important that you delete log files regularly. For information about the directory
containing log files, see
Export Tool returns a termination code when Export Tool finishes as listed in the following table:
Table 2 Termination codes returned by Export Tool
Termination code
0
1
2
3
4
101

Error handling

When an internal error occurs during export processing, an exclamation mark (!) indicates the
error. By default, Export Tool makes up to three more attempts at processing. You can change
the maximum number of retries by using the retry subcommand. For detailed information about
the retry subcommand, see
If export processing does not finish within three retries or if an internal error occurs other than
those listed in the following table, Export Tool stops. If Export Tool stops, quit the command
prompt, and then run the tool again.
For more information, see
Errors returned by Export Tool
Error message ID
0001 4001
0001 5400
0001 5508
"Java" (page 82).
Description
Export Tool finished successfully.
An error occurred when the set subcommand (see
attempt to switch to Modify mode failed. Some other user might have been logged on in
Modify mode.
One of the following two errors occurred:
A command file has been corrupted or could not be read.
An error occurred when a command was parsed.
An error occurred due to more than one reason. For example, an attempt to switch to
Modify mode failed when the set subcommand (see
user might have been logged on in Modify mode.
The Storage Administrator (Performance Management) role is not assigned to the user
ID.
An error occurred during the preparation process for running Export Tool. For details on
the error, see the displayed message and the table in
(page 101).
"retry" (page
"Troubleshooting Export Tool" (page
Description
An error occurred during the SVP processing.
Because the SVP is busy, the monitoring data cannot be obtained.
An administrator is changing a system environment file.
"set" (page
"set" (page
62).
100).
80)) is run, because an
80)) is run. Some other
"Messages issued by Export Tool"
Using Export Tool 59