HP UX SNAplus2 manual Defining Client TPs, NOF verbs querycentrallogger or querynodeall

Managing SNAplus2 Clients

Client Networking Requirements

•The administration commands query_central_logger or query_node_all (these return the information that was available before the TCP/IP connection was dropped, and so may not match the current status of the LAN).

•The NOF verbs query_central_logger or query_node_all

(as for the equivalent administration commands)

In particular, the TCP/IP connection is dropped if you enable the SNAplus2 software but do not start any SNAplus2 applications on the client within the specified timeout.

When one of these events occurs while the TCP/IP connection is down, the client re-starts the attempt to contact a server, as described for the * and servername parameters in “HP-UX Client Network Data File (sna_clnt.net)”, “Servers”, or “[Servers]”.

Incoming Attaches for invoked TPs on this client cannot be accepted while the TCP/IP connection is down; the Attach is rejected as though the target system were inactive. This means that automatically started TPs on the client are not available if no other applications on the client are running and the TCP/IP connection has timed out. However, operator-started TPs on the client can be used at any time, because a Receive_Allocate verb issued by the TP re-establishes the TCP/IP connection.

Defining Client TPs

For information about defining TPs to SNAplus2, see “Defining TPs” or Appendix C, “Configuring an Invokable TP Using snaptpinstall.”

Chapter 11 253