If you are ONLY looking to see what the user entered from the console (and keep in mind, you won't see anything issued from full-screen write environments like XEDIT/filelist/rdrlist, etc.) this does indeed get around the problems associated with a user mucking with console spooling.
I guess it really all depends on what is being asked for. Perhaps Chaitra can provide more specific details. Michael Coffin, President MC Consulting Company, Inc. 57 Tamarack Drive Stoughton, Massachusetts 02072 Voice: (781) 344-9837 FAX: (781) 344-7683 [EMAIL PROTECTED] www.mccci.com -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ron Schmiedge Sent: Friday, June 15, 2007 11:43 AM To: [email protected] Subject: Re: Regarding Event logging in VM > > We need to know > (a) what is meant by "track" (securely audit? all types of guests?) > (b) what is meant by "all" (highly unlikely as it isn't practical) > (c) what is meant by "activities" > > I'm comfortable that we have a handle on "the". :-) > > Alan Altmark > z/VM Development > IBM Endicott > LOL! Perhaps having a second userid defined as an OBSERVER for the first userid will suffice, too (once all the definitions are gathered).
