WATFOR—The University of Waterloo FORTRAN IV compiler
Communications of the ACM
The simulation of time sharing systems
Communications of the ACM
Microprogamming under a page on demand strategy
Communications of the ACM
Description of a high capacity, fast turnaround university computing center
Communications of the ACM
PUFFT—The Purdue University fast FORTRAN translator
Communications of the ACM
CORC—the Cornell computing language
Communications of the ACM
Structure of TUCC: hardware and software
ACM-SE 6 Proceedings of the 6th annual Southeastern regional meeting of the Association for Computing Machinery and national meeting of Biomedical Computing - Volume 1
An appraisal of the Atlas supervisor
ACM '67 Proceedings of the 1967 22nd national conference
Bulk core in a 360/67 time-sharing system
AFIPS '67 (Fall) Proceedings of the November 14-16, 1967, fall joint computer conference
Operating systems architecture
AFIPS '70 (Spring) Proceedings of the May 5-7, 1970, spring joint computer conference
The management of a multi-level non-paged memory system
AFIPS '70 (Spring) Proceedings of the May 5-7, 1970, spring joint computer conference
AFIPS '70 (Fall) Proceedings of the November 17-19, 1970, fall joint computer conference
AFIPS '71 (Spring) Proceedings of the May 18-20, 1971, spring joint computer conference
Optimal sizing, loading and re-loading in a multi-level memory hierarchy system
AFIPS '71 (Spring) Proceedings of the May 18-20, 1971, spring joint computer conference
Experiments in page activity determination
AFIPS '72 (Spring) Proceedings of the May 16-18, 1972, spring joint computer conference
| Hi-index | 0.00 |
Operating System/360 was designed to meet a severe core-memory constraint: a 14K-bytes resident supervisor plus a repertoire of compilers, utility programs, sort programs, and application packages fitting into 18K bytes (approximately 4500 data words and executable instructions). Many supervisory functions included in the nucleus of pre-360 systems were repackaged into 1000-byte overlays for OS/360 (e.g. logic to OPEN and CLOSE files---hereafter called data sets, following OS/360 nomenclature). Specification of device type, buffering technique, and data set identification---which was assembled, compiled, or link-edited into many pre-360 application programs --- is deferrable in OS/360 until the data set is actually opened for processing, essentially "latest-possible binding of data-set attributes and processing mode" (cf. Part 3 of Reference 5 for a complete discussion).