You can specify rah command from the
command line as the parameter, or in response to the prompt if you
do not specify any parameter.
Use the prompt method if the command contains the following special
characters:
| & ; < > ( ) { } [ ] unsubstituted $
If you specify the command as the parameter on the command line,
you must enclose it in double quotation marks if it contains any of
the special characters just listed.
Note: On Linux and UNIX operating
systems, the command is added to your command history just as if you
typed it at the prompt.
All special characters in the command can be entered normally (without
being enclosed in quotation marks, except for \). If you require a
\ in your command, you must type two backslashes (\\).
Note: On Linux and UNIX operating systems, if you are not using
a Korn shell, all special characters in the command can be entered
normally (without being enclosed in quotation marks, except for ",
\, unsubstituted $, and the single quotation mark (')). If you require
one of these characters in your command, you must precede them by
three backslashes (\\\). For example, if you require a \ in your command,
you must type four backslashes (\\\\).
If you require a double quotation mark (") in your command, you
must precede it by three backslashes, for example, \\\".
Note: - On Linux and UNIX operating systems, you cannot include a
single quotation mark (') in your command unless your command shell
provides some way of entering a single quotation mark inside a singly
quoted string.
- On Windows, you cannot
include a single quotation mark (') in your command unless your command
window provides some way of entering a single quotation mark inside
a singly quoted string.
When you run any korn-shell shell-script that contains logic to
read from stdin in the background, explicitly redirect stdin to a
source where the process can read without getting stopped on the terminal
(SIGTTIN message). To redirect stdin, you can run a script with the
following form:
shell_script </dev/null &
if there is no input to be supplied.
In a similar way, always specify </dev/null when
running db2_all in the background. For example:
db2_all ";run_this_command" </dev/null &
By doing this you can redirect stdin and avoid getting stopped
on the terminal.
An alternative to this method, when you are not concerned about output
from the remote command, is to use the "daemonize" option in
the db2_all prefix:
db2_all ";daemonize_this_command" &
DB2 10.5 for Linux, UNIX, and Windows