DB2 FOR LUW / DB2FORLUW / 970 - 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:                                              * 
* Users running rah or db2_all commands using ";"              * 
* prefixsequence, i.e running the commands in parallel in      * 
* thebackground in non-Linux DB2 Enterprise Server             * 
* Editionplatforms.                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* running rah or db2_all commands using ";" prefix             * 
* sequence,i.erunning the commands in parallel in the          * 
* background, willreturnthe error "ksh: +1:  not found.". This * 
* issue only occurs toDB2 Enterprise Server Edition on         * 
* non-Linux platforms.For example:$ db2_all ";date"rah:        * 
* primary monitoring process for date is 893000rah: waiting    * 
* for 966708, host1:dateksh: +1:  not found.                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* 1) Try not to use ";" prefix sequence in rah or              * 
* db2_allcommands.2) Modify the rah script and change the line * 
* 676 from "$*)"to "*)" as below.672 case ${OSN?} in673        * 
* ${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 runningtheshell command "which rah", normally it should   * 
* be in thedirectory <db2 instance home>/sqllib/bin.           * 
****************************************************************

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.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 9.7 Fix Pack 2

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC75400 
follow-up : 

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

12.01.2010
31.05.2010
31.05.2010

9.7.FP2