Managing multi-version capable releases
One significant change to consider when dealing with multi-version capable releases, is how the installed releases are integrated with each other. There are certain objects that can only exist once on a partition. The multi-version capable releases are designed to recognize this and accommodate this as part of their installation. Whenever a more recent multi-version capable release is installed, its commands, panel groups, and message files are copied to QSYS and QNOTES. When these commands are used on the system in an interactive session or a batch program, the primary release version of the commands are used.

Other commands can be used against any release, no matter which release the command originated from. For example, the command ENDDOMSVR SERVER(*ALL) will end all active servers on the partition that are currently running. It does not matter which release of Domino the servers are configured to use, or which release of Domino defined the command.

Note Even when a library qualified use of this command is entered, all currently active servers on that partition are ended, no matter which release they are configured to use. For example, on a server with Domino 6.5.3 and 7.0 installed, the following command would still end all active servers:


The following subsections detail how different commands work in a multi-version capable environment. There are also details on a new command, UPDDOMSVR.


Issuing the WRKDOMSVR command displays all configured Domino servers on a particular partition, regardless of which release a server is configured to use.

To display a server's configured release library and Domino release level, press F11 from the main display for the WRKDOMSVR command.

If any server is configured to use a specific release of Domino that is not installed, the server's status will show *UNAVAIL.

All functions of the WRKDOMSVR display are supported and all can be used against any server displayed.

Note There are two exceptions. You cannot start or change a Domino server with a status of *UNAVAIL. Attempting to start it will fail with message LNT0218, and attempting to change it will fail with message LNT0215.

The following shows a sample of the WRKDOMSVR display after pressing F11.


When multiple releases of Domino are installed on one partition, new Domino servers can be configured to use any of the installed releases of Domino. The CFGDOMSVR command is one that can be library qualified and run against specific releases.

If you use CFGDOMSVR without library qualifying it, it will use the primary release of Domino installed. For example, if you have both Domino 6.5.0 and 7.0 installed, the following command will only create servers that are configured to use 7.0:

If you library qualify the CFGDOMSVR command, you can configure a server to use any installed Domino release. For example, to configure a Domino 6.5.0 server in the above environment, you would use the following command:
Using the *REMOVE option in any multi-version capable release can be used to remove any configured Domino server. Therefore, if the specific release that a Domino server is configured to use is no longer installed, you can still remove that server using the following command:

The CHGDOMSVR command is used to change the configuration of existing Domino servers. You can use this command on any server, from any installed library. This command detects the release of the server you specify and displays the appropriate parameter options for that server's release. This means that you must have that server's release currently installed on your partition for this command to work properly. If a server's release is not installed, and you try to change its configuration, you will receive the error message LNT0218. You can either update your server to an installed release, using the UPDDOMSVR command, or install the appropriate release for that server.


The UPDDOMSVR command allows you to update specific Domino servers to newer releases. You can update all servers, or select specific servers, allowing you to control which servers are configured for specific Domino releases.

Prior to releases 6.0.3/6.5, servers were automatically upgraded during the product installation process. However, this process no longer occurs during installation. With any multi-version capable release, you must run the UPDDOMSVR command after installation in order to update that server to a newer release.

Note You must end the Domino server before attempting to update it.

Do not library-qualify the UPDDOMSVR command. This ensures that the command associated with the primary release, which contains the most current version information, is used to update the Domino server.

You can only update a Domino server to a release that is currently installed on your partition. Updating a Domino server to a previous release is not supported.

For more information on the UPDDOMSVR command, see Appendix B "Using CL Commands With Domino for System i."