PreviousNext

The localtimeout, globaltimeout, and queryattempts Attributes

When a system queries a server, it waits for a response for the period that is specified by the localtimeout or globaltimeout attribute. The localtimeout attribute setting applies when the system attempts to contact a local server; the globaltimeout attribute setting applies when the system attempts to contact a global server.

The queryattempts attribute determines how many times DTS resets the time-out timer before the system quits trying to contact a given server. Once the time-out setting has elapsed the number of times that is determined by the queryattempts attribute, the system quits querying the server. If the system is querying a global server, DTS then generates a Server Not Responding event report and removes the server from the system's list of global servers. If a response from the global or local server is required in order to meet the minservers attribute setting, DTS generates a Too Few Servers event report, and the system does not synchronize.

The default setting for the queryattempts attribute is 3. The following example shows how to set the queryattempts attribute value to 4:

dcecp> dts modify -change {queryattempts 4}
dcecp>

The default setting for the localtimeout attribute is 5 seconds, and the default setting for the globaltimeout attribute is 15 seconds. The global setting is larger to account for the communications delay on WAN links that are often used to access the global set. It is unlikely that you will have to change the localtimeout attribute setting. The globaltimeout attribute setting, however, may need to be changed due to the variations in WAN topologies and transmission quality. In the following example, the globaltimeout setting is changed to 20 seconds:

dcecp> dts modify -change {globaltimeout 00-00:00:20.000}
dcecp>

If you continually receive Server Not Responding event reports for a global server, increase the globaltimeout setting. If you increase the setting and the event reports continue, there may be a problem with the communications link to the server.