I'm connecting via Reflection X using OPENSSH. When I log in, the db2profile doesn't get ran automatically. I have to manually execute the db2profile after logging on. What has to be done to auto run the db2 profile when I log in with OPENSSH. To get it to work on a server we telnet into, we added these 2 lines to the .profile

ENV=.krcsh
export ENV

then we created a .krcsh file that executes the db2 profile. Don't ask me why this was done (before me and they're gone), but it worked. Either we're missing a piece that was done before, or something extra has to be done for OPENSSH. Any help would be appreciated.

Why don't you just add the db2profile invokation into ~/.profile?

I did. here's what I've been testing...

I added an echo statements to .profile

$ cat .profile
echo "running .profile...."

PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:.

export PATH

if [ -s "$MAIL" ] # This is at Shell startup. In normal
then echo "$MAILMSG" # operation, the Shell checks
fi # periodically.

# The following three lines have been added by UDB DB2.
. /home/db2inst1/sqllib/db2profile
ENV=.krcsh
export ENV

I added an echo statement to db2profile

DB2INSTANCE=db2inst1
export DB2INSTANCE
INSTHOME=/home/db2inst1
echo "running db2profile...."

If I log in as dasusr1 and switch to db2inst1:

$ whoami
dasusr1
$ su - db2inst1
db2inst1's Password:
running .profile....
running db2profile....
running db2profile....
$

This ran the db2 profile twice. I believe we're running the new environment variable .krcsh which also executes db2profile.

If we log on as db2inst1, we get nothing…

If I execute the .profile manually, I get:

$ . /.profile
TERM=vt320
running db2profile....
des084iimp1: /home/db2inst1#
(notice I never got the "running .profile" message??)

If I execute the db2profile manually, I get my prompt.

des084iimp1: /home/db2inst1/sqllib#. /home/db2inst1/sqllib/db2profile
running db2profile....
des084iimp1: /home/db2inst1/sqllib#


Seems like i'm not running .profile when I log on...

Have you added the sourcing of db2profile also in /.profile? This file resides in the root directory of the file system - but it seems like a very bad idea doing that. So why am I asking this? This is the file you are sourcing:
My guess is that you have to make sure you are using the correct files here...

which shell is being used for this userid : echo $SHELL
.profile is for ksh
.bash_profile for bash ....
and other

Bash also reads .profile if it is started as login shell.

$ echo $SHELL
/usr/bin/ksh

and .profile is invoking db2profile
# The following three lines have been added by UDB DB2.
. /home/db2inst1/sqllib/db2profile
ENV=.krcsh
export ENV