Re: Signal support

[David Boyes]

Title: RE: Signal support

And once you’re running CMS multitasking, it’s not really CMS any more, although that’s an interesting argument: adding it to the CMS MT library and providing a thread automatically that waited for the signal and then drove the CMS MT termination code for MT apps.   That much development is probably beyond what we can ask IBM to do reasonably, I’d think. Putting it into CMS would be a pretty major internal change that messes with a lot of longstanding assumptions about CMS internals. The number of CMS MT programs is much smaller, and the number of non-IBM GCS programs is even smaller than that, so you could probably do it safely there, but the applications that would benefit are the ones we’ve been talking about here (RSCS, RACF, TCPIP, etc) which could be enabled much easier by direct modification.   David Boyes Sine Nomine Associates From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard Sent: Wednesday, August 09, 2006 2:45 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Signal support   RSCS is in the GCS group, not a CMS application.   Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]On Behalf Of Huegel, Thomas Sent: Wednesday, August 09, 2006 11:28 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Signal support Maybe the requirement should to put the Signal Support directly into the CMS Nucleus, that way applications that run under CMS wouldn't need to be changed.. or