Event Listen Properties Tab

You can use the Event Listen properties tab to specify nodes and events to be monitored in a process job. If a specified event is found, then the Event Listen node executes any downstream node to which it is connected.

The tab includes the following elements:

• Nodes - Specifies the nodes to be monitored, as follows: 
  
  All -All nodes in the process job will be monitored.
  
  Node Type - All nodes of the specified type in the process job will be monitored.
  
  Node - One selected node in the process job will be monitored.
  
  
• Event type - Specifies the type of event that the Event Listen node will monitor. Available types are All, Error, and a set of SAS events that can be used to monitor SAS Code nodes and SAS Code (reference) nodes. The events are as follows: 
  
  All - All events from the specified nodes will be monitored.
  
  Error -Only error events from the specified nodes will be monitored.
  
  SAS_EVENT_PROCSTART- Indicates that a SAS procedure started in a monitored node.
  
  SAS_EVENT_SUBMITCOMPLETE - Indicates that the SAS Workspace Server finished running the submitted job for a monitored node.
  
  SAS_EVENT_PROCCOMPLETE - Indicates that a SAS procedure completed successfully for a monitored node.
  
  SAS_EVENT_DATASTEPSTART - Indicates that a SAS DATA step started for a monitored node.
  
  SAS_EVENT_DATASTEPCOMPLETE - Indicates that a SAS DATA step completed successfully for a monitored node.
  
  SAS_EVENT_STEPERROR - Indicates that a SAS ERROR occurred in a monitored node.
  
  SAS_EVENT_GLOBALSTMTCOMPLETE - Indicates that a SAS global statement in a monitored node completed successfully.
  
  SAS_EVENT_GLOBALSTMTERROR - Indicates that an error occurred in a SAS global statement for a monitored node.
  
  SAS_EVENT_CANCEL - Indicates that a SAS job was canceled for a monitored node.

Note that you can use //!event notation when you create a user-defined event in the Expression node. (This notation takes the following format: //!event <name of event>.) Then the event will be displayed in the selection list of the Event Listener node. The following example illustrates this code format:

//!event INFO_MISSING

raiseevent("INFO_MISSING", "FILE", "OK", "FIELDS", "NO DATE")