Cisco Cisco Workload Automation 6.3 Betriebsanweisung

Events

Event Types



– The name of the action. 

If an action triggered is a job action, you can display additional details about the job that was triggered. 

The Triggered Details dialog displays by double-clicking on a trigger listed on the Triggered Actions page of the Trigger 
Details dialog or by selecting a trigger and selecting the Job Details option from the context menu. You can study details 
about the job that was triggered by the event from this dialog.

Right-click the job to display a context menu. You can update the details about the job by clicking the 

 option.

Exit Codes Tab

This tab displays in the 

 dialog only if the 

 option 

is selected in the 

field. If you are creating a job event that is triggered by a specific exit code or a range 

of exit codes, type the exit code(s) on this tab. You can create several actions using different job event triggers keyed to 
different exit code ranges to denote various job statuses. The exit code you use is determined by the script you are using. 
The exit code value can range from 0 to 30,000.

Use the operator field to select an operator for comparing the exit code(s) specified in the adjacent fields. 



 – The exit code must match the specified value or within the range of values. This operator enables both value 

fields and is the only operator that can specify a range of values.



 – The exit code must be anything but the specified value. Essentially greater than or less than the specified 

value.



– The exit code must be less than the specified value.



 – The exit code must be less than or equal to the specified value.



 – The exit code must be greater than the specified value.



 – The exit code must be greater than or equal to the specified value.

System events

About System Events

System events assign actions to events generated by the CWA master. For example, if the master is shutdown, you can 
notify users via email that jobs will not run until the master has started again. System events are useful for notifying 
interested users of conditions with system-wide effects. 

You create system events much like job events, except that they are not associated with particular jobs, since they are 
applicable to all jobs. Each includes a system event trigger, and one or more actions to take when the event occurs. The 
system event is created in the 

dialog by linking predefined actions to the system event triggers that CWA 

provides.

The CWA master is constantly monitoring for the conditions that trigger system events. The four categories of system 
event triggers monitored by CWA are:



 – Agent connection and job execution information



 – System and individual queue limit adjustments and job execution information



 – Compiling start and finish times and new production day information



 – Master start, stop, pause, resume and information