DB2 FOR LUW / DB2FORLUW / B10 - DB2

There is a small bug in `db2profile`. Basically in the
`AddRemoveString` function, all other variables are unset except
 for "action", causing `$action` to leak out and wreak havoc on
users' script, which probably defined another `action` variable
locally.
----------------------------------------------------------------
---------
AddRemoveString()
{
...
addrm_str=$2 #The new path to be used
action=$3 #Action: a -> add, r -> remove
if [ "X${action?}" != "Xa" -a "X${action?}" != "Xr" ]; then
return 0 # return without doing anything
fi
...
unset var addrm_str awkval newval
}

The problem is fixed on Db2 v11.1 Mod4 FP5.

Modify the last line to `unset var addrm_str action awkval
newval`:
$ diff db2profile.20180810 db2profile
113c113
<    unset var addrm_str awkval newval
---
>    unset var addrm_str action awkval newval

The problem is fixed on Db2 v11.1 Mod4 FP5.

Upgrade to Db2 v11.1 Mod4 FP5.

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

29.01.2022
29.01.2022
29.01.2022