Barry writes:
> Take a look in NMMGR at the NETXPORT.GLOBAL screen.
> On this screen you can configure your name search
> methods, and the order in which to use them.

But DNS isn't one of the options.  AFAIK, the NETXPORT.GLOBAL screen only
affects "NS" name lookups, and not "ARPA" name lookups.  I believe that the
NetIPC name resolution routines and the Berkeley sockets name resolution
routines may not both operate the same way, so it would depend on which
interface the program you are running uses.  But I don't understand the real
differences (if any) between the two, and how the whole name resolution
thing *really* works under MPE.

Maybe someone from HP can present a flowchart of exactly what process each
type of lookup goes through, how the "Local HP3000 node name" of a machine
interacts with the "Local domain name" as configured separately in NMMGR,
what happens if you have /etc/hosts, *and* DNS, *and* Probe, *and*
NSDIRectory, etc.

> I'm less certain about this one, but there is a
> configuration file called RESLVCNF.NET.SYS, the
> contents of which may have some bearing on your
> problem.

Generally RESLVCNF.NET.SYS *is* where you want to look if you're expecting
to do lookups to a DNS server as opposed to an "NS" service like Probe,
Probe Proxy, or the NSDIR directory.  An update/upgrade or patch
installation shouldn't, as far as I know, result in changes to this file or
the way it's interpreted, so I'm surprised that a patch installation would
break name lookups.

G.