Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX SNAplus2 API NOF Programmer's Guide: HP-UX 11.0, 11i v1, and 11i v2 > Chapter 1 Introduction to the NOF API

SNAplus2 Resources

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The resources of the SNAplus2 system can be divided into two types:

  • Node Resources

    Define the communications capabilities of a particular APPN node:

    • Connectivity resources:

      • DLCs

      • Ports

      • Link stations

      • Connection networks

    • LUs

      • Type 0-3 for: 3270. RJE, LUA communications

      • Type 6-2 for: APPC, CPI-C communications, 5250 emulation

    • Modes and classes of service

    • Directroy information

  • Domain Resources

    Additional resources not defined as part of the node, which are used to support particular user programs. These resources include:

    • 3270 user information

    • RJE workstations

    • CPI-C side information

    • Information about access to the HP-UX Command Facility and Service Point Command Facility

    For more information about these resources, refer to the HP-UX SNAplus2 Administration Guide.

Dependent LU Register (DLUR)

This section does not apply to LEN nodes.

As well as providing direct access to a host computer, SNAplus2 can also provide DLUR facilities. This feature enables sessions for dependent LUs to span multiple nodes in an APPN network, instead of requiring a direct connection to the host.

DLUR on the SNAplus2 node works in conjunction with Dependent LU Server (DLUS) at the host to route sessions from dependent LUs on the SNAplus2 node across the network to the DLUS host. The route to the host can span multiple nodes, and can take advantage of APPN’s network management, dynamic resource location, and route calculation facilities.

PU Concentration

As well as providing direct access to a host computer, SNAplus2 can also provide PU concentration facilities. This feature enables other computers to use SNAplus2 resources to access a host computer instead of requiring a separate connection to the host from each computer.

Figure 1-2 illustrates the PU concentration feature.

Figure 1-2 PU Concentration Facilities Provided by SNAplus2

PU Concentration Facilities Provided by SNAplus2

The downstream computer must contain an SNA PU type 2.0 or 2.1 to support dependent LUs. For example, the downstream computer could be a PC running Microsoft’s SNA Server for Windows NT or another SNAplus2 computer.

Using this feature, all the data transferred between the host and the downstream computer is routed through the SNAplus2 local node. This enables a downstream computer to share a host connection with SNAplus2 or with other downstream computers instead of requiring a direct link. For example, you could set up several downstream computers connected to SNAplus2 over a local Token Ring network, so that they could all access the same long-distance leased line from SNAplus2 to the host.

Using PU concentration also simplifies the configuration at the host because there is no need to define the downstream computers and the communications links to them. The host configuration only needs to include the SNAplus2 computer and its host communications link; the LUs at the downstream computers are configured as part of the resources of the SNAplus2 computer. The host computer is not aware that PU concentration is being used.

TN Server

SNAplus2 TN server provides access to 3270 host computers for TN3270 users on other computers. The TN server feature enables TN3270 users to share a host connection with SNAplus2 or with other TN3270 users, instead of requiring a direct link. It also enables TN3270 users to access hosts that are not running TCP/IP.

Figure 1-3 illustrates the SNaplus2 TN server function.

Figure 1-3 SNAplus2 TN Server

SNAplus2 TN Server

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 computer 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.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003 Hewlett-Packard Development Company, L.P.