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.[1]
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. Polling and addressing of the cluster controllers was performed by the NCP without mainframe intervention.
In 2005 IBM introduced Communications Controller for Linux (CCL), a software product that allows an unmodified NCP to run on the mainframe, eliminating the need for a separate communications controller in some cases.
A remote NCP had no direct connection to a mainframe but was connected to a local NCP via one or more high-speed SDLC links.
Notes
^However, if NCP was generated with Partitioned Emulation Program (PEP), then the Emulator Program (EP) has its own block of I/O addresses, normally on a different channel from that used by the NCP proper. The EP part of a PEP was often used to communicate with the Message Control Program (MCP) provided by TCAM running in the mainframe as the interface with application programs.
W. S. Hobgood (1976). (PDF). Vol 15, No 1. IBM Systems Journal. Archived from the original on 2007-03-16. Retrieved 2006-08-26.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
March 03, 2023
network, control, program, this, article, about, software, arpanet, network, control, program, network, control, program, arpanet, software, that, 37xx, communications, controller, managed, communication, with, remote, devices, provided, services, comparable, . This article is about the IBM Network Control Program software For the ARPANET Network Control Program see Network Control Program ARPANET 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 1 Contents 1 Overview 2 Notes 3 References 4 Further readingOverview EditThe 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 Polling and addressing of the cluster controllers was performed by the NCP without mainframe intervention In 2005 IBM introduced Communications Controller for Linux CCL a software product that allows an unmodified NCP to run on the mainframe eliminating the need for a separate communications controller in some cases A local NCP connected to a System 370 channel via single NB 1 address A remote NCP had no direct connection to a mainframe but was connected to a local NCP via one or more high speed SDLC links Notes Edit However if NCP was generated with Partitioned Emulation Program PEP then the Emulator Program EP has its own block of I O addresses normally on a different channel from that used by the NCP proper The EP part of a PEP was often used to communicate with the Message Control Program MCP provided by TCAM running in the mainframe as the interface with application programs References Edit Microsoft SNA Functional Layers Retrieved Sep 7 2012 Further reading EditW S Hobgood 1976 The role of the Network Control Program in Systems Network Architecture PDF Vol 15 No 1 IBM Systems Journal Archived from the original on 2007 03 16 Retrieved 2006 08 26 a href Template Cite web html title Template Cite web cite web a CS1 maint bot original URL status unknown link Retrieved from https en wikipedia org w index php title IBM Network Control Program amp oldid 1128570038, wikipedia, wiki, book, books, library,
