When RMS starts, it reads the values of environment variables from hvenv and hvenv.local and initializes the ENV and ENVL objects respectively. To change the values of environment variables before RMS starts up, you need to specify them in the hvenv.local file. RMS provides an extended set of environment variables when it executes a script for a controlled application. Like the general set of script execution variables, this extended set exists only while the script is being processed, but the context is even more specialized.
These settings will be overridden at installation.
Note
The RMS error may occur if the /tmp directory is nearly full because hvenv uses it to sort the RMS environment variables.
To change the global environment variables, you must make the same adjustment to hvenv.local on all the nodes in the cluster. After stopping RMS on all the nodes, you will have to restart RMS for the change to take effect.
Note
Do not explicitly set RMS environment variables in the user environment. Doing so can cause RMS to lose environment variables settings.
The values of environment variables are specified as export directives in each file. A typical export directive would appear as follows:
export SCRIPTS_TIME_OUT=200
Therefore, any changes you make to hvenv.local file will not take effect until the next time RMS starts up. While RMS is running, you can display the environment variables with the following commands:
hvdisp ENV
hvdisp ENVL
