Share: |


-by Joe Goldberg, Lead Technical Marketing Consultant, Control-M Solutions Marketing, BMC Software Inc.

 

When jobs fail, BMC Control-M provides a variety of notification options such as sending email or opening Remedy incidents.

 

However, events don’t have to be only errors and DO MAIL, DO REMEDY and WHEN OK are not your only alerting options.

 

Shout Destinations give you almost unlimited options for what you can do when “events” occur in Control-M jobs.

 

The Shout Destination table allows you to define your own logical destinations and even to modify these on the fly. So let’s say you want to send an email to the on call programmer by using destination ONCALL  but you wish to change who that person is from time to time (maybe shift to shift or day to day). You can create multiple tables and switch them at the beginning of each shift (run  the “ctmshtb” utility for Control-M/Server or the Modify command with the NEWDEST parameter for Control-M for z/OS).

 

ctmshtb SHIFT001            Run this at 7:00 to activate the Shift 1 Destination Table that defines

   ONCALL as Joe_smith@mycompany.com

 

ctmshtb SHIFT002            Run this at 19:00 to activate the Shift21 Destination Table that defines

      ONCALL as jack_brown@myafterhoursserviceprovider.com

 

What if you want to run a program or a script when a job ends? However, the action is not one that is directly part of the business process. Or perhaps you want to perform an action that Control-M does not natively support? You can define a custom logical destination and SHOUT to it. If you need to pass job attributes to the program or script, you can imbed them in the shout message using auto-edit variables.

 

Let’s take a look at a simple example. You have a data validation application that runs on a regular basis and returns a checksum value for each execution that is important to the Finance Department. These users need to see 10 to 20 results for a particular date and time and would prefer to keep a running log file rather than searching through dozens of emails. The value we want is returned as the completion status of the application. We can see the SHOUT, which includes the %%COMPSTAT AutoEdit variable, in the job definition as follows:

 

Snap8.jpg

 

In this example, we have created a custom destination called LOG2FILE. When a shout to this destination is performed, a script is run and the SHOUT message text, which includes the %%COMPSTAT AutoEdit variable, is included as a parameter.

 

This destination is added to the active Shout Destination Table via the Control-M Configuration Manager (CCM). Right click on a Control-M/Server and select Shout Destinations Manager to view thHere ise dialogs below.

Snap10.jpg

 

The script specified as the "value" is listed here:

@echo off
echo %2 >> D:\Users\Logs\OurFile.txt

 

Shout destinations have been used to open incidents in help desk tools, to collect information as we saw above and to “annotate” job execution in the Control-M log (use the “Log destination type).

Please share your experiences of how you have used Shout Destinations in your environment.

  

The postings in this blog are my own and do not necessarily represent the opinions or positions of BMC Software