Add warn message for invalid field content on CommandExchangeBuffer
As Patrick Dessalle from users-list stated:
[...] the code is not enforcing the field formats specification. For instance, I can set the dataset name of a Virtual file with lower case characters and a length longer than 26. [...]
And as I reported to him:
[...] Fields contents are partially checked by the library. Their format is not enforced but the data is stripped and filled with missing characters (it pads with space character or zeros depending on NUMERIC or ALPHA format) Personally I think this is the best approach. Maybe we can add a log to WARN user of invalid data arriving at the library level. The class I think we could add that warning is CommandExchangeBuffer, which would automatically proceed to all and every OFTP commands and fields. [...]
This is not considered as a bug, but may require an improvement.
So that's why we are adding a warn message for inconsistent field values.