How do I change a UniVerse tuning parameter?

The current settings for the configurable parameters are stored in the uvconfig file, located in the UV account directory (/u2/uv). A command called uvregen uses the uvconfig file to create another file in the UV account directory named .uvconfig, which contains an encrypted version of the current configurable parameter settings. The .uvconfig file is used during the startup of UniVerse.

When you run the uvregen program, it does the following:

  • Verifies that the values in the uvconfig file are reasonable
  • Creates a new .uvconfig file in the UV account directory
  • Resets the master key if you are using encryption

To change configurable parameter values, you can edit the uvconfig file manually. When you change configurable parameter settings, you must save them in the uvconfig file. You must restart UniVerse for the new settings to take affect.

Make sure you understand the effect of any changes you make to the default values. A small change can have a significant impact on your system. It is impossible to document the impact of each of these parameters so that you can predict the effect of a value change. If you are not sure about how to change the value of any parameter, please consult with a UniVerse support specialist.

To change the value of a configurable parameter, complete the following steps:

Stop Eclipse services that rely on UniVerse (SYSTEM.ADMIN, JBoss):

Change the working directory to the UV account directory (make sure the UV account directory is in the current path).

cd /u2/uv

Make sure all users are logged out of UniVerse and stop all UV processes:


Press ESC
At the prompt, type:


Shut down UniVerse

bin/uv -admin -stop
Before making changes to a configuration file, always make a backup.

Edit the uvconfig file in the UV account directory using your preferred text editor (for example, vi):

vi uvconfig

When you’ve saved the changes, apply them by executing the UniVerse uvregen program:


Start up UniVerse:

bin/uv -admin -start

Start up any dependent services (SYSTEM.ADMIN, JBoss, etc.):