I have a CLEANLOG XEDIT macro to remove various messages from console logs. It shows a selection panel. Things one can remove: - All LOGON/LOGOFF messages - All or many RSCS messages - SCIF messages of users you indicate - Various VMOPER macro messages - ... It really deletes the lines from the log. No problem in our case as we do not really XEDIT a LOGFILE, it is meant to be called after we run LGOPER, an EXEC -with a panel- that allows one to select the date of the log, timespan, etc; LGOPER creates an empty -storage resident only- file with what you selected, its fmode is set to A, so a FILE or SAVE won't change the real log.
I'll send it to you for inspiration. It is however coded to handle VMOPER log files; PROP logfiles will be different in what if found where. 2008/7/9 Thomas Kern <[EMAIL PROTECTED]>: > In viewing the logs with xedit, you could do an ALL command with not > /ATTACH/ or not /DETACH/. That should help reduce what you need to look at. > > /Tom Kern > > Ray Waters wrote: >> >> DASD space is not the issue. While reviewing these logs, debugging >> other problems is slowed due to the volume of ATT/DET commands. Tapes >> being attached or detached is usually not a problem. >> >> Ray >> >> -----Original Message----- >> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >> Behalf Of Kris Buelens >> Sent: Wednesday, July 09, 2008 11:00 AM >> To: [email protected] >> Subject: Re: The Programmable Operator Facility >> >> In PROP, logging is all or nothing. VM:Operator has a NOLOG option, I >> don't know about IBM Operations Manager. >> >> At the other hand: DASD isn't that expensive, incomplete log files >> make debugging less easy. Alternatively, you could postprocess the >> log file of the previous day and code a PIPE filter to remove what you >> don't want to keep. >> > -- Kris Buelens, IBM Belgium, VM customer support
