Previous Topic: TCP/IP TerminologyNext Topic: ECI Terminology


SNA Terminology

APPC—see Advanced Program-to-Program Communications

Advanced Program-to-Program Communications (APPC)

A set of application programming verbs that is used by an application program to communicate with another program. APPC provides a programmatic interface to SNA's LU 6.2 protocol.

APPL Statement

A VTAM application definition.

APPN—see Advanced Peer-to-Peer Networking

An extension to SNA that features greater distributed network control, dynamic definition of network resources, and automated resource registration and directory lookup.

BIND

An SNA command that results in to Logical Units (LUs) going into session. The BIND establishes the characteristics of the LU-to-LU session.

Common Program Interface—Communications (CPI/C)

IBM's Systems Applications Architecture (SAA) describes a set of software interfaces, conventions, and protocols that provide a framework for building distributed processing applications. CPI/C is part of SAA, and provides calls for transaction programs to participate as a one of the programs in an LU 6.2 program-to-program application. The verbs provided as part of CPI/C provide a common interface to the underlying APPC implementation.

Communications Server

An IBM product that provides SNA networking components used to connect PC-base Local-Area Network workstations to an SNA Network.

conversation

A term used to describe the logical connection between a pair of transaction programs. An established conversation has exclusive use of the session the conversation has been allocated to use. Depending on the type of LU used to support an LU 6.2 conversation, the LU can support the execution of conversation in a serialized fashion or concurrently. It is possible, when using an Independent LU, for multiple conversations between different pairs of transaction programs to be active concurrently, with each conversation being allocated to a distinct session.

CPI/C—see Common Program Interface—Communications

dependent LU

An Logical Unit that can only support a single session at a time. Therefore, a dependent LU can support being used by a single conversation.

FMH-5

An LU 6.2 Function Management Attach Header that describes the request for an LU 6.2 conversation to be established between two application programs.

Host Integration Server (HIS)

A Microsoft product that provides a collection of products that integrate Web or workstation-based applications to applications spread across a network. HIS offers an SNA networking component which connects PC-based Local-Area Networks with SNA networks.

Logical Unit (LU)

A type of SNA NAU that serves as the port through which an end-user of an SNA network communicates. The communications path through an SNA network is represented by an LU-to-LU session, with each user of the network represented by its associated LU. An LU connects a program to the underlying SNA network.

LU—see Logical Unit

LU 6.2

A type of SNA LU that defines the protocol for the message and control data that is exchanged between an APPC application program and it partner program.The LU 6.2 protocol also describes the interaction between the APPC program and the control programs of the SNA network.

ILU—see Independent Logical Unit

Independent Logical Unit (ILU)

A specific type of Logical Unit that is capable of supporting multiple sessions concurrently with other LU's defined in the SNA network. The ability of an ILU to manage parallel sessions lets multiple conversations be allocated and processing concurrently, each conversation allocated to its own session.

NAU—see Network Addressable Unit

Network Addressable Unit (NAU)

A resource managed by the products that implement an SNA network. An NAU is a uniquely identified by it network name and is assigned a unique network address.

Network Node (NN)

An APPN implementation of an SNA Physical Unit.

NN—see Network Node

parallel sessions

A term used to describe the occurrence of two or more sessions between the same pair of LUs. Multiple sessions can concurrently use the same physical resources used to connect the pair of LUs.

Physical Unit (PU)

A type of SNA NAU that represents a node within an SNA network. The PU controls the physical configuration and logical resources associated with its associated SNA node.

PU—see Physical Unit

Request Unit (RU)

A formatted message that is transmitted between NAUs.

RU—see Request Unit

session

A formally bound paring between two NAUs. A bound session must exist before the two partners involved in the session can communicate. A session provides a relatively long-lived connection between two LUs. A session can be used by a succession of conversations.

SNA—see Systems Network Architecture

SNA Network

A logical set of interconnected NAUs over which explicitly formatted message traffic flows. The NAU's are connected by a path control network that is implemented over a physical network of interconnected communications gear, each implementing a portion of the SNA network. An SNA network consists of physical nodes that are interconnected by communications links.

SNA node

A grouping of hardware and software that implement a portion of an SNA network. There are different types of SNA nodes, each helping to facilitate the implementation of the network.

SSCP—see System Service Control Point

Systems Network Architecture (SNA)

A communications architecture developed by IBM that is divided into well-defined logical layers. SNA provides the set of rules that govern the format, definition, and sequence of information sent across an SNA network. SNA formally defines the functional responsibility and protocol assigned to various logical and physical components communicating within the SNA network.

System Service Control Point (SSCP)

A type of SNA NAU that represents the component(s) within the network that provide general management of the network. The SSCP controls the bring up of the network, establishment of sessions, and network recovery.

transaction programs

A program distinguished from other programs by the characteristic that other programs invoke it by using a mechanism known as an Attach. An Attach initiates a conversation with the target transaction program. Transaction programs inter-communicate over the conversation using a set of transaction programming verbs as provided by its associated type 6.2 LU.

Virtual Telecommunications Access Method (VTAM)

An IBM MVS product that provides SSCP communications support within an SNA network.

VTAM—see Virtual Telecommunications Access Method