HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
Managing Win32 clients
• Invokable TPs (APPC or CPI-C) that can run on the client
The most commonly used parameters can also be modified using the Client Configuration Utility, which is the
preferred method for modifying them. For more information, see Section 11.2.4,
Win32 Client Configuration.
11.2.1 Enabling a Win32 Client
The Win32 Client runs as a Windows service. The installation program configures it to start automatically when
the computer starts. If necessary, you can start it manually in either of the following ways.
• Start the client service from the Services applet under Control Panel, Administrative Tools.
• Type
net start sxclient from a command window or from the Start / Run icon.
The client then uses the information in the Windows Registry, defined using the Client Configuration Utility and
described in Section 11.2.4, Win32 Client Configuration, to locate a server running SNAplus2.
11.2.2 Viewing Status of a Win32 Client
The Client Monitor places an icon in the system tray that displays the Client’s status when you move the mouse
pointer over it. The Monitor is set up to run automatically when the computer starts, but you can also run it
manually from the Start menu if necessary. The status is one of the following:
Not Active
The client has not been started.
Not Connected
The client has been started, but has not yet made contact with a server (or has lost contact).
Server_Name
The client is connected to the named server.
11.2.3 Disabling a Win32 Client
Before disabling the client, ensure that all SNAplus2 applications (3270 and 5250 emulation programs, or
applications using the SNAplus2 APIs) on the client have been stopped.
To disable the client, stop the Client service in one of the following ways.
• Stop the Client service from the Services applet under Control Panel, Administrative Tools.
• Type net stop sxclient from a command window or from the Start / Run icon.
On a computer running Windows Terminal Services, this means that all users are prevented from using the client.
11.2.4 Win32 Client Configuration
On Win32 Clients, configuration information is held in the Windows Registry. The Registry contains SNA network
information(similar to the information held in the client network data file on HP-UX clients). It also contains some
additional configuration information that is specific to Win32 Clients.
Note
Configuration information for a CPI-C application (the local TP name and local LU alias)
can be specified either in environment variables or in the registry. You may need to use
environment variables if you are using Windows Terminal Server and need to run multiple
copies of the same application using different local LUs. For more details, see Section
11.2.4, Win32 Client Configuration.
146