The only place we had problems was with NetWare - the native NetWare TCP/IP
code does not support DNS, and so all of those folks have to direct address -
we don't support the third party name resolution software for NetWare that is
available. Also, the few people that used 3270 had to change their host name,
but, overall, probably 95% of the customer base didn't even realize we had
moved.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Moving the server, transparently
Author:  INTERNET.OWNERAD at SNADGATE
Date:    12/30/97 8:41 AM


We currently have our server running on a MVS mainframe, and I want to
move it to another mainframe.  In anticipation of that, I had requested
all of the client administrators to change their options for
TCPSERVERADDRESS from either an old logical name "mvs.mm.com" for
example or a hard-coded TCP address to a NEW logical name.  My purpose
was so that once all clients had made the change, the new logical name
could be switched from MVS system to another MVS system, simply by
having the TCP/IP gurus changing the resolve of that name from one TCP
address to another.  Well, I'm now told that this is not do-able.  How
have other folks done this??