FMS was a different operating system, and the only OSs that I know of on the 7000 series to support multiprogramming were CTSS and some on Stretch. OS/360 supported multiprogramming and time sharing without DAT.
Could be an instruction for the CE, could be an unintended instruction. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Thursday, March 3, 2022 2:16 PM To: [email protected] Subject: Re: S0C4 pic 4 On Thu, 3 Mar 2022 18:27:54 +0000, Seymour J Metz wrote: >There was only one that I know of: IBM 7040/7044 Operating System (16K32K) - >7040-PR-150; basically IBSYS/IBJOB. Whether they used it or ran stand-alone I >don't know. > IIRC, FMS didn't multi-process jobs. I doubt that IBSYS was different -- tape ruled and no DAT. Interpreters can provide multi-processing -- GE-Dartmouth provided time sharing with no hardware memory protection, and I encountered a Data General system that did likewise, decoding 16 110-baud RS-232 lines with CPU timing! I suspect that setting bad parity supported hardware diagnostics. >________________________________________ >From: Paul Gilmartin >Sent: Thursday, March 3, 2022 10:47 AM >> >>There used to be a student compiler for FORTRAN IV that initialized storage >>to bad parity and put out an "uninitialized" message if you read that storage >>before you set it. >> >What hardware+OS supports that? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
