Configuration: Mixed platform Clusters

On the VAX nodes, the TCPWARE_LOGICALS.COM file would look something like this:

$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON -
       SYS$COMMON:,ALPHA$DKA300:[VMS$COMMON.]
$ !
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC -
       SYS$SPECIFIC:
$ !
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT -
       SYS$SYSROOT:,ALPHA$DKA300:[VMS$COMMON.]
$ !
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE  -
       "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE -
       "TCPWARE_ROOT:[TCPWARE.INCLUDE]"

On the Alpha nodes, the TCPWARE_LOGICALS.COM file would look something like this (this is the "normal" one):

$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON       SYS$COMMON:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC     SYS$SPECIFIC:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT         SYS$SYSROOT:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE              "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE   "TCPWARE_ROOT:[TCPWARE.INCLUDE]"

The common files reside on Alpha's system disk (ALPHA$DKA300:[VMS$COMMON.TCPWARE...).

Keep in mind the following:

1) When installing a new version, "restore" the logicals to their original values on the VAX's when doing the installation.

2) After installing, DELETE (or rename) the SYS$SYSROOT:[TCPWARE...]*_CONTROL.COM files on the VAX systems. If this isn't done, TCPware will fail to start because it will find two sets of all the control files and will try to execute them twice which will cause problems.

3) After installing, clean up any of the data files that TCPware creates during installation if it doesn't find them (since it won't find them since the logical no longer points to include them). This is on the VAX system.

4) Restore the TCPWARE_LOGICALS.COM to that shown above for the VAX.