HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
Managing Win16 Clients
• In situations where the client cannot reach any servers using UDP broadcasts, and must use directed
messages, specify the name of the first server it should try to contact. This applies in the following cases:
• When the SNAplus2 LAN spans multiple TCP/IP subnets, and there are no SNAplus2 servers in any
TCP/IP subnet that the client can access using UDP
• When UDP support is not installed on the client.
In other cases, the use of UDP broadcasts is optional; to specify that broadcasts should not be attempted,
specify the name of the first server instead of
*.
Server2–Server10
Specify the names of additional SNAplus2 servers that the client should contact, in order of preference. If
the client has tried to contact a server using a UDP broadcast (or has tried to contact the server speci
fied
in
Server1), but has received no response, it then attempts to contact the server specified in Server2 using a
directed message. If this fails, it tries the server specified in Server3, and so on.
These server names are optional, but provide a backup mechanism if the broadcast method of locating a server
fails or if the server specified by Server1 is unavailable.
If the client tries all the servers listed without success, it waits for the number of seconds specified by
the server_lost_timeout parameter, then restarts the process of trying to contact a server (either with UDP
broadcasts or with the first server listed).
The parameters Server2–Server10 cannot be set to * to indicate the use of UDP broadcasts. Only the Server1
parameter can be used to indicate this, because the * value must precede any server names in the file.
[Logging]
The [Logging] section of the file specifies logging options for the client. These options can be used to specify
client logging settings that override the logging options specified for the domain as a whole. For more information
about specifying domain logging options, see Section 4.3, Configuring Logging.
If central logging is enabled, all log messages are written to a central file on a server. In this case, only the excep-
tion_logging_enabled and audit_logging_enabled parameters specified here are used; the remaining parameters are
ignored.
The logging options are specified as follows:
exception_logging_enabled
Set this parameter to one of the following values:
YES
Record exception messages.
NO
Do not record exception messages.
This parameter is optional. If it is not specified, the Win16 client uses the global domain settings to determine
whether exception messages are recorded. (The initial default is that exception messages are recorded.)
audit_logging_enabled
Set this parameter to one of the following values:
YES
Record audit messages.
NO
Do not record audit messages.
This parameter is optional. If it is not specified, the Win16 client uses the global domain settings to determine
whether audit messages are recorded. (The initial default is that audit messages are recorded.)
163