|
IBM LU6.2
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. Some examples of non-IBM products which ... [...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 an ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Peer-to-peer
Peer-to-peer (P2P) computing or networking is a distributed application architecture that partitions tasks or workloads between peers. Peers are equally privileged, equipotent participants in the network. They are said to form a peer-to-peer network of nodes. Peers make a portion of their resources, such as processing power, disk storage or network bandwidth, directly available to other network participants, without the need for central coordination by servers or stable hosts. Peers are both suppliers and consumers of resources, in contrast to the traditional client–server model in which the consumption and supply of resources are divided. While P2P systems had previously been used in many application domains, the architecture was popularized by the file sharing system Napster, originally released in 1999. The concept has inspired new structures and philosophies in many areas of human interaction. In such social contexts, peer-to-peer as a meme refers to the egalitarian so ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Common Programming Interface For Communications
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. It was adopted in 1992 by X/Open as an open systems standard, identified as standard C210, and documented in ''X/Open Developers Specification: CPI-C''. See also * IBM Advanced Program-to-Program Communication References External links Distributed Transaction Processing: The XCPI-C Specification Version 2 [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM Information Management System
The IBM Information Management System (IMS) is a joint hierarchical database and information management system that supports transaction processing. History IBM designed the IMS with Rockwell and Caterpillar starting in 1966 for the Apollo program, where it was used to inventory the very large bill of materials (BOM) for the Saturn V moon rocket and Apollo space vehicle. The first "IMS READY" message appeared on an IBM 2740 terminal in Downey, California, on August 14, 1968. In the interim period, IMS has undergone many developments as IBM System/360 technology evolved into the current z/OS and IBM zEnterprise System technologies. For example, IMS now supports the Java programming language, JDBC, XML, and, since late 2005, web services. Vern Watts was IMS's chief architect for many years. Watts joined IBM in 1956 and worked at IBM's Silicon Valley development labs until his death on April 4, 2009. He had continuously worked on IMS since the 1960s. Database The IMS Data ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Microsoft Host Integration Server
Microsoft Host Integration Server (a.k.a. HIS) is a gateway application providing connectivity between Microsoft Windows networks and IBM mainframe and IBM i systems. Support is provided for SNA, 3270 (standard and TN3270), 5250 (standard and TN5250), 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. HIS is the successor to Microsoft SNA Server. SNA Server was released in 1994, and was one of the first add-on products available for the fledgling Windows NT. SNA Server was also included in Microsoft BackOffice Server. Similar gateway products were NetWare for SAA (defunct, ran on Novell NetWare) and IBM Communications Manager/2 (defunct, ran on OS/2). HIS has an active ecosystem of third party hardware (e.g. network ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
NetWare
NetWare is a discontinued computer network operating system developed by Novell, Inc. It initially used cooperative multitasking to run various services on a personal computer, using the IPX network protocol. The original NetWare product in 1983 supported clients running both CP/M and MS-DOS, ran over a proprietary star network topology and was based on a Novell-built file server using the Motorola 68000 processor. The company soon moved away from building its own hardware, and NetWare became hardware-independent, running on any suitable Intel-based IBM PC compatible system, and able to utilize a wide range of network cards. From the beginning NetWare implemented a number of features inspired by mainframe and minicomputer systems that were not available in its competitors' products. In 1991, Novell introduced cheaper peer-to-peer networking products for DOS and Windows, unrelated to their server-centric NetWare. These are NetWare Lite 1.0 (NWL), and later Personal ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Systems Application Architecture
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. SAA did not define new standards, but selected from among IBM's existing guidelines and software. IBM also purchased some third party software from developers such as Bachman Information Systems, Index Technology, Inc., and KnowledgeWare, Inc. These were intended to be implemented uniformly across all SAA compliant environments. The standard was "designed to make application programs look and work in the same manner across the entire range of the company's personal computing systems, midrange processors and System/370 processors." SAA was ... [...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 across the ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Network Protocols
A communication protocol is a system of rules that allows two or more entities of a communications system to transmit information via any kind of variation of a physical quantity. The protocol defines the rules, syntax, semantics and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both. Communicating systems use well-defined formats for exchanging various messages. Each message has an exact meaning intended to elicit a response from a range of possible responses pre-determined for that particular situation. The specified behavior is typically independent of how it is to be implemented. Communication protocols have to be agreed upon by the parties involved. To reach an agreement, a protocol may be developed into a technical standard. A programming language describes the same for computations, so there is a close analogy between protocols and programming languages: ''protocols are to co ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
.jpg "Click for more on -> Systems Network Architecture")
