Chapter 8. Command-line interface and Script Editor
503
Execute Only
To run this option, select the Tools
Execute Only option. The Script Editor engine
executes a script. It displays an error message if a syntax error is encountered.
If an execution error occurs, the script might or might not continue to execute depending
on the included On Error script statement. The On Error Stop statement stops the script if
an execution error is encountered. The On Error Continue statement allows the script to
continue even after an execution error is encountered. (This is the default.)
Interpreting the script execution results
During script execution, messages are displayed in the output view, beginning with:
Executing script...
After a successful script execution, you see the message:
Script execution complete.
If there is an error during the parse phase, an error indication is displayed in the Output View,
giving the line and column number and a description of the syntax error.
If there is an error during execution, a message is displayed in the Output View stating that
the command failed and reporting a description of the error.
8.2.2 Embedding commands in batch files
Due to the business demand for higher availability of data, the time window allocated to make
backups is shrinking. Customers can no longer afford the daily downtime on their production
server to perform backups. This becomes especially true as databases become larger and
larger. Online backups improve the availability of the database, but cost CPU, disk, and
network resources. Even with the use of incremental and differential backups, the time
necessary to perform a backup can be significant.
On the other hand, a feature such FlashCopy enables customers to perform offline backups
by creating a point in time copy of a logical device, which can then be presented to a host and
backed up. A script can be written, such as the example in Example 8-8 on page 496, which
will execute a FlashCopy procedure from the host at a chosen time of day using UNIX “cron”
scheduling, for example. Thus, CLI and scripting can become an important tool in managing
the DS5000 and host operations.
Note: Certain execution errors, including the inability to communicate with the storage
subsystem, always cause the script execution to halt. In these cases, execution stops even
if you have used the On Error Continue statement.
Summary of Contents for System Storage DS4000
Page 2: ......
Page 18: ...xvi IBM Midrange System Storage Hardware Guide...
Page 40: ...22 IBM Midrange System Storage Hardware Guide...
Page 302: ...284 IBM Midrange System Storage Hardware Guide...
Page 344: ...326 IBM Midrange System Storage Hardware Guide...
Page 372: ...354 IBM Midrange System Storage Hardware Guide Figure 7 25 Drive firmware Incompatible...
Page 490: ...472 IBM Midrange System Storage Hardware Guide...
Page 522: ...504 IBM Midrange System Storage Hardware Guide...
Page 544: ...526 IBM Midrange System Storage Hardware Guide...
Page 561: ...Index 543 Z zoning 129 130...
Page 562: ...544 IBM Midrange System Storage Hardware Guide...
Page 564: ...IBM Midrange System Storage Hardware Guide IBM Midrange System Storage Hardware Guide...
Page 565: ......