IBM Data Communications: A Quarter Century of Evolution and Progress

Jarema, David R.; Sussenguth, Edward H.

doi:10.1147/rd.255.0391

Cited by 13 publications

(3 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, a message destined for destination subarea 11 will be placed on an outbound TG which will initially be sent to subarea 3, i.e., TG 1-3. Then the routing table in subarea 3 will forward the message on the TG specified in its table. From the routing table of Figure 14, we can see a definite pattern of TG usage in relation to specific sets of subarea nodes.…”

Section: Four Route Numbers At a Timementioning

confidence: 99%

SNA routing: Past, present, and possible future

1983

View full text Add to dashboard Cite

This paper reviews the evolution of routing mechanisms in IBM's Systems Network Architecture (SNA) since its inception in 1974 to the present. Routing mechanisms are related to changes in the application and communications environment. Also discussed are possible evolutionary paths that may be taken in the future to address the problems of large heterogeneous networks. This paper traces the evolution of SNA routing from adsiract, but no other portions, of this paper may be copied or distributed royalty free without further permission by computerpresent and speculates on possible directions that republish any other portion of this paper must be obtained from may be taken to meet future needs. In addition to the Editor. _the introduction Of the architecture in 1974 to the based and other information-service systems. Permission to IBM SYSTEMS JOURNAL,

show abstract

Section: Four Route Numbers At a Timementioning

confidence: 99%

SNA routing: Past, present, and possible future

1983

View full text Add to dashboard Cite

show abstract

“…and physically carried to a paper tape transmit-Examples of computer based message switches ter for onward transmission. The advantages of introduced during the early 1960s were those built and operated by the Collins Radio Company (Atwood et al 1964) and systems for private networks such as the IBM 1050 data communications system announced in 1963 (Jarema and Sussenguth 1981). The first commercial British system, based on the ICT 1900 series computer, was announced in 1966 (Tomkins 1966).…”

Section: Introduction Introductionmentioning

confidence: 99%

Data Communications at the National Physical Laboratory (1965-1975)

Campbell-Kelly

1987

IEEE Annals Hist. Comput.

View full text Add to dashboard Cite

“…I suggest that it is conceptually useful, then, to instead consider "synchronous" communication as corresponding to a state of waiting on behalf of the sender or receiver: a situation in which a sender must wait for something to be fully received, and a receiver must wait for something to be fully sent. 9 A model for this might be the standard "bisync" data communications of late-1960s IBM terminals, in which the terminal and mainframe maintain a back-and-forth dialogue on a leased communications line; one is always "blocked" waiting for the other to send or receive(Jarema and Sussenguth 1981). Another common form of contact synchrony is isochrony, in which communication is consistently "clocked" by pulses separated by an equal interval of time, produced by a clock generator using, e.g., a crystal oscillator.…”

mentioning

confidence: 99%

Middleware’s Message: the Financial Technics of Codata

Castelle

2019

Philos. Technol.

View full text Add to dashboard Cite

In this paper, I will argue for the relevance of certain distinctive features of messaging systems, namely those in which data (a) can be sent and received asynchronously, (b) can be sent to multiple simultaneous recipients and (c) is received as a "potentially infinite" flow of unpredictable events. I will describe the social technology of the stock ticker, a telegraphic device introduced at the New York Stock Exchange in the 1860s, with reference to early twentieth century philosophers of synchronous experience (Bergson), simultaneous sign interpretations (Mead and Peirce), and flows of discrete events (Bachelard). Then, I will show how the ticker's data flows developed into the 1990s-era technologies of message queues and message brokers, which distinguished themselves through their asynchronous implementation of ticker-like message feeds sent between otherwise incompatible computers and terminals. These latter systems' characteristic "publish/subscribe" communication pattern was one in which conceptually centralized (if logically distributed) flows of messages would be "published," and for which "subscribers" would be spontaneously notified when events of interest occurred. This paradigm-common to the so-called "message-oriented middleware" systems of the late 1990s-would re-emerge in different asynchronous distributed system contexts over the following decades, from "push media" to Twitter to the Internet of Things.

show abstract

IBM Data Communications: A Quarter Century of Evolution and Progress

Cited by 13 publications

References 18 publications

SNA routing: Past, present, and possible future

SNA routing: Past, present, and possible future

Data Communications at the National Physical Laboratory (1965-1975)

Middleware’s Message: the Financial Technics of Codata

Contact Info

Product

Resources

About