SNA connectivity overview

BARR/NJE

BARR/NJE uses an IBM-based protocol that works over SNA Acronym for Systems Network Architecture. The description of logical structure, formats, protocols, and operational sequences for transmitting information units through and controlling the configuration and operation of networks.. 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, BARR/NJE can connect through Microsoft’s SNA Server, which is an SNA gateway, or a channel-attached (CTC Acronym for channel-to-channel. A channel-attached SNA connection type that uses a cable to connect the remote computer to the mainframe.) connection. 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 BARR/NJE to your mainframe SNA network.

Connection types

When you configure BARR/NJE, there are three available connection types: Barr SNA, SNA, and CTC.

Barr SNA

The Barr-developed link services connect a network of computers in a LAN Acronym for Local Area Network. A group of computers and other devices dispersed over a relatively limited area and connected by a communications link that enables any device to interact with any other on the network. LANs commonly include computers and shared resources such as laser printers and large hard disks. The devices on a LAN are known as nodes, and the nodes are connected by cables through which messages are transmitted. (In contrast, a wide area network might span hundreds or thousands of miles.) 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.

• 802.2 LLC2 – Uses any interface network card such as Ethernet or a token ring to connect to the mainframe. Requires installing the DLC protocol, which comes with your operating system.

• SDLC – Uses a modem or CSU/DSU Acronyms for Channel Service Unit and Data Service Unit. These make up the device that digital data services (dedicated communications lines) use to connect two networks, instead of a modem. The CSU connects the network to the transmission line; the DSU converts data for transmission by the CSU and controls data flow. to connect to the mainframe. Requires the BARR SYNC modem adapter, which we provide to you.

• HPR/IP – Uses any interface network card such as Ethernet to connect to the mainframe.

SNA

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 BARR/NJE. If you use JES2 as your host spooler, you can also configure auto-start parameters.

CTC

The channel-to-channel (CTC) option connects remote computers directly to the mainframe using channel cables. The channel cables transfer data at a faster rate than the other connection types. CTC, however, does not provide the same flexibility, such as giving you access to networks over long distances. With CTC, you only need to configure the host and BARR/NJE; an SNA gateway is not required.

What do you want to do?

• Get started with BARR/NJE

See also:

• BARR/NJE overview

• Configuring BARR/NJE for Barr SNA

• Configuring BARR/NJE for CTC

• Configuring BARR/NJE for SNA