Cisco Cisco Workload Automation 6.3 User Guide

Page of 78
53
 
Defining Actions Based on Job Conditions
Understanding Actions
Job – CWA can initiate automated job recovery procedures with a job action. The new job action also allows you to 
override certain command parameter values at submission time.
Variable – This variable update action updates user-defined variables. Since jobs can be dependent on variable 
values, this action can be used to start a job based on a wide selection of events experienced by another job which 
sets the variable. 
Log – The log message action posts a user-defined message to the CWA logging facility and optionally to the NT 
Application Events log, viewable from the Logs window and the NT Event Viewer (respectively).
Creating an Alert Action
In the following exercise, you define an action that sends an alert to the Job Activity window when the job EDI_Download 
(created in the previous chapter) ends with a Completed Abnormally status.
To create an Alert action:
1.
In the Navigator pane, select Definitions>Actions.
The Actions window displays.
2.
Double-click Alert to display the Alert window.
3.
In the CWA toolbar, click the Add  
button.
The Action Definition:Alert dialog displays.
4.
Type the following message and select the variables shown in angle brackets from the Variables list. The variables 
appear between the brackets as <variable>.
The Job <Jobname>, owned by <JobOwner> went to <JobStatus> status on <SysDate.M/d/yy>. <JobOwner>’s 
pager number is <JobPager>.
When this action is triggered, an alert record is sent to the Job Activity console for the operator to take action. 
5.
Click OK to accept the action.
The action is displayed in the Actions window.
Associating the Action to the Job
You can assign the action to the EDI_Download job through the Job Events dialog.
To associate the action to the job:
1.
In the Navigator pane, select Definitions>Events to display the Events window.
2.
Double-click Job Events to display the Job Events window.
Variable
Path
Description
<JobName>
Job Variables\JobNAME
The name of the job that triggered the action.
<JobOwner>
Job Variables\JobOWNER
The name of the user that owns the job.
<JobStatus>
Job Variables\JobSTATUS
The status the Job is in at the time of the message.
<SysDate.M/d/yy>
System Variables\System 
Date\M/d/yy
The day, month, date, year action was triggered.
<Job Pager>
Job Variables Owner’s 
Pager Number
The pager number of the owner.