It would be nice if there were some sample code to demonstrate connecting to this new system service (*VMEVENT) and some sample records so that we cou ld get a feel for the kind of data and the level of effort to begin implementing this.
/Tom Kern On Tue, 11 Mar 2008 10:57:26 -0400, Alan Altmark <[EMAIL PROTECTED] > wrote: >You're right - type 04s are only created for incorrect passwords. Sorry >for the confusion. > >I suppose the easiest way, if your ESM doesn't do it for you, is to >connect to the z/VM 5.3 *VMEVENT system service and listen for LOGONs an d >LOGOFFs. When you connect, you'll receive a list of users who are alrea dy >logged on, so you can "catch up". > >*VMEVENT gives you other interesting events, including: >- a user has tripped the 15 minute self destruct timer >- a user has cancelled the self destruct >- user has loaded a disabled wait PSW >- soft abend of the user >- ... > >These are events that are not available anywhere else, though you will s ee >them on the HMC if you're using it to monitor virtual machine status. (T he >HMC can do the same things to a virtual machine it can do to an LPAR, >including monitoring with notification.) > >Alan Altmark >z/VM Development >IBM Endicott
