Note
Do not change the hvenv configuration file. Changes to your configuration's environment variables should be confined to the hvenv.local file.
The values of environment variables are specified as export directives in the hvenv.local file. To adjust a variable's setting, you would open hvenv.local with a text editor of your choice and modify (or add) the appropriate line.
A typical export directive would appear as follows:
export SCRIPTS_TIME_OUT=200
When RMS starts, it reads the values of environment variables from hvenv and hvenv.local and initializes the ENV and ENVL objects respectively. No further reference is made to these two configuration files while RMS is running. Therefore, any changes you make to hvenv.local will not take effect until the next time RMS starts up.
Values in the ENVL (local) object override values in the ENV (global) object. If a global variable setting appears in the hvenv.local file, it will override the corresponding setting in the hvenv file. However, if you adjust a global variable in the hvenv.local file on one node, you must make the same adjustment to hvenv.local on every other node in the cluster. Global variable settings must agree clusterwide.
While RMS is running, you can display the environment variables with the hvdisp command, which does not require root privilege:
hvdisp ENV
hvdisp ENVL
