Input records that do not have the 'VAL' field set always have UDF alarm status.

[pheest]

This is the case whether or not PINI is set to "YES".
It does not apply to output records.

Tests show that reversing 'self.raw' in ptable.py addresses the issue for simple record types.
However for more complex types using either self.raw = False or using the RVAL field causes IOC applications to fail.
Self.raw does not appear to be referenced anywhere so this is difficult to understand.

[pheest]

Some helpful information in interfaces.rst:

" .. attribute:: raw

A boolean value indicating whether this device support
uses "raw" access.  A Raw support module will update
the VAL field even if the recordtype has an RVAL field
(eg. ai/ao, mbbi/mbbo).

Omitting this attribute is the same as False."

[pheest]

The "raw" attribute is passed to dbdset.c with:
ret = PyObject_GetAttrString(priv->support, "raw");
and stored with:
priv->rawsupport = 1;

This alters the behaviour of:
init_record2 and process_record2 to return 2, not 0.
This is taken to mean "Success, but don’t modify VAL" for record types that are using RVAL.