Hello all: Justin's approach to use db2profile works great if you are setting up a user account. But for programs that run as cron (say on the DB host as user db2inst1), it may not work. The program won't always inherit the proper environment because cron doesn't invoke the user's startup scripts, unless you explicitly do so in your command invocation. There there are programs initiated through a web server (CGI and such). We often set up our webserver account as a non-login account with no home directory, which means db2profile has no place to set up its stuff and there is not profile or login environment.
In practice, we use both approaches here: db2profile for user accounts and explicit environment setup for automation tools. Stph
