Tuxedo 6.5.3 TUXCONFIG Incompatibility Issue

The GROUPS section of the TUXCONFIG file was changed in a way that created an incompatability
between Releases R6.5 V1 and R6.5 V2. This situation is reported in case number 10-0009290-2837.
A new field was incorrectly added to the GROUPS section in R6.5 V2 to support a future enhancement.
The new field causes an R6.5 V1 TUXCONFIG file to be unusable with an R6.5 V2 executable and vice
versa. The new field has been retained in R6.5 V3 and will be retained in any subsequent R6.5 releases.
This means that an R6.5 V1 TUXCONFIG file cannot be used with future R6.5 releases. When
upgrading from R6.5 V1 to another version of R6.5, you must reload the TUXCONFIG file after the new
NonStop™ TUXEDO executables have been installed. Likewise, if you must fall back to R6.5 V1, the
TUXCONFIG file must be reloaded after the R6.5 V1 executables have been reinstated.
The symptoms of the problem appear only when the user attempts to start a server contained in a
GROUP that is not the first GROUP in the TUXCONFIG file. When that happens, either tmboot or the
server will issue the following userlog message:
LIBTUX_CAT:665:ERROR:Invalid server group name - <GROUP NAME>.
Under normal circumstances, the routines used to read the TUXCONFIG file are used from the /T SRL.
That means changing from an R6.5 V1 SRL to another R6.5 version of the SRL requires the
TUXCONFIG file to be reloaded. However, clients and servers can also be statically linked, which
causes the routines to be bound to the executable. Therefore, if any of the clients or servers have been
statically linked, they must be rebuilt with the correct version of the NonStop™ TUXEDO libraries
before they can be used with the updated TUXCONFIG file.
Untitled Document
file:///C|/READMEs TUXEDO/Release 6.5 V3 white/TUXCONFIG_Incompatibility.html [7/1/2004 1:51:10 PM]