mbboDirectRecord

[Benjamin Franksen <franksen@mail.bessy.de>]

Hello,

I observed a strange behavior of the mbboDirectRecord: the record
remains undefined (UDF==1), even though a correct value was put into VAL
(the hardware was written correctly either). Nevertheless, the STAT and
SEVR are both ok.

I compared the code to that of the mbboRecord. It is obvious that UDF is
not handled properly in the mbboDirect.

First, inside init_record, UDF is not set to 0 after
pdset->init_record() returns ok. BTW, init_record checks if the return
value is 2, which doesn't make sense in a record that has no conversion.

Second, inside process(), UDF is not checked and there is no call to
recGblSetSevr that sets STAT = UDF_ALARM.

I propose to correct these things for R3.13.2.

Ben