NJE uses an IBM-based protocol that works over SNA. With Barr-developed SNA link services, you can connect a network of computers to the mainframe without an SNA gateway. This simplifies the configuration process because it is only necessary to configure the host and the Barr software. Alternatively, NJE can connect through Microsoft’s SNA Server, which is an SNA gateway. The Barr SNA link services and SNA Server emulate a 3174 Cluster Controller, a PU Acronym for Physical Unit. In SNA, software responsible for managing the resources of a node, such as data links. A PU supports a connection to the host (SSCP) for gathering network management statistics. type 2.
The following diagram shows the connection types available to connect NJE to your mainframe SNA network.
|
Connection Type |
Requires |
|
|
|
|
(2) MS/LUA |
SNA gateway software (Must be purchased separately) |
|
|
|
|
(4) HPR/IP |
Ethernet adapter |
|
|
|
When you configure NJE, there are two available connection types: Barr SNA and SNA.
The Barr-developed link services connect a network of computers in a LAN to the mainframe, or establish individual connections between remote computers and the mainframe using modems. This option also provides an easier configuration process because it is not necessary to configure an SNA gateway. If you use JES2 as your host spooler, you can also configure auto-start parameters. Barr SNA provides the following communication links.
HPR/IP – Uses any interface network card such as Ethernet to connect to the mainframe.
The Microsoft LUA option connects a network of computers in a LAN (using TCP/IP) to your mainframe. An SNA gateway, Microsoft SNA Server or HIS, is necessary to interface between the remote computers and the mainframe. With SNA, you must configure the host, the SNA gateway, and NJE. If you use JES2 as your host spooler, you can also configure auto-start parameters.
