I like to think adding ESALPS keeps it semi-vanilla? The monitor records have most of this, and most of it gets logged on the ESAOPER report. This report is mostly for configuration changes. So for example, any time a USER SHARE changes, this gets recorded to ESAOPER. Any processor event gets recorded, samples are:
- PR/SM time slice changed from dy -PR/SM time slice changed from '| - PR/SM time slice changed to dyna - PR/SM time slice changed to '|| - Processor configuration changed'); - CPU Capability changed from '|| - CPU Secondary Capability changed from '|| - VARY ONLINE PROCESSOR '|| - VARY OFFLINE PROCESSOR'|| there are many other configuration changes recorded for I/O, scheduler, others.... Anything missing? i don't get who delivered the command, just when issued and what the change is. Whenever i detect changes in configuration, they get recorded, so this is not just a "monitor configuration record", much more... >Date: Wed, 6 Dec 2006 13:58:36 -0500 >From: Jim Vincent <[EMAIL PROTECTED]>i >To: [email protected] > >I am just starting to dig, but thought I would toss this out to >the list. If someone enters a command like CP SET SHARE or CP >VARY PROCESSOR, are those logged anywhere? Are they in the >monitor data or accounting data? > >Assume a semi-vanilla z/VM 5.2 system with no ESM and no >third-party tools like VM:Manager... ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************
