DB2 FOR LUW / DB2FORLUW / 950 - DB2

running rah or db2_all commands using ";" prefix sequence, i.e 
running the commands in parallel in the background, will return 
the error "ksh: +1:  not found.". This issue only occurs to 
DB2 Enterise Server Edition on non-Linux platforms. 
 
For example: 
 
$ db2_all ";date" 
 
rah: primary monitoring process for date is 893000 
 
rah: waiting for 966708, host1:date 
 
ksh: +1:  not found.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR Descripton                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 FP8                                          * 
****************************************************************

1) Try not to use ";" prefix sequence in rah or db2_all 
commands. 
2) Modify the rah script and change the line 676 from "$*)" to 
"*)" as below. 
 
    672 case ${OSN?} in 
    673   ${OSLNX?}) 
    674     TAIL_CMD="tail --lines=" 
    675     ;; 
    676   *)    ####### used to be $*) ####### 
    677     TAIL_CMD="tail " 
    678     ;; 
    679 esac; 
 
 
Note that the rah script's location can be found by running the 
shell command "which rah", normally it should be in the 
directory <db2 instance home>/sqllib/bin.

DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

V9.5 FP8 should contain the fix.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

30.03.2011
30.06.2011
30.06.2011

9.5.FP8