Matthew, Using TSM Operational Reporting, under the hourly default monitoring report, we added in a new Variable ANR9999
select count(*) as ANR9999 from actlog where msgno=9999 and date_time between current_timestamp- 1 hour and current_timestamp Then with an active rule if ANR9999>0 then send out an email alert. This will notify you within the hour of an ANR9999 message occurring. You will still have to query the activity log and interpret the message and then determine the action. TSM OR is Windows specific. Unix shell scripts & crontab could be used to develop a similar outcome. Leigh -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Large, M (Matthew) Sent: 14 August 2006 16:24 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Alerting on ANR9999D Afternoon Richard, Yep, you just confirmed my suspicions. Just had to make sure I wasn't blindly missing another solution (well documented ANR9999D guide would be a dream..) More training for the OPS! Cheers, Matthew -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 14 August 2006 13:52 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Alerting on ANR9999D On Aug 14, 2006, at 6:59 AM, Large, M (Matthew) wrote: > ...How do you alert against these unpredictable messages? Good morning, Matthew - Your adjective adeptly summarizes the situation: these messages are unpredictable, being Dignostic messages to provide internals info to allow TSM Support personnel to pursue a fuzzy situation. Once a cause can be nailed down per a solid customer event, the situation can either be resolved and become a footnote in history, or be formalized as a standard message to describe a reasonable thing which may occur from time to time. I would not look for a definitive explanation of an ANR9999D message, then. In writing an Ops guide, I would expect ANR9999D messages to be referred to the TSM administrator for pursuit, rather than being handled by an operator, as these messages may indicate issues which go beyond a simple remediation step, and likely need to be pursued with the vendor. Richard Sims _____________________________________________________________ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________