On Wednesday, 08/27/2008 at 10:04 EDT, "John P. Baker" <[EMAIL PROTECTED]> wrote: > For example, let's say that we create an *NOTIFY system service. > > A virtual machine, appropriately authorized is allowed to connect to the > *NOTIFY service, and by sending properly constructed messages, register its > desire to begin receiving, or to discontinue receiving, specific types of > event notifications. Certainly, LOGON and LOGOFF notifications should be > available. Other event types come to mind, such as varying a central > processor online or offline, or varying a device online or offline. I feel > certain that others here can recommend other event types that should be > monitorable. > > Then, whenever an event of the requested type occurs, all registered > listeners would receive the notification on the *NOTIFY path. > > This would at least provide a mechanism by which one of your requirements > could be addressed.
Gary's requirement to know when a guest has logged off, re-IPLed or otherwise has been reset is handled by IUCV itself. BTW, z/VM already has a *VMEVENT system service that will tell you about all virtual machines (in general) and their state changes. Over time, more system-level events will be added. In the meantime, CPU changes would be in *MONITOR. Alan Altmark z/VM Development IBM Endicott
