Re: VxWorks global variable device support

[kerstien@odin.atdiv.lanl.gov (Deb Kerstiens)]

> 
>   > We might consider one additional subtlety
> 
> Just one?
> 
>   > for those of us who use STAT and/or
>   > SEVR, particularly to display value with a color rule that indicates these
>   > values.  If an output record had readback but was not processed, would it affect
>   > STAT and/or SEVR values.  Right now I think these are usually UDF and INVALID
>   > respectively until the record is processed. 
> 
> Good point. As the record is defined after reading back the value,
> UDF/INVALID is inappropriate. Would you think we need to have another
> status that announces that the value has been read back and is valid, but
> the record hasn't been processed yet? Or would that be too subtle a
> difference to be signalled?
> 
> Ralph
> 

>From my own perspective, the distinction would not generally be an important 
one.  It might be an important one, though, if you're accustomed to using the 
UDF and INVALID as indications that a record hasn't been processed when 
debugging applications at the IOC level as I often do.  You'd have to look at
the "read but don't process" choice if the record used DOL to understand why 
VAL was different from DOL and why nothing else in the chain had been processed.So it might be nice to have the distinction reflected in STAT and SEVR (if it's not too much trouble :-), but I can live without it if no one else cares.
 
deb