HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
Managing Win32 clients
• 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 SNA 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 Section 11.4.2, HP-UX Client Network
Data File (sna_clnt.net), Section 11.3.3, Win16 Client Initialization File (sna.ini), or Section 11.2.4, Win32 Client
Configuration.
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.
11.2 Managing Win32 clients
WINDOWS
SNAplus2 enables machines running Microsoft Windows 2000, Windows XP, or Windows Server 2003 to act as
clients in the SNAplus2 domain. The SNAplus2 client software includes API libraries that are compatible with
Microsoft Host Integration Server, the Windows Open Systems Architecture (WOSA), and the interfaces provided
by IBM Personal Communications and Communications Server for Windows. This enables applications written for
these implementations to run unchanged on the SNAplus2 Win32 client.
SNAplus2 supports the following WOSA APIs:
• Windows APPC
• Windows CPI-C
• Windows LUA
• Windows CSV
• 3270 Emulator Interface Specification
For more information about Windows SNA APIs, see the documentation provided with Microsoft Host Integration
Server.
SNA network information, and other information required by Win32 clients, is held in the Windows Registry.
The client must be enabled before you can use SNAplus2 applications or emulation programs on the client. For
more information, see Section 11.2.1, Enabling a Win32 Client. When the client is enabled, it contacts a server
running SNAplus2 over the TCP/IP network in order to access SNAplus2 features.
The operation of the client is also controlled by the information in the Windows Registry. The Windows Registry
contains information about the following:
• Configuration information specific to Win32 clients
• Servers that the client can access
• Logging and tracing options for applications running on the client
• Additional options for CPI-C and CSV applications running on the client
145