System/370

(redirected from 370 architecture)

System/370

(hardware, IBM)
(S/370) An IBM mainframe computer introduced in 1970 as a successor to the IBM 360. Enhancements included the ability to support virtual memory and improved main storage. Two models were available initially: 165 and 155, with cycle times of 80 and 115 nanoseconds.

Press Release.
This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)

System/370

The IBM mainframe line that superseded System/360. Introduced in 1970, the System/370 added virtual memory and other enhancements. In the early 1980s, IBM added Extended Architecture (XA) to the series, featuring I/O enhancements and increased addressing from 24 to 31 bits. In the late 1980s, it debuted the Enterprise System Architecture (ESA), which added more registers and address modes.

The 370 architecture was brought down to the PC level in 1983 with the PC XT/370, and then again in 1989 with the VM/SP Technical Workstation. See System/360, System/390 and IBM mainframes.


System/370
As impressive as this Model 155 was, there is more computational power in any modern personal computer. Nevertheless, machines of this type routinely processed millions of records for the world's largest companies. They were doing real "data processing," not graphics processing for the user interface, which swallows up most of a computer's machine cycles these days. (Image courtesy of IBM.)
Copyright © 1981-2019 by The Computer Language Company Inc. All Rights reserved. THIS DEFINITION IS FOR PERSONAL USE ONLY. All other reproduction is strictly prohibited without permission from the publisher.
References in periodicals archive ?
The socket 370 architecture was selected for the processor because of long-term availability and relatively low cost.
BARROWS: We have said there will be one 370 architecture data center domestically.
We narrowed these 164 proposals down to 20 or 30 viable instructions and finally included half a dozen of them in the 370 architecture. AS What types of analysis have you done of the use of the 360/370 architecture, and how has this analysis affected the implementation of specific models?