HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
Managing Win32 clients
The Registry data type of this value is REG_DWORD.
Specify the time in seconds that an application waits while the client starts and tries to contact a server.
Values between 0 and 300 are valid; values outside this range are forced into the range. The default value is
10 seconds.
This parameter can be used to control events when both the application and the client are congured to be
started on system startup (either by being in the Startup Folder or by being an automatically started service).
The application waits for the number of seconds specied in this eld, to enable the client to get in rst. In
this way, the client can connect to a server to provide the resources required by the application, before the
application fails due to the lack of those resources.
Servers
The Servers subkey contains information about SNAplus2 conguration servers that the client should contact to
obtain conguration information. This list should contain the names of the master conguration server and any
backup servers in the same domain as the client. For information about conguring master and backup servers, see
Section 4.1,
Conguring Client/Server Functions.
Server1
The Registry data type of this value is REG_SZ.
Enter an asterisk (*) or a server name:
To indicate that the client should attempt to nd a server running SNAplus2 by using a UDP broadcast
message to all computers on its TCP/IP subnet (or on all subnets that it can access, if the client computer
contains more than one LAN adapter card), specify *.
The client retries the broadcast every 10 seconds, up to the number of attempts specied by the broad-
cast_attempt_count parameter, until it contacts a server. If the limit specied by broadcast_attempt_count
is reached before a server has been contacted, the client then tries using directed messages to one or more
named servers (specied by the following lines of the le).
In situations where the client cannot reach any servers using UDP broadcasts, and must use directed mes-
sages, specify the name of the rst 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 rst server instead of *.
Server2Server9
The Registry data type of this value is REG_SZ.
Specify the names of additional SNAplus2 conguration 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 specied
in Server1), but has received no response, it then attempts to contact the server specied in Server2 using
a directed message. If this fails, it tries the server specied 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
specied by Server1 is unavailable.
If the client tries all the servers listed without success, it waits for the number of seconds specied by
the server_lost_timeout parameter, then restarts the process of trying to contact a server (either with UDP
broadcasts or with the rst server listed).
The parameters Server2Server9 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 le.
150