Unexpected behavior for I&M0, I&M5 and I&M Filter data when handled by application

When stack is configured to pass I&M to application, it still internally rejects wiriting I&M0 and I&M5 with access denied. It is expected that in such a case, the information is forwared to the application in order to retrieve the correct error code "Access Denied" or "Invalid Index". This is necessary as if an submodule has its own I&M record, the write must be denied, while when it has no own I&M record it must be rejected with invalid index.

Also Writing I&M Filter data record is rejected with invalid error code "Invalid Index". Should be "Access Denied"