From: bleau@umdsp.umd.edu
Newsgroups: vmsnet.mail.mx
Subject: Re: Misconfigured UCX?
Date: 13 Aug 92 17:38:09 GMT
Reply-To: bleau@umdsp.umd.edu
Organization: University of Maryland Physics Dept., College Park, MD

In article <1992Aug12.234800.29944@cco.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
>Sorry for asking a frequently-asked question, but I never thought I'd be
>saddled with setting up MX on a system running UCX.  Here's the router log file:
> ...
>OK.  How do I get the domain expander to not translate IMG.UMD.EDU to img?  I
>don't have access to the UCX manuals (I'm in California, and I'm installing MX
>on a machine in Maryland, and the local computing center doesn't have the UCX
>documentation on CDROM).  So I'd appreciate it if someone could tell me either:
>	1)  How to get MX not to run the domain expander; or better
>	2)  How to reconfigure UCX's hosts database so that it uses the FQDN
>	    as the primary name of the system.
>Please give explicit instructions if you're answering question 2.  Thanks.

I recall running into a similar problem over a year ago when installing MX and
UCX on a system I used to manage.  I think it was resolved through a series
of steps, but I only recall some of them.  One is that the UCX host database
must have the FQDN of the local host _first_, then any aliases for it.  Get
into UCX and do a SHOW HOST IMG to see how it is defined.  Use the command

	SET HOST hostname/ADDRESS=Internet-address/ALIAS=other-name

to define alternate names.  This can be repeated as often as desired.  If the
original name is incorrect (is not FQDN) you may have to first do a SET NOHOST
to undefine it, but then _immediately_ do the proper SET HOST commands in the
proper sequence so that IMG.UMD.EDU is the first one in the list.  Since UCX
says host names are case sensitive I put both in, though I never came across a
case where I could tell that it mattered.

To re-emphasize, the order in which the host name and its aliases are specified
in UCX matters to MX, though just why I don't know.  (Comments, Matt?)  If you
make a change to the primary name, double check the UCX startup and
configuration files (I think it's called UCX$INET_SET_INTERFACES.COM) just in
case the _old_ name was specified there.  The last thing you want is for UCX to
not work at all, so TELNET and other utilities also fail.

If this node is in a cluster be sure to make similar changes on the other nodes
in the cluster, as it's quite likely UCX was installed in the same manner on
the other nodes.  Test it out well on the main node first, though.

Sorry I can't be more explicit about the commands, but it has been a while
since I solved this one, and I no longer manage the system, so I've lost touch
with many of its problems/solutions.

BTW, I didn't have UCX manuals either, and we couldn't afford a CD-ROM with a
full documentation set and a reader to go along with it.  I was able to resolve
it with the help file (within UCX), a few friends to post for me, and this news
group.  Email me directly or post again if you have more problems along these
lines and I'll try to jog my memory a bit more.  Good luck!

Larry Bleau
University of Maryland
bleau@umdsp.umd.edu
301-405-6223