TN3270e Server Manual

Using the TN3270e Server
TN3270e Server Manual—422923-003
3-7
EMS Events

If -n1 is specified, host names are resolved from the hosts file specified by
PARAM TCPIP^HOST^FILE or, if PARAM is omitted, from
$SYSTEM.ZTCPIP.HOSTS. If a host is not found in the hosts file, the host name
does not appear in EMS events and no error is reported.

If -n2 is specified, the method of host name resolution is determined by the
presence or absence of the TCPIP^HOSTS^FILE and TCPIP^RESOLVER^NAME
as expressed by the rules in Table 3-3.
Errors accessing the Domain Name Resolver are reported through EMS events. Refer
to the TCP/IP Configuration and Management Manual or the TCP/IPv6 Configuration
and Management Manual for details of configuration of the resconf file.
Table 3-3 summarizes how name resolution is performed.
EMS Events
If the name resolution command line option (-n) is enabled, the TN3270e server
attempts to provide the host name of clients in all session-related EMS events.
If an EMS alternate collector is specified and logging to that collector fails, event
logging automatically switches to the EMS primary collector. You can use the ALTER
PROCESS command to redirect event logging to another collector.
Note. If host name resolution through a Domain Name Resolver is specified, and the resolver
is not accessible, significant delays will be encountered by all sessions during the
establishment of a new session. This is due to timeouts when attempting to access a Domain
Name Resolver.
Table 3-3. Name Resolution
-n PARAM Rules
0N.A. 5
1N.A. 4
1 TCPIP^HOST^FILE 3, 4
2 N.A. 2, 4, 5
2 TCPIP^HOST^FILE 3, 4, 5
2 TCPIP^RESOLVER^NAME 1, 2, 5
2 (both) 1, 2, 3, 4, 5
Rule 1: If it exists, the file resconf is used to locate the Domain Name Resolver.
Rule 2: If it exists, the file $SYSTEM.ZTCPIP.RESCONF is used to locate the Domain Name Resolver.
Rule 3: If it exists, the file hosts is used.
Rule 4: If it exists, use the file $SYSTEM.ZTCPIP.HOSTS.
Rule 5: No name resolution is done.