Hi All,
I am using Control-M 7.0 and facing problem in using Automated E-mail shout in both "STEPS" Tab and in "Post-Processing" Tab.
Below is the stepwise Scenario :
1) I have the File-watcher job which waits for one of the files every day.
2) File-watcher should wait for the file for specific time period in a day.
3) If the File has not arrived in that Time range,( let job be in Executing state) then Job has to shout a message to specific Mail address defined either in STEPS tab or from Post-Processing.
4) I tried using "Late Time" format as the shout subparameter but din't worked.
Please let me know how to define the above scenario in a File-Watcher job.
Thanks,
MDude
Define shout message for File-Watcher job in Post-processing
- MaheshDude
- Nouveau
- Posts: 28
- Joined: 12 Dec 2011 12:00
- MaheshDude
- Nouveau
- Posts: 28
- Joined: 12 Dec 2011 12:00
Define shout message for File-Watcher job in Post-processing
Hi, Thanks to your reply,
I tried the "Late Time" parameter again and it worked for me. I mean i am able to shout the message to specific mail group once the File watcher reaches the End time specified in the PostProc Tab.
Now, my other scenario is :
1) If file did not come till the END TIME specified, File watcher should fail.
2) Also it should pass the Out condition to some other job ( i.e not the regular pattern like, if the file is available and file watcher "ENDED OKAY" and trigger the next dependent job.
Thanks
I tried the "Late Time" parameter again and it worked for me. I mean i am able to shout the message to specific mail group once the File watcher reaches the End time specified in the PostProc Tab.
Now, my other scenario is :
1) If file did not come till the END TIME specified, File watcher should fail.
2) Also it should pass the Out condition to some other job ( i.e not the regular pattern like, if the file is available and file watcher "ENDED OKAY" and trigger the next dependent job.
Thanks
passing the condition to the next job you can do from the step tab
on stmt=* code = compstat > 0
do condition <condition> sign +
compstat > 0 will ensure anything other than sucess.
NOTe : I am yet to find out how to make the job fail when it reaches the END time , but i have a doubt that at reaching the end time the job would automatically fail .
if u use ctmfw 0 10 60 3 fr eg would fail after the 3 loop
on stmt=* code = compstat > 0
do condition <condition> sign +
compstat > 0 will ensure anything other than sucess.
NOTe : I am yet to find out how to make the job fail when it reaches the END time , but i have a doubt that at reaching the end time the job would automatically fail .
if u use ctmfw 0 10 60 3 fr eg would fail after the 3 loop
Anirudh
- MaheshDude
- Nouveau
- Posts: 28
- Joined: 12 Dec 2011 12:00
Hi Anirudh,
Thanks for the clue.
I actually, tried the below steps and able to resolve the issue.
STEPS :
1. IN file-watch panel i gave "<full> CREATE 0 60 10 3 N 5 NOW 0 NO_MIN_AGE NO_MAX_AGE"
2. IN STEP tab, as below:
A. on stmt=* code = OK
Do mail <Mail>
B. on stmt=* code = compstat > 0
Do Condition <condition> sign +
So, according to STEP 2 if the File is available, then file watcher (code = OK) will pass the condition to next dependent job as per STEP A.
Where as, if the File is not available, then File-Watcher will fail, once it reaches the end time. Now,as per STEP B, it will pass the <condition> given in the DO Statement and will bypass it to some other job which suppose to trigger. Thus avoiding the regualr pattern run.
Thanks Again
MDUDE
Thanks for the clue.
I actually, tried the below steps and able to resolve the issue.
STEPS :
1. IN file-watch panel i gave "<full> CREATE 0 60 10 3 N 5 NOW 0 NO_MIN_AGE NO_MAX_AGE"
2. IN STEP tab, as below:
A. on stmt=* code = OK
Do mail <Mail>
B. on stmt=* code = compstat > 0
Do Condition <condition> sign +
So, according to STEP 2 if the File is available, then file watcher (code = OK) will pass the condition to next dependent job as per STEP A.
Where as, if the File is not available, then File-Watcher will fail, once it reaches the end time. Now,as per STEP B, it will pass the <condition> given in the DO Statement and will bypass it to some other job which suppose to trigger. Thus avoiding the regualr pattern run.
Thanks Again
MDUDE