×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hmm. My two years of high school programming (IBM VS-BASIC, with some FORTRAN, both G1 and WATFIV) were on a 370/135 running McGill University MUSIC, and we never had to worry about being swapped out while doing conversational I/O. There were front-end processors to take care of that.
Nor did I ever have to worry about that sort of thing at the University (various CDC Cybers running NOS, and a DEC PDP-11/70 running RSTS.
I never had to punch a single Hollerith card until I was back on a MUSIC system, doing a bit of work at my old high school (which by then had its own used 4341), and wanted a report to come out on the line printer, instead of on a much slower DECWriter (batch-submit from terminal sessions wasn't available).
It's a complete mystery to me, what people here are saying about having to jump through hoops to make terminal-based apps work on a mainframe: isn't the whole point of a timesharing OS, whether it uses sub-second timeslices, or it offloads terminal interaction to a front-end processor, and whether it's on a mainframe, a midrange, or even just a big micro, to create the illusion that each application has a whole box to itself?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.