Previously, the only indication that no terminal was configured for
command alarms was a misleading error message "Failure to execute
command" when the alarm triggered. Now a warning is given when the
alarm is created, and the error message is improved at trigger time.