Here are suggestions on how to handle some problems that you may encounter when you are running rah:
This problem may be caused because:
Either one of the machines does not have the ID running rah correctly defined in its .hosts file, or the ID running rah does not have one of the machines correctly defined in its .rhosts file.
The ID running rah does not have one of the machines correctly defined in its .rhosts file.
rsh somewher -l $USER db2_killrah never completes.
This is normal. rah starts background monitoring processes, which continue to run after it has exited. Those processes will normally persist until all processes associated with the command you ran have themselves terminated. In the case of db2_kill, this means termination of all database managers. You can terminate the monitoring processes by finding the process whose command is rahwait>or and kill <process_id>. Do not specify a signal number. Instead, use the default (15).
This is because multiple concurrent executions of rah are trying to use the same buffer file (for example, $RAHBUFDIR/$RAHBUFNAME) for buffering the outputs. To prevent this problem, use a different $RAHBUFNAME for each concurrent rah command, for example in the following ksh:
export RAHBUFNAME=rahout rah ";$command_1" & export RAHBUFNAME=rah2out rah ";$command_2" &
or use a method that makes the shell choose a unique name automatically such as:
RAHBUFNAME=rahout.$$ db2_all "....."
Whatever method you use, you must ensure you clean up the buffer files at some point if disk space is limited. rah does not erase a buffer file at the end of execution, although it will erase and then re-use an existing file the next time you specify the same buffer file.
rah '"print from ()'
and received the message:
ksh: syntax error at line 1 : `(' unexpected
Prerequisites for the substitution of () and ## are:
For a performance tip when running commands in parallel, use | rather than |&, and use || rather than ||& or ; unless you truly need the function provided by &. Specifying & requires more rsh commands and therefore degrades performance.
[ DB2 List of Books | Search the DB2 Books ]