Controlling the rah command
This topic lists the environment variables to control the rah command.
Name | Meaning | Default |
---|---|---|
$RAHBUFDIR Note: Available
on Linux® and UNIX operating systems only.
|
Directory for buffer | /tmp/$USER |
$RAHBUFNAME Note: Available
on Linux and UNIX operating systems only.
|
File name for buffer | rahout |
$RAHOSTFILE (on Linux and UNIX operating systems); RAHOSTFILE (on Windows operating systems) | File containing list of hosts | db2nodes.cfg |
$RAHOSTLIST (on Linux and UNIX operating systems); RAHOSTLIST (on Windows operating systems) | List of hosts as a string | extracted from $RAHOSTFILE |
$RAHCHECKBUF Note: Available
on Linux and UNIX operating systems only.
|
If set to "no", bypass checks | not set |
$RAHSLEEPTIME (on Linux and UNIX operating systems); RAHSLEEPTIME (on Windows operating systems) | Time in seconds this script waits for initial output from commands run in parallel. | 86400 seconds for db2_kill, 200 seconds for all others |
$RAHWAITTIME (on Linux and UNIX operating systems); RAHWAITTIME (on Windows operating systems) | On Windows operating
systems, interval in seconds between successive checks that remote
jobs are still running. On Linux and UNIX operating systems, interval
in seconds between successive checks that remote jobs are still running
and On
all operating systems, specify any positive integer. Prefix value
with a leading zero to suppress messages, for example, It is not necessary to specify a low value as rah does not rely on these checks to detect job completion. |
45 seconds |
$RAHENV Note: Available
on Linux and UNIX operating systems only.
|
Specifies file name to be executed if $RAHDOTFILES=E or K or PE or B | $ENV |
$RAHUSER (on Linux and UNIX operating systems); RAHUSER (on Windows operating systems) | On Linux and UNIX operating systems, user ID
under which the remote command is to be run. On Windows operating systems, the logon account associated with the Db2® Remote Command Service |
$USER |
Note: On Linux and UNIX operating systems, the value
of $RAHENV where rah is run
is used, not the value (if any) set by the remote shell.