Knowledge

RSCS

Source đź“ť

90:(CSC), asked Hendricks to find a way for the CSC machine to communicate with machines at IBM’s other Scientific Centers. CPREMOTE had taught Hendricks so much about how a communications facility would be used and what function was needed in such a facility, that he decided to discard it and begin again with a new design. After additional iterations, based on feedback from real users and contributed suggestions and code from around the company, Hendricks and Tim Hartmann, of the IBM Technology Data Center in Poughkeepsie, NY, produced RSCS, which went into operation within IBM in 1973. 193:
Remote Spooling and Communications Subsystem (RSCS). Together they form a general purpose tool for the delivery of the computing resources of the IBM System/ 370 machines to a wide variety of people and computers. ...RSCS is the operating system used to provide information transfer among machines linked with communications facilities." Details of the design of RSCS as a virtual machine subsystem are described in the IBM Systems Journal.
192:
described RSCS as an operating system and considered it an essential component of the VM/370 Time-Sharing System. "The Virtual Machine Facility/370, VM/370 for short, is a convenient name for three different operating systems: the Control Program (CP), the Conversational Monitor System (CMS), and the
116:
XLVI, in February, 1976, Hendricks and Hartmann reported that the network, which was now beginning to be called VNET, spanned the continent and connected 50 systems. By SHARE 52, in March, 1979, they reported that VNET connected 239 systems, in 38 U.S. cities and 10 other countries. “VNET passed 1000
222:
VNET was the first large-scale connectionless network, making it possible for a computer to join the network using dial-up lines, making connection inexpensive while ARPANET required dedicated 50kb lines at first (later raised to 230KB. Most leased lines at the time typically operated at a maximum
176:
states (as GulfNet). BITNET was also very popular in other parts of the world, especially in South America, where about 200 nodes were implemented and heavily used in the late 1980s and early 1990s. Over time, BITNET was eventually merged into the Internet. Newer versions of RSCS, as well as Jnet
128:
Due to the key role RSCS played in building networks, the line drivers became known as the "RSCS Protocols". The supported protocols were drawn from other programs. The CPREMOTE protocol may have been the very first symmetrical protocol (sometimes called a "balanced" protocol). To expand the RSCS
62:
The history of this program, and its influence on IBM and the IBM user community, is described in contemporaneous accounts and interviews by Melinda Varian. Technical goals and innovations are described by Creasy and by Hendricks and Hartmann in seminal papers. Among academic users, the same
177:
and the various UNIX NJE stacks, provided support for TCPNJE line drivers. Since most sites that were on BITNET also had access to the Internet, the BITNET links that were once ran over leased lines and dialup modems were tunneled over the Internet. It was also not uncommon to run NJE over
212:
or continuous network connections. Messages and files were transmitted in their entirety from one server to the next until reaching their destination. In case of a broken network connection RSCS would retain the message and retry transmission when the remote system became available.
93:
The first version of RSCS distributed outside of IBM (1975) was not a complete networking package. It included uncalled subroutines for functions such as store-and-forward that were included in the IBM internal version. The store-and-forward function was added in the
167:
in addition to DECnet (The VAX/VMS NJE protocol stack was known as Jnet). At its zenith around 1991, BITNET extended to almost 500 organizations and 3,000 nodes, all educational institutions. It spanned North America (in Canada it was known as NetNorth), Europe (as
117:
nodes in 1983 and 3000 nodes in 1989. It currently (1990s) connects somewhat more than 4000 nodes, about two-thirds of which are VM systems.” In comparison, by 1981 the ARPANET consisted of 213 host computers. Both ARPANET and VNET continued to grow rapidly.
27:
which accepts files transmitted to it from local or remote system and users and transmits them to destination local or remote users and systems. RSCS also transmits commands and messages among users and systems.
104:
Once those capabilities were added, “the network began to grow like crazy.” Although at first the IBM network depended on people going to their computer room and dialing a phone, it soon began to acquire
318: 79:, which he completed by mid-1969. CPREMOTE was the first example of a “service virtual machine” and was motivated partly by the desire to prove the usefulness of that concept. 366: 289:
A PRPQ (Programming Request for Price Quotation), was an IBM administrative term for software that was available but not fully supported as an IBM product
35:
and directly influenced both internet development and user acceptance of networking between independently managed organizations. RSCS was developed by
137:
Network Job Interface protocol, which enabled the network to grow rapidly. He later added the JES2 Network Job Entry as an RSCS/VNET line driver.
120:
By 1986, IBM’s Think magazine estimated that VNET was saving the company $ 150,000,000 per year as the result of increased productivity.
134: 51:. The network interfaces continued to be called the RSCS compatible protocols and were used to interconnect with IBM systems other than 229:
VNET was a true "distributed control" while ARPANET required a "control" center operated at Bolt, Beranek, and Newman in Cambridge, MA.
169: 490: 495: 500: 320:
Virtual Machine/ System Product Remote Spooling Communications Subsystem Networking Program Reference and Operations Manual
480: 178: 209: 148: 87: 485: 475: 336: 160: 98: 83: 52: 24: 75:
RSCS arose because people throughout IBM recognized a need to exchange files. Hendricks’s solution was
152: 226:
VNET employed a vastly simplified routing and path finding approach, later adopted for the Internet.
31:
RSCS is the software that powered the world’s largest network (or network of networks) prior to the
40: 277: 201: 159:
which was based on VNET. The first network link was between CUNY and Yale. The BITNET (RSCS)
113: 76: 442: 385: 426: 156: 36: 405: 163:
were eventually ported to non-IBM computer systems, and became widely implemented under
469: 362: 189: 173: 106: 337:
https://www.ibm.com/docs/en/zos/2.1.0?topic=functions-vtam-definitions-sna-nje
144: 32: 446: 389: 460: 197: 164: 143:
was a cooperative United States university network founded in 1981 by
429:; Hartmann, T.C. (1979). "Evolution of a Virtual Machine Subsystem". 140: 64: 47:
product and as an IBM internal network, it later became known as
205: 95: 48: 438: 381: 130: 56: 44: 23:
is a subsystem ("virtual machine" in VM terminology) of IBM's
101:, first for files, and then for messages and commands. 196:From a technical point of view, RSCS differed from 407:VM and the VM community, past present, and future 208:. Unlike ARPANET, it did not require dedicated 367:"The origin of the VM/370 time-sharing system" 8: 413:. SHARE 89. Atlanta, GA. Sessions 9059-9061 374:IBM Journal of Research & Development 17:Remote Spooling Communications Subsystem 263: 261: 239: 124:Other RSCS Protocol Compatible Networks 7: 204:" network, as such it was more like 133:, Hartmann reverse-engineered the 14: 200:in that it was a point-to-point " 67:and related networks worldwide. 404:Varian, Melinda (August 1997). 339:, VTAM definitions for SNA NJE 1: 210:Interface Message Processor 149:City University of New York 88:Cambridge Scientific Center 517: 172:), India (TIFR) and some 63:software was employed by 59:) and non-IBM computers. 317:IBM Corporation (1982). 491:History of the Internet 25:VM/370 operating system 496:IBM mainframe software 267:Hendricks and Hartmann 501:VM (operating system) 481:Computer networking 447:10.1147/sj.181.0111 431:IBM Systems Journal 390:10.1147/rd.255.0483 129:network to include 86:, Manager of IBM’s 84:Norman L. Rasmussen 55:systems (typically 365:(September 1981). 223:rate of 9600 baud. 486:Computer printing 278:Nicolas Rasmussen 202:store and forward 508: 476:Remote job entry 450: 422: 420: 418: 412: 400: 398: 396: 371: 349: 346: 340: 334: 328: 327: 325: 314: 308: 305: 299: 296: 290: 287: 281: 274: 268: 265: 256: 253: 247: 244: 217:VNET vs. ARPANET 185:Technical Issues 516: 515: 511: 510: 509: 507: 506: 505: 466: 465: 457: 427:Hendricks, E.C. 425: 416: 414: 410: 403: 394: 392: 369: 361: 358: 353: 352: 347: 343: 335: 331: 323: 316: 315: 311: 306: 302: 297: 293: 288: 284: 275: 271: 266: 259: 254: 250: 245: 241: 236: 219: 187: 157:Yale University 153:Greydon Freeman 126: 73: 37:Edson Hendricks 12: 11: 5: 514: 512: 504: 503: 498: 493: 488: 483: 478: 468: 467: 464: 463: 456: 453: 452: 451: 423: 401: 357: 354: 351: 350: 341: 329: 309: 300: 291: 282: 276:The father of 269: 257: 248: 238: 237: 235: 232: 231: 230: 227: 224: 218: 215: 186: 183: 125: 122: 72: 69: 43:. Both as an 13: 10: 9: 6: 4: 3: 2: 513: 502: 499: 497: 494: 492: 489: 487: 484: 482: 479: 477: 474: 473: 471: 462: 459: 458: 454: 448: 444: 440: 436: 432: 428: 424: 409: 408: 402: 391: 387: 383: 379: 375: 368: 364: 360: 359: 355: 348:Creasy, p 483 345: 342: 338: 333: 330: 322: 321: 313: 310: 307:Varian, p. 42 304: 301: 298:Varian, p. 41 295: 292: 286: 283: 279: 273: 270: 264: 262: 258: 252: 249: 243: 240: 233: 228: 225: 221: 220: 216: 214: 211: 207: 203: 199: 194: 191: 184: 182: 180: 175: 171: 166: 162: 158: 154: 150: 146: 142: 138: 136: 132: 123: 121: 118: 115: 110: 108: 102: 100: 97: 91: 89: 85: 80: 78: 70: 68: 66: 60: 58: 54: 50: 46: 42: 41:T.C. Hartmann 38: 34: 29: 26: 22: 18: 434: 430: 415:. Retrieved 406: 395:November 19, 393:. Retrieved 377: 373: 363:Creasy, R.J. 344: 332: 319: 312: 303: 294: 285: 272: 251: 242: 195: 190:R. J. Creasy 188: 174:Persian Gulf 139: 127: 119: 111: 107:leased lines 103: 92: 81: 74: 61: 30: 20: 16: 15: 384:: 483–490. 151:(CUNY) and 470:Categories 417:October 9, 356:References 71:Background 161:protocols 145:Ira Fuchs 82:In 1971, 455:See also 77:CPREMOTE 33:Internet 461:NETDATA 441:: 122. 198:ARPANET 165:VAX/VMS 147:at the 255:Creasy 246:Varian 141:BITNET 65:BITNET 437:(1). 411:(PDF) 380:(5). 370:(PDF) 324:(PDF) 234:Notes 114:SHARE 419:2013 397:2011 206:UUCP 170:EARN 135:HASP 99:PRPQ 96:VNET 49:VNET 39:and 21:RSCS 443:doi 439:IBM 386:doi 382:IBM 181:. 179:SNA 155:at 131:MVS 112:At 57:MVS 45:IBM 19:or 472:: 435:18 433:. 378:25 376:. 372:. 260:^ 109:. 53:VM 449:. 445:: 421:. 399:. 388:: 326:. 280:.

Index

VM/370 operating system
Internet
Edson Hendricks
T.C. Hartmann
IBM
VNET
VM
MVS
BITNET
CPREMOTE
Norman L. Rasmussen
Cambridge Scientific Center
VNET
PRPQ
leased lines
SHARE
MVS
HASP
BITNET
Ira Fuchs
City University of New York
Greydon Freeman
Yale University
protocols
VAX/VMS
EARN
Persian Gulf
SNA
R. J. Creasy
ARPANET

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