Open bfrk opened 4 years ago
A short comment: this will be a problem on disconnects, which can easily be simulated by setting of autoconnect and disconnect through CNCT field of the asyn record.
You are right, NO_ALARM/INVALID is a confusing combination and was not intended. But I need to check your fix with "I/O Intr" records first.
bool Stream::process()
initializes the status toNO_ALARM
, then callsstartProtocol
, and if that fails setsrecGblSetSevr(record, status, INVALID_ALARM)
. This means the record will haveSTAT=NO_ALARM
andSEVR=INVALID
which is a bit confusing.Here is a fix, using the
COMM_ALARM
status instead.