A System Command Action enables ClearSCADA to automatically trigger an operating system command in response to a particular alarm situation. This can be used, for instance, to trigger an external application to record the alarms on your system. The application that the command runs needs to be fully automated, so that it runs up, performs its required activity, and then automatically closes again in the briefest period of time (certainly well under a second). While such a system command-triggered application is running, any other system commands are placed on hold.
You need to configure a separate System Command Action for each different executable that ClearSCADA is to run in response to an alarm situation (or, if appropriate, use a batch file to trigger multiple executes from a single System Command Action).
For further information, see Configure a Redirection Action, and see Define the System Command Action Details.
ClearSCADA can also execute system commands from Logic programs, and from pick action menus on Mimics. For information, see the ClearSCADA Guide to Logic, and the ClearSCADA Guide to Mimics, respectively.
If system calls are disabled, the credentials are invalid or user impersonation has failed, the alarm redirection action will fail. For more information, see System Calls Settings in the ClearSCADA Guide to Server Administration.