Back when I was in high school, student accounts on the district's
student timeshare system (IBM 370/135 running McGill University MUSIC)
had concurrent sessions disabled by default, because there were
generally more students than terminals at any given time, and a student
using more than one terminal was effectively keeping at least one other
student off the system.
One of our customers (and only one) has concurrent terminal sessions
disabled by default. As one who can easily keep multiple terminal
sessions busy, I'm morbidly curious as to why, in an era when terminal
sessions are not a particularly limited resource, an installation would
do this.
Any insights?
--
JHHL
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.
midrange.com
