IBM LU6.2

Last updated

Logical Unit 6.2 is an IBM-originated communications protocol specification dating from 1974, and is part of IBM's Systems Network Architecture (SNA).

A device-independent SNA protocol, it is used for peer-to-peer communications between two systems, for example, between a computer and a device (e.g. terminal or printer), or between computers. LU6.2 is used by many of IBM's products, including Common Programming Interface for Communications Intersystem Communications (CICS ISC), and Information Management System, and also many non-IBM products. In 1986, Bruce Compton, Manager of Office Systems and Technology with General Electric, said:

LU 6.2 means I don't have to write the software communications interfaces. If I have one office server in a DEC environment, and another in a Wang environment I can use the LU 6.2 standard to pass files between those devices, and I don't have to worry about things like block checking and clock. [1]

Some examples of non-IBM products which implemented the SNA stack including LU6.2 are: Microsoft Host Integration Server, and NetWare for SAA. [2]

APPC is a protocol used with LU6.2 architecture. APPC is often used to refer to the LU6.2 architecture or to specific LU6.2 features.

LU6.2-compliant devices operate as peers within the network and can perform multiple simultaneous transactions over the network. LU6.2 devices can also detect and correct errors. The LU6.2 definition provides a common API for communicating with and controlling compliant devices. Although the concepts were the same on all platforms, the actual API implementation often varied on each IBM platform which implemented it. Other vendors also implemented LU6.2 in their own products and with their own APIs. IBM later defined the Common Programming Interface for Communications (CPIC) API which would eventually become widely implemented. CPIC allowed for the authoring of multi-platform code.

Adoption was slow but steady. As of November 1987, of 207 large US companies interviewed "Eighteen percent of the companies said they have implemented LU 6.2 systems already, and 51% said they expect to have such systems up and running within two years." [3]

Related Research Articles

The Internet protocol suite is the conceptual model and set of communications protocols used in the Internet and similar computer networks. It is commonly known as TCP/IP because the foundational protocols in the suite are the Transmission Control Protocol (TCP) and the Internet Protocol (IP). During its development, versions of it were known as the Department of Defense (DoD) model because the development of the networking method was funded by the United States Department of Defense through DARPA. Its implementation is a protocol stack.

A network operating system is a specialized operating system for a network device such as a router, switch or firewall.

DECnet is a suite of network protocols created by Digital Equipment Corporation. Originally released in 1975 in order to connect two PDP-11 minicomputers, it evolved into one of the first peer-to-peer network architectures, thus transforming DEC into a networking powerhouse in the 1980s. Initially built with three layers, it later (1982) evolved into a seven-layer OSI-compliant networking protocol.

Systems Network Architecture (SNA) is IBM's proprietary networking architecture, created in 1974. It is a complete protocol stack for interconnecting computers and their resources. SNA describes formats and protocols and is, in itself, not a piece of software. The implementation of SNA takes the form of various communications packages, most notably Virtual Telecommunications Access Method (VTAM), the mainframe software package for SNA communications.

InfiniBand (IB) is a computer networking communications standard used in high-performance computing that features very high throughput and very low latency. It is used for data interconnect both among and within computers. InfiniBand is also used as either a direct or switched interconnect between servers and storage systems, as well as an interconnect between storage systems. It is designed to be scalable and uses a switched fabric network topology.

Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the complexity of developing applications that span multiple operating systems and network protocols. The middleware creates a distributed communications layer that insulates the application developer from the details of the various operating systems and network interfaces. APIs that extend across diverse platforms and networks are typically provided by MOM.

Systems Application Architecture (SAA), introduced in 1987, is a set of standards for computer software developed by IBM. The SAA initiative was started in 1987 under the leadership of Earl Wheeler, the "Father of SAA". The intent was to implement SAA in IBM operating systems including MVS, OS/400 and OS/2. AIX, IBM's version of the UNIX operating system, was not a target of SAA, but does have interoperability with the SAA family.

Virtual Telecommunications Access Method (VTAM) is the IBM subsystem that implements Systems Network Architecture (SNA) for mainframe environments. VTAM provides an application programming interface (API) for communication applications, and controls communication equipment such as adapters and controllers. In modern terminology, VTAM provides a communication stack and device drivers.

In computing, Advanced Program to Program Communication or APPC is a protocol which computer programs can use to communicate over a network. APPC is at the application layer in the OSI model, it enables communications between programs on different computers, from portables and workstations to midrange and host computers. APPC is defined as VTAM LU 6.2

