Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!decwrl!ucbvax!VTVM1.CC.VT.EDU!VALDIS
From: VALDIS@VTVM1.CC.VT.EDU (Valdis Kletnieks)
Newsgroups: comp.lang.asm370
Subject: Re: Interrupt case study stuff
Message-ID: <9007301631.AA22683@ucbvax.Berkeley.EDU>
Date: 30 Jul 90 16:26:27 GMT
References: <PHIL%VMD.CSO.UIUC.EDU@OHSTVMA.IRCC.OHIO-STATE.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List
              <ASM370@OHSTVMA.BITNET>
Distribution: inet
Organization: The Internet
Lines: 14

On Fri, 27 Jul 90 18:09:00 CDT Phil Howard said:
>Good operating systems designed for multiple concurrent activity, of course,
>do just this kind of thing.  CMS imposes different constraints.  You can
>easily get into a "hang" situation where some CMS routine just loaded a
>wait state PSW instead of jumping to a dispatcher, which it knows nothing
>about.  To make CMS fully multi-tasking requires redesigning CMS.
Phil:

See sessions O714 and O715 ("Towards a Multitasking CMS - DIalog with IBM")
to be presented at SHARE 75 in New Orleans in 2 weeks or so.

                                  Valdis Kletnieks
                                  Computer Systems Engineer
                                  Virginia Tech