Hi,

set up a new Shout Destination target for mailing and code "exectime +20% shout to <newdest>" in PostProc.

Or - if you forward/handle your alerts already with a script you could code a "exectime +20% shout to EM" from there.

Rg, Rolf

Yes you are right unfortunately CTM does not have a direct "shout Mail" option on the PostProc Panel.

The normal solution here is to setup a new Shout Destination ("ctmsys" from shell or Config Manager).

In general on the Shout Dest Panel you could set it up as type Mail or Program. With type mail you are limited regarding the customizations - you just add the needed email adr.

fe "ctmsys":

On the Job:

This gives you a mail:

Subject: Control-M Server: Shout by orderno: 00000iz9 testmsg

Body:

Mail message from CONTROL-M:

testmsg

If you need more customization (fe, if you need to feed some Autoedits to the mail) then you need to setup the Shout Dest as type "P" - here you specify the location to a script (which you have to write on your own). In the script you are free to do whatever you need - you get all the values from the "Message" part of the Jobdef as script paras.

Rg, Rolf

Haku,

What version are you running?

My print screen is from V7. On V8 you find it under "Actions" - Notifications before job completion - "Destination" is your new defined Shot dest

Haku,

Just a note....you can add the variables to the message.

CONTROL-M job %%JOBNAME in folder: %%SCHEDTAB Application: %%APPLIC, subapplication: %%APPLGROUP is running late.

Hi Haku,

First i should point out that Job's average execution time is not actually what you think it means.  Job's average execution time = Jobs execution time.  Where it says Exceeds average time it does mean Average Time.  The screenshot below shows you how to get it setup to shout when the current Execution time exceeds the jobs average execution time by 20 percent.  The Destination TEAM below is defined in a Shout Destination Table setup on the CTM server using the ctm_menu using option 5 -> 3 -> 1  Or you can use the CCM select Tools -> Alerts -> Shout Destinations Manager.  There is good information in the manual regarding shout destination tables.

Why use average time instead of hard-coded value in PostProcessing tab with Exectime >

For example, If Exectime > 120  (minutes), shout to DBA or Operations team. Using average will eventually cause problems if run time grows slowly over time but your SLA does not.

Nicholas,

You are correct,  Probably 90+ % of the time i hard code an exectime > xxx.  There are some cases where you know that the job will be growing incrementally throughout the year and you know that a hard coded time isnt going to cut it.  the > than a % gives a clean alternative option to allow intentional "run creep" to happen but still catch the extreme executions that literally stop your schedule.  Since Haku asked about % i gave him %

I have followed everything defined in your solution, BUT still not receiving email. -- Actually I don't even see any entry in the job log that indicates mail notification.

See attachment for details:

What solution ?

Hi Rahim,  Just a thought, 90% less than 38secs is 2.3 secs.  The job ran for 2 secs... probably didn't meet requirements.  Can you specify instead a lower percentage?

Hi,

Was this ever resolved? We have success with shouts for minutes, but not percentage over/under.

Thanks!