Advanced Peer-to-Peer Networking (APPN) is an extension to the Systems Network Architecture (SNA) "that allows large and small computers to communicate as peers across local and wide-area networks."

Teleprocessing Network Simulator (TPNS) is an IBM licensed program, first released in 1976 as a test automation tool to simulate one or many network terminal(s) to a mainframe computer system, for functional testing, regression testing, system testing, capacity management, benchmarking and stress testing. In 2002, IBM re-packaged TPNS and released Workload Simulator for z/OS and S/390 (WSim) as a successor product.

Novell Embedded Systems Technology (NEST) was a series of APIs, data formats and network protocol stacks written in a highly portable fashion intended to be used in embedded systems. The idea was to allow various small devices to access Novell NetWare services, provide such services, or use NetWare's IPX protocol as a communications system. Novell referred to this concept as "Extended Networks", and when the effort was launched they boasted that they wanted to see one billion devices connected to NetWare networks by year 2000. NEST was launched in mid-1994 countering Microsoft's similar Microsoft at Work efforts, which had been launched in 1993.

A clustered file system is a file system which is shared by being simultaneously mounted on multiple servers. There are several approaches to clustering, most of which do not employ a clustered file system. Clustered file systems can provide features like location-independent addressing and redundancy which improve reliability or reduce the complexity of the other parts of the cluster. Parallel file systems are a type of clustered file system that spread data across multiple storage nodes, usually for redundancy or performance.

Microsoft Host Integration Server is a gateway application providing connectivity between Microsoft Windows networks and IBM mainframe and AS/400 systems. Support is provided for SNA, 3270, 5250, CICS, APPC, and other IBM protocols. Support is also provided for advanced integration with Windows networks and software, such as linking Microsoft Message Queuing applications to IBM WebSphere MQ, binding Microsoft DTC transactions with CICS, and cross-protocol access to DB2 databases on IBM platforms.

Windows NT is a family of operating systems produced by Microsoft, the first version of which was released on July 27, 1993. It is a processor-independent, multiprocessing and multi-user operating system.

Common Programming Interface for Communications (CPI-C) is an application programming interface (API) developed by IBM in 1987 to provide a platform-independent communications interface for the IBM Systems Application Architecture based network, and to standardise programming access to SNA LU 6.2. CPI-C was part of IBM Systems Application Architecture (SAA), an attempt to standardise APIs across all IBM platforms.

The IBM 9370 systems were "baby mainframe" midrange computers, released 1986 at the very low end of, and compatible with System/370.

The IBM WebSphere Host On-Demand Server, or HOD as it is commonly known is a Java application that runs on a Server that is deliverable via modern web servers such as the Apache web server. The application allows the end user to access IBM 3270, IBM 5250 and other Virtual terminals using the Telnet protocol whether through a secure or unsecured mode of communication. The product in its present form runs on AIX, UNIX, HP-UX, i5/OS, Z/OS, Linux, Solaris and Windows Server.

The Physical Security Interoperability Alliance (PSIA) is a global consortium of more than 65 physical security manufacturers and systems integrators focused on promoting interoperability of IP-enabled security devices and systems across the physical security ecosystem as well as enterprise and building automation systems.

Distributed Data Management Architecture

Distributed Data Management Architecture (DDM) is IBM's open, published software architecture for creating, managing and accessing data on a remote computer. DDM was initially designed to support record-oriented files; it was extended to support hierarchical directories, stream-oriented files, queues, and system command processing; it was further extended to be the base of IBM's Distributed Relational Database Architecture (DRDA); and finally, it was extended to support data description and conversion. Defined in the period from 1980 to 1993, DDM specifies necessary components, messages, and protocols, all based on the principles of object-orientation. DDM is not, in itself, a piece of software; the implementation of DDM takes the form of client and server products. As an open architecture, products can implement subsets of DDM architecture and products can extend DDM to meet additional requirements. Taken together, DDM products implement a distributed file system.

References

  1. Dix, John (7 Apr 1986). "The Glacier Advances" (v.3 n.5). Network World. Retrieved Nov 23, 2018.
  2. Horwitt, Elisabeth (May 10, 1993). "Novell sells 3270 line, addresses NetWare messaging" (v.27 n.19). Computerworld. Retrieved Nov 23, 2018.
  3. Korzeniowski, Paul (Nov 2, 1987). "LU 6.2 use accelerates" (v.4 n.44). Network World. Retrieved Nov 23, 2018.