|
Communications Controller For Linux
Communications Controller for Linux (Communications Controller for Linux on System z or CCL) is an IBM software product announced in 2005 that runs under Linux on IBM Z and emulates an IBM 37xx communications controller. CCL runs unmodified IBM Network Control Program (NCP) to allow consolidation of an SNA network infrastructure to IP. According to IBM "SNA traffic enters and leaves CCL as SNA network flows over an OSA adapter. However, your wide area network infrastructure does not need to be SNA. You can consolidate your SNA traffic and use tunneling such as data link switching (DLSw) to encapsulate the SNA communication over an IP network." CCL supports Ethernet and Token Ring local area network (LAN) connectivity directly, and other connectivity through a DLSw router. X.25 requires IBM's NPSI software plus a third party package. CCL does not support Bisync Binary Synchronous Communication (BSC or Bisync) is an IBM character-oriented, half-duplex link protocol, announced ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Linux On IBM Z
Linux on IBM Z or Linux on zSystems is the collective term for the Linux operating system compiled to run on IBM mainframes, especially IBM Z / IBM zSystems and IBM LinuxONE servers. Similar terms which imply the same meaning are ''Linux/390'', ''Linux/390x,'' etc. The three Linux distributions certified for usage on the IBM Z hardware platform are Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and Ubuntu. History Linux on IBM Z originated as two separate efforts to port Linux to IBM's System/390 servers. The first effort, the "Bigfoot" project, developed by Linas Vepstas in late 1998 through early 1999, was an independent distribution and has since been abandoned. IBM published a collection of patches and additions to the Linux 2.2.13 kernel on December 18, 1999, to start today's mainline Linux on IBM Z. Formal product announcements quickly followed in 2000, including the Integrated Facility for Linux (IFL) engines. Think Blue Linux was an early mainframe distribution ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM 37xx
IBM 37xx (or 37x5) is a family of IBM Systems Network Architecture (SNA) programmable communications controllers used mainly in mainframe environments. All members of the family ran one of three IBM-supplied programs. *''Emulation Program'' (EP) mimicked the operation of the older IBM 270x non-programmable controllers. *'' Network Control Program'' (NCP) supported Systems Network Architecture devices. *''Partitioned Emulation Program'' (PEP) combined the functions of the two. Models 370x series * 3705 — the oldest of the family, introduced in 1972 to replace the non programmable IBM 270x family. The 3705 could control up to 352 communications lines. * 3704 was a smaller version, introduced in 1973. It supported up to 32 lines. 371x The 3710 communications controller was introduced in 1984. 372x series The 3725 and the 3720 systems were announced in 1983. The 3725 replaced the hardware line scanners used on previous 370x machines with multiple microcoded proce ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
IBM Network Control Program
The IBM Network Control Program, or NCP, was software that ran on a 37xx communications controller and managed communication with remote devices. NCP provided services comparable to the data link layer and Network Layer functions in the OSI model of a Wide area network. Overview The original IBM Network Control Program ran on the 3705-I and supported access to older devices by application programs using Telecommunications Access Method (TCAM). With the advent of Systems Network Architecture (SNA), NCP was enhanced to connect cluster controllers (such as the IBM 3270) to application programs using TCAM and later to application programs using Virtual Telecommunications Access Method (VTAM). Subsequent versions of NCP were released to run on the IBM 3704, IBM 3705-II, IBM 3725. IBM 3720, or IBM 3745 Communications Controllers, all of which SNA defined as a SNA Physical Unit Type 4 (PU4). A PU4 usually had SDLC links to remote cluster controllers (PU1/PU2) or to other PU4s. P ... [...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] |
Ethernet
Ethernet () is a family of wired computer networking technologies commonly used in local area networks (LAN), metropolitan area networks (MAN) and wide area networks (WAN). It was commercially introduced in 1980 and first standardized in 1983 as IEEE 802.3. Ethernet has since been refined to support higher bit rates, a greater number of nodes, and longer link distances, but retains much backward compatibility. Over time, Ethernet has largely replaced competing wired LAN technologies such as Token Ring, FDDI and ARCNET. The original 10BASE5 Ethernet uses coaxial cable as a shared medium, while the newer Ethernet variants use twisted pair and fiber optic links in conjunction with switches. Over the course of its history, Ethernet data transfer rates have been increased from the original to the latest , with rates up to under development. The Ethernet standards include several wiring and signaling variants of the OSI physical layer. Systems communicating over Ethernet ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Token Ring
Token Ring network IBM hermaphroditic connector with locking clip. Screen contacts are prominently visible, gold-plated signal contacts less so. Token Ring is a computer networking technology used to build local area networks. It was introduced by IBM in 1984, and standardized in 1989 as IEEE 802.5. It uses a special three-byte frame called a ''token'' that is passed around a logical ''ring'' of workstations or servers. This token passing is a channel access method providing fair access for all stations, and eliminating the collisions of contention-based access methods. Token Ring was a successful technology, particularly in corporate environments, but was gradually eclipsed by the later versions of Ethernet. History A wide range of different local area network technologies were developed in the early 1970s, of which one, the Cambridge Ring, had demonstrated the potential of a token passing ring topology, and many teams worldwide began working on their own implementations. ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Local Area Network
A local area network (LAN) is a computer network that interconnects computers within a limited area such as a residence, school, laboratory, university campus or office building. By contrast, a wide area network (WAN) not only covers a larger geographic distance, but also generally involves leased telecommunication circuits. Ethernet and Wi-Fi are the two most common technologies in use for local area networks. Historical network technologies include ARCNET, Token Ring and AppleTalk. History The increasing demand and usage of computers in universities and research labs in the late 1960s generated the need to provide high-speed interconnections between computer systems. A 1970 report from the Lawrence Radiation Laboratory detailing the growth of their "Octopus" network gave a good indication of the situation. A number of experimental and early commercial LAN technologies were developed in the 1970s. Cambridge Ring was developed at Cambridge University starting in 1974. Ethe ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Data-Link Switching
Data-Link Switching (DLSw) is a tunneling protocol designed to tunnel unroutable, non-IP based protocols such as IBM Systems Network Architecture (SNA) and NBF over an IP network. DLSw was initially documented in IETF RFC 1434 in 1993. In 1995 it was further documented in the IETF RFC 1795. DLSw version 2 was presented in 1997 in IETF RFC 2166 as an improvement to RFC 1795. Cisco Systems has its own proprietary extensions to DLSw in DLSw+. According to Cisco, DLSw+ is 100% IETF RFC 1795 compliant but includes some proprietary extensions that can be used when both devices are Cisco. Some organisations are starting to replace DLSw tunneling with the more modern Enterprise Extender (EE) protocol which is a feature of IBM APPN on z/OS systems. Microsoft refers to EE as IPDLC. Enterprise Extender uses UDP traffic at the transport layer rather than the network layer. Cisco deploy Enterprise Extender on their hardware via the IOS feature known as SNAsW (SNA Switch). See also *Microsoft ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Bisync
Binary Synchronous Communication (BSC or Bisync) is an IBM character-oriented, half-duplex link protocol, announced in 1967 after the introduction of System/360. It replaced the synchronous transmit-receive (STR) protocol used with second generation computers. The intent was that common link management rules could be used with three different character encodings for messages. Six-bit Transcode looked backwards to older systems; USASCII with 128 characters and EBCDIC with 256 characters looked forward. Transcode disappeared very quickly but the EBCDIC and USASCII dialects of Bisync continued in use. At one time Bisync was the most widely used communications protocol and is still in limited use in 2013. Framing Bisync differs from protocols that succeeded it in the complexity of message framing. Later protocols use a single framing scheme for all messages sent by the protocol. HDLC, Digital Data Communications Message Protocol (DDCMP), Point-to-Point Protocol (PPP), etc. e ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
.jpg "Click for more on -> Systems Network Architecture")
