*** Welcome to piglix ***

IBM 3790


The IBM 3790 Communications System, developed by IBM's Data Processing Division (DPD), was announced in 1975. It was one of the first distributed computing platforms. The 3790 preceded the IBM 8100, announced in 1979.

It was designed to be installed in branch offices, stores, subsidiaries, etc., and to be connected to the central host mainframe, using IBM Systems Network Architecture (SNA).

Although its successor's role in distributed data processing was said to be "a turning point in the general direction of worldwide computer development," the 3790 was described by Datamation in March 1979 as "less than successful.".

IBM described it as "a programmable, operator oriented terminal system."

The 3790 supported

The base unit of the 3790 was the IBM 3791 programmable control unit, which was offered as a choice of:

Attached to the 3791 were:

The 3790 failed to achieve the success IBM intended, due to several issues. It had a complex programming language, The 3790 Macro Assembler, and the customers found it difficult to deploy applications on it. The Macro Assembler ran only on an IBM mainframe and then the compiled and linked object was moved to the 3790 for testing.

The 3790 was designed as a departmental processor, but the requirement for an IBM mainframe development environment inhibited adoption in its target market of mid-size companies. The result was lackluster interest in the product. In addition the 3790 was priced higher than minicomputers of comparable processing power.

One of the products IBM released to help developers was Program Validation Services (PVS). With PVS, one could test a program in the mainframe environment using scripts. The scripts were cumbersome to create, and prone to errors. Since mainframe time was expensive and often difficult to obtain very few programmers used PVS for anything other than initial testing.

The manual for the Macro Assembler was bulky (about 4 inches thick) and difficult to use as a reference. Another programming issue was code design and size; the hardware architecture loaded code into memory on 2k segments, for optimal execution time it was critical to ensure that processing intensive loops did not cross the segment boundary and incur delays swapping segments in and out of memory.

IBM recognized the problems with the Macro Assembler and created an automated program generator named DMS. DMS later became Cross System Product (CSP) on the 8100. DMS was essentially a screen painter; it could do simple edits such as field range checking or numeric tests but more complex logic still had to be coded using the Macro Assembler.


...
Wikipedia

...