|
SNADS
SNADS or Systems Network Architecture Distribution Services is an "asynchronous distribution service that can store data for delayed delivery." SNADS uses SNA data links to allow messages and objects to be sent from system to system using the APPC protocol. It is a very robust service: once an object has been accepted by SNADS it will get to its destination. If the communication link is unavailable (down), the transmission will be held on the sending system until the link is available, at which time it is sent. If the transmission is interrupted, it will be resumed or re-sent once the communication problem is resolved. SNADS is available on several IBM platforms, including IBM i, the AS/400 or System/38. Microsoft Exchange Server 5.5 Enterprise Edition includes a gateway called ''SNA Distribution Services (SNADS) Connector'' for communication with SNADS networks. References External linksSNADS documentation on ibm.com See also *Systems Network Architecture Systems Networ ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Systems Network Architecture
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 but, in itself, is 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. History SNA was made public as part of IBM's "Advanced Function for Communications" announcement in September, 1974, which included the implementation of the SNA/SDLC (Synchronous Data Link Control) protocols on new communications products: *IBM 3767 communication terminal (printer) *IBM 3770 data communication system They were supported by IBM 3704/3705 communication controllers and their Network Control Program (NCP), and by System/370 and their VTAM and other software such as CICS and IMS. This announcement was followed by ano ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM Advanced Program-to-Program Communication
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 ( Logical unit type 6.2 ) APPC was developed in 1982 as a component of IBM's Systems Network Architecture (SNA). Several APIs were developed for programming languages such as COBOL, PL/I, C or REXX. APPC software is available for many different IBM and non-IBM operating systems, either as part of the operating system or as a separate software package. APPC serves as a translator between application programs and the network. When an application on your computer passes information to the APPC software, APPC translates the information and passes it to a network interface, such as a LAN adapter card. The information travels acro ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM I
IBM i (the ''i'' standing for ''integrated'') is an operating system developed by IBM for IBM Power Systems. It was originally released in 1988 as OS/400, as the sole operating system of the IBM AS/400 line of systems. It was renamed to i5/OS in 2004, before being renamed a second time to IBM i in 2008. It is an evolution of the System/38 CPF operating system, with compatibility layers for System/36 SSP and AIX applications. It inherits a number of distinctive features from the System/38 platform, including the Machine Interface, the implementation of object-based addressing on top of a single-level store, and the tight integration of a relational database into the operating system. History Origin OS/400 was developed alongside the AS/400 hardware platform beginning in December 1985. Development began in the aftermath of the failure of the Fort Knox project, which left IBM without a competitive midrange system. During the Fort Knox project, a skunkworks project was st ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
AS/400
The IBM AS/400 (Application System/400) is a family of midrange computers from IBM announced in June 1988 and released in August 1988. It was the successor to the System/36 and System/38 platforms, and ran the OS/400 operating system. Lower-cost but more powerful than its predecessors, the AS/400 was extremely successful at launch, with an estimated 111,000 installed by the end of 1990 and annual revenue reaching $14 billion that year, increasing to 250,000 systems by 1994, and about 500,000 shipped by 1997. A key concept in the AS/400 platform is Technology Independent Machine Interface (TIMI), a platform-independent instruction set architecture (ISA) that is compiled along with the native machine language instructions. The platform has used this capability to change the underlying processor architecture without breaking application compatibility. Early systems were based on a 48-bit CISC instruction set architecture known as the ''Internal Microprogrammed Interface'' (IMP ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
System/38
The System/38 is a discontinued minicomputer and midrange computer manufactured and sold by IBM. The system was announced in 1978. The System/38 has 48-bit addressing, which was unique for the time, and a novel integrated database system. It was oriented toward a multi-user system environment. At the time, the typical system handled from a dozen to several dozen terminals. Although the System/38 failed to displace the systems it was intended to replace, its architecture served as the basis of the much more successful IBM AS/400. History The System/38 was introduced on October 24, 1978 and delivered in 1980. Developed under the code-name "Pacific", it was made commercially available in August 1979. The system offered a number of innovative features, and was designed by a number of engineers including Frank Soltis and Glenn Henry. The architecture shared many similarities with the design of the failed IBM Future Systems project, including the single-level store, the use of mic ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
.jpg "Click for more on -> Systems Network Architecture")
.jpg "Click for more on -> System/38")