IBM Books

Quick Beginnings for DB2 Extended Enterprise Edition for UNIX

Controlling the rah Command

You can use the following environment variables to control the rah command.

Table 24.  
Name Meaning Default
$RAHBUFDIR directory for buffer /tmp/$USER
$RAHBUFNAME filename for buffer rahout
$RAHOSTFILE file containing list of hosts db2nodes.cfg
$RAHOSTLIST list of hosts as a string extracted from $RAHOSTFILE
$RAHCHECKBUF if set to "no", bypass checks not set
$RAHSLEEPTIME time in seconds this script will wait for initial output from commands run in parallel 86400 seconds for db2_kill, 200 seconds for all other
$RAHWAITTIME interval in seconds between successive checks that remote jobs are still running and rah: waiting for <pid> ... messages. Specify any positive integer. Prefix value with a leading zero to suppress messages, for example, export RAHWAITTIME=045.

It is not necessary to specify a low value as rah does not rely on these checks to detect job completion.

45 seconds
$RAHENV specifies filename to be executed if $RAHDOTFILES=E or K or PE or B $ENV
$RAHUSER user ID under which the remote command is to be run $USER
Note: The value of $RAHENV where rah is run is used, not the value (if any) set by the remote shell.


Following are the .files that are run if no prefix sequence is specified:

File named in $RAHENV (probably .kshrc)
Same as E
.profile followed by file named in $RAHENV (probably .kshrc)
Same as PE
None (or Neither)
Note:If your login shell is not a Korn shell, any dot files you specify to be executed will be executed in a Korn shell process, and so must conform to Korn shell syntax. So, for example, if your login shell is a C shell, to have your .cshrc environment set up for commands executed by rah, you should either create a Korn shell INSTHOME/.profile equivalent to your .cshrc and specify in your INSTHOME/.cshrc:
or you should create a Korn shell INSTHOME/.kshrc equivalent to your .cshrc and specify in your INSTHOME/.cshrc:
  setenv RAHENV INSTHOME/.kshrc
Also, it is essential that your .cshrc does not write to stdout if there is no tty (as when invoked by rsh). You can ensure this by enclosing any lines which write to stdout by, for example,
  if { tty -s } then echo "executed .cshrc";

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]