The resolver uses the IPv6/common search order when it determines
that any of the following conditions exist:
- The resolver setup statement COMMONSEARCH is specified (to have
the resolver use IPNODES to locate IPv4 addresses, IPv6 addresses,
and sitenames), and the getaddrinfo, gethostbyname, getnameinfo, gethostbyaddr,
sethostent, gethostent, or endhostent APIs are invoked.
- The resolver setup statement NOCOMMONSEARCH is specified (or left
to default), and the getaddrinfo API is attempting to locate an IPv6
address.
- The resolver setup statement NOCOMMONSEARCH is specified (or left
to default), and the getnameinfo API is attempting to resolve an IPv6
address.
Note: The IPv6/common search order is never used for the following
API socket calls:
- getnetbyname
- getnetbyaddr
- setnetent
- getnetent
- endnetent
The IPv6/common search order is as follows. The
search ends at the first file found:
- GLOBALIPNODES value
If defined, the resolver GLOBALIPNODES
setup statement value is used. For a description of the GLOBALIPNODES
statement, see The resolver setup file.
- The value of the environment variable RESOLVER_IPNODES
- userid.ETC.IPNODES
userid is
the user ID that is associated with the current security environment
(address space or task/thread).
- hlq.ETC.IPNODES
hlq represents
the value of the DATASETPREFIX statement specified in the base resolver
configuration file (if found); otherwise, hlq is
TCPIP by default.
- DEFAULTIPNODES
If defined, the resolver DEFAULTIPNODES setup
statement value is used. For a description of the DEFAULTIPNODES statement,
see The resolver setup file.
- /etc/ipnodes