Manualshelf

HP-UX SNAplus2 R7 NOF Programmer's Guide

ManualsBrandsHP ManualsSoftwareHP-UX SNAplus2 Software
41424344454647484950
Introduction to the NOF API
SNAplus2 Resources
Figure 1–3 SNAplus2 TN Server
TCP/IP Network
TCP/IP Network
Host
SNA Node
Running TN Server
Clients Running TN3270
and TN3270E Programs
SNA Nodes Running
3270 Emulators
SNA Node
TN Server Configuration
TN3270 Program View
of the Configuration
Host
Clients Running TN3270
and TN3270E Programs
Host
Host View of the Configuration
The SNAplus2 TN server feature provides an association between a TN3270 user and SNAplus2 3270 LU. All data
from the TN3270 user is routed to the LU. This means that the configuration for both the host and the TN3270 user
is as though they were connected directly; neither needs to be aware that data is being routed through TN server.
TN Server Users
Any 3270 emulation programs that communicate over TCP/IP rather than over an SNA network are referred to as
TN3270 programs (Telnet 3270 emulation programs). SNAplus2 TN server supports various TN3270 programs,
including SNAplus2 TN3270 (packaged separately from the main SNAplus2 product).
When a TN3270 program communicates with TN server, SNAplus2 identifies it by the TCP/IP address of the com-
puter where the TN3270 program is running; it cannot distinguish between two different TN3270 programs being
used by different users on the same computer. In the SNAplus2 manuals, the term “TN server user” refers to the
computer where a TN3270 program is running (identified by its TCP/IP address), and not to an individual user of
that program.
Each TN server user is normally configured to access a single 3270 LU and so is restricted to one host session at
a time. However, you can also configure a TN server user to access a pool of 3270 LUs instead of having a single
dedicated 3270 LU for each user. This enables the user to access as many sessions as there are available LUs in
the pool.
You can also define a default record that enables access by any TN3270 client (with the same LUs or LU pools for
all clients), instead of having to define an individual record for each client.
47