Unanswered: Set unsupported environment vars for db2 processes ?
I have two similar db2 v8 instances, instance owner shell is csh. One of these systems has some problems - and I noticed that environments for db2 processes are different. I took db2agent process as an example and printed environment using AIX command:
ps eww somepid
And yes the output was different - one instance had additional variables.
According to IBM if I want to set unsupported environment variable:
To set variables that are not supported by DB2 UDB, define them in your script files, userprofile and usercshrc.
So I included missing variables into usercshrc, like:
setenv varname varvalue
After that I restarted problematic instance and checked again using "ps eww pid" - there was no aditional variables I included in usercshrc !
What am I doing wrong ? How to add additional environment variables to db2 processes(db2agent for example) ?
.login .profile .cshrc sqllib/usercshrc sqllib/userprofile - all these files are the same(according to instance).
One instance db2 processes have enviroment vars contained into usercshrc, while other instance processes don't - even usercshrc contains the same vars.
Maybe one instance is configured NOT to read usercshrc somehow ?