How do we clean up unreasonably large numbers of duplicate Incident Log entries? Is there a good programmatic way to do it?
Aside from assigning the virtual equivalent of making somebody write on the chalkboard "I will not leave MATCHLIM undefined" 65535 times, telling them to clean up each Incident Log entry one by one. I'd also like to be able to easily locate all the Incident Log entries that don't have SVC dumps any more because somebody simply deleted them. I suppose one could hack into the /var directory and figure it out but I already tried similar things and broke my sandbox repeatedly. If nobody has such a thing, I'll take another run at it. Thomas Ambros Operating Systems and Connectivity Engineering 518-436-6433 Email Classification: KeyCorp Public </pre> This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or redisclose such information for any purpose other than to provide the services for which you are receiving the information. 127 Public Square, Cleveland, OH 44114 <pre> If you prefer not to receive future e-mail offers for products or services from Key send an e-mail to mailto:[email protected] with 'No Promotional E-mails' in the SUBJECT line. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
