IBM System Storage DS3000 Programming Manual page 25

Table 1-2. Command Line Terminals (continued)
Terminal
-o
-p
-q
-quick
Definition
Specifies a file name for all output text that is a result of
running the script commands when you use this terminal
with the -c terminal or the -f terminal. If you do not specify
an output file, the output text goes to standard output
(stdout). All output from commands that are not script
commands is sent to stdout, regardless of whether this
terminal is set.
Specifies the password for the storage subsystem on which
you want to run commands. A password is not necessary
under these conditions:
v A password has not been set on the storage subsystem.
v The password is specified in a script file that you are
running.
v You specify the password by using the -c terminal and the
set session password= password command.
Specifies the frequency that you want to include additional
profile or support bundle information in the email alert
notifications. An email alert notification containing at least the
basic event information is always generated for every critical
event. If you set the -I terminal to eventOnly, the only valid
value for the -q terminal is everyEvent. If you set the -I
terminal to either the profile value or the supportBundle
value, this information is included with the emails with the
frequency specified by the -q terminal. These values are valid
frequency values:
everyEvent – Information is returned with every email
v
alert notification.
2 – Information is returned no more than once every two
v
hours.
4 – Information is returned no more than once every four
v
hours.
8 – Information is returned no more than once every eight
v
hours.
12 – Information is returned no more than once every 12
v
hours.
24 – Information is returned no more than once every 24
v
hours.
Reduces the amount of time that is required to run a
single-line operation. An example of a single-line operation is
the re-create FlashCopy LogicalDrive command. This
terminal reduces time by not running background processes
for the duration of the command.
Do not use this terminal for operations that involve more than
one single-line operation. Extensive use of this command can
overrun the controller with more commands than the
controller can process, which causes operational failure. Also,
status updates and configuration updates that are collected
usually from background processes will not be available to the
CLI. This terminal causes operations that depend on
background information to fail.
Chapter 1. About the Command Line Interface
1-5