HP StorageWorks Storage System Scripting Utility reference (September 2005)

2nd bad ASQ: 0
ss1> exer stop
Examples
exercise_disk start "\Disk Groups\Default Disk Group\Disk 002,
\Disk Groups\Default Disk Group\Disk 004"
This example ex
ercises Disk 002 and Disk 004.
exercise_disk start all
This example exercises all disks.
EXIT
The EXIT command terminates the utility session.
If the utility is accepting input from the terminal or the command line, EXIT c auses the program to terminate.
If the utility is processing a script from a file while encountering a FILE command, the behavior of the EXIT
command depends on how the FILE command was issued:
• If the FILE command was issued from the command line, an EXIT command in the file causes
the utility to terminate.
• If the FILE command was issued from the terminal, an EXIT command in the file causes the utility to
return to accepting input from the terminal.
• If a file is currently executing as a result of a nother FILE command, an EXIT command in that file
returns control to the previous file. The utility does not run any commands in a script beyond the
EXIT command. EXIT causes an immediate return to the “calling” layer.
Syntax
EXIT
Example
EXIT
The utility terminates.
FILE
The FILE comm and causes the current mode of input to be suspended and redirects the scripting utility to
accept input from the specified file. Either the end of the file or an EXIT command in the specified file
causes the
utility to again accept input from the previous input source.
FILE comma
nds can be nested. Nesting FILE commands means that a filebeingexecutedthroughaFILE
command can have FILE @commands within its command set. The only limitation on how deep FILE
commands may be nested is based on the host array’s resources.
Syntax
FILE <filename>
An extension is not required by the utility, although you can choose one appropriate to your environment.
Examples
FILE snapd1.txt
HP StorageWorks Storage System Scripting Utilit y reference
49