The configuration editor is a tool to let you make changes to the configuration database. As described earlier, it has both a command line and a DECwindows Motif interface.
Console Manager does not allow multiple users to edit the configuration database at the same time. For users with privilege to modify the configuration database, the first user to run the configuration editor is allowed to modify the database. Any user who runs the editor while the first user is still editing the database will have read-only access to the database.
If a user is already editing the configuration database when you run the configuration editor, the following messages are displayed:
Database currently locked by another user No access to modify database, Read-Only mode enabled
To be able to modify the configuration database, you must exit the configuration editor, and restart it when no other user is modifying the database.
If you are running Console Manager on more than one node in a OpenVMS Cluster, then only one, cluster-wide instance of the configuration editor can modify the configuration database. This is the case even if two different instances of the database are being edited. The first privileged user to run the configuration editor in the cluster will be the one who can modify the configuration database.
When you invoke the configuration editor, the configuration database file is read. If the configuration database file does not exist in the default directory, the editor automatically creates a configuration database with default characteristics for you. Any updated characteristics are saved as the new configuration database file when you exit the editor.
To use a configuration database file created with a different name, you must rename it to the default configuration database file name, and reconfigure Console Manager.
We recommend that you:
|
Copyright © 2010 CA.
All rights reserved.
|
|