Kbase P105832: Fathom Management: custom perl script calling the Default_Mail_Action on exit code
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/10/2008 |
|
Status: Verified
SYMPTOM(s):
custom perl script calling the Default_Mail_Action on exit code
To be able to send an alert based on the exit status of a job
custom email Alert: Default_Mail_Action
But the email received doesn't contain the custom email Alert detail
in the admserv.log logfile, it does say it send the custom email Alert: Default_Mail_Action
But the email received doesn't contain the custom email Alert
Default_Mail_Action
FACT(s) (Environment):
Fathom Management 3.0A
All Supported Operating Systems
CAUSE:
There is a difference between Action and Alert type of mail messages received, since they are different features.
The issue related to the difference between using the Default_Mail_Action for a Job Completion Action or a Job Alert Definition. The two cases are handled differently in the mail code to populate the body of the email.
The exit status can be used to chain jobs (command actions) together depending on the exit status of the previous job. It can't send alert information because it isn't an alert and does not have that kind of information. All the alert information is not applicable for a Job Completion Action since there is no alert context to include whereas in the Job Alert Definition, the alert is fired which results in the Default_Mail_Action.
FIX:
Alter the perl script by adding the 'fathom -firealert' option, in the section where the alert is needed, on other words; firing the alert directly from the job when it has failed
for example:
system("C:\\Progress\\Fathom30A\\bin\\fathom -firealert Backup_Failed -resource $DATABASE");