Reader Feedback: Programming E-mail Notification When a Robot/SCHEDULE Job Fails

Published: April 15, 2009

Dear Joe,

I appreciate your recent Robot/SCHEDULE article describing code that users can write to program e-mail notification when a Robot/SCHEDULE job fails. For further clarification, I would like to mention two points:

First, Robot/SCHEDULE offers multiple ways besides abnormal end of job to help users keep informed about their job schedule. For example, Robot/SCHEDULE provides warning messages when calendars and date objects are about to expire, and tracks events when jobs are skipped or delayed because of resource availability. And, for users worried about Service Level Agreements, Robot/SCHEDULE job monitors can track when a job is late, ran too quickly (indicating a problem), or did not start on time.

Second, for Robot/SCHEDULE users who may not be interested in programming, Robot/ALERT offers an easier way to set up notification. Robot/ALERT works closely with Robot/SCHEDULE to automatically notify users when a job ends abnormally, or encounters conditions such as warning events, by sending a pager, text, or e-mail message as soon as the event occurs.

Robot/ALERT has been handling notification issues for more than 15 years and offers the following benefits:

• An easy-to-use menu and command interface
• Support for multiple protocols: TAP, SMTP, SNPP, SMS, GSM, and SNMP
• Distribution lists for escalation
• Time of day, or day of the week notification
• Automatic system, job, date, and time stamps
• A detailed history of e-mail and pager messages

Robot/SCHEDULE and Robot/ALERT work together as a simple, effective way to create and maintain an automated e-mail or pager notification process for job scheduling.

Tom Huntington
Vice President of Technical Services
Help/Systems

RELATED STORY

Catching Robot/SCHEDULE Job Failures As They Happen

                     Post this story to del.icio.us
               Post this story to Digg
    Post this story to Slashdot