Code: Select all
Environment:
Some cluster members have similar names; each has its own system disk.
(Cluster software is used for disk sharing, and little else.) Same VMS
and TCPIP software everyplace:
IT $ tcpip show version
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 5
on an HP zx2000 (1.50GHz/6.0MB) running OpenVMS V8.4-2L3
ITS $ tcpip show version
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 5
on an HP rx2600 (1.50GHz/6.0MB) running OpenVMS V8.4-2L3
ITX $ tcpip show version
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 5
on an HP rx2660 (1.59GHz/9.0MB) running OpenVMS V8.4-2L3
REX $ tcpip show version
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 5
on an HP rx2600 (1.50GHz/6.0MB) running OpenVMS V8.4-2L3
Apparently, "tcpip start mail" on node IT destroys SMTP queues on
_all_ nodes named "IT*" (_not_ only queues with "_IT_" in their names),
and then recreates them for only node IT.
This occurs, for example, when node IT is started.
Demonstration (with explicit "tcpip start mail" command on node IT):
IT $ show queue tcpip$smtp_it*
Server queue TCPIP$SMTP_ITS_1, idle, on ITS::, mounted form DEFAULT
Server queue TCPIP$SMTP_ITX_1, idle, on ITX::, mounted form DEFAULT
Server queue TCPIP$SMTP_IT_1, idle, on IT::, mounted form DEFAULT
IT $ tcpip start mail
IT $ show queue tcpip$smtp_it*
Server queue TCPIP$SMTP_IT_1, idle, on IT::, mounted form DEFAULT
A "tcpip start mail" command on a differently named (non-substring)
node (ITS, ITX, or REX, for example) caused no such problems.
Knowing nothing (except the observed behavior), my guess would be
that "TCPIP START MAIL" first deletes all the old stuff it can find, and
then creates the desired new stuff. And the problem is that the
difference between "_<node>*" and "_<node>_*" is causing it to find and
delete too much old stuff, _if_ you use an unlucky set of node names.