#11 pvput does not display error/warning messages for illegal values

[Sinisa Veseli]

Tag: 3.0-pre1
OS: linux, 64-bit

pvput does not display error/warning messages for illegal values.

Steps to reproduce:

1) run test IOC using st.cmd from pvaSrv/testApp/iocBoot/testDbPv

2) invoke pvput commands as in the examples below:

bash-4.1$ pvget enum01
enum01
uri:ev4:nt/2012/pwd:NTEnum
enum_t value
int index 1
string[] choices [zero,one,two,three]

bash-4.1$ pvput -r "field(value.index)" enum01 4
Old :
uri:ev4:nt/2012/pwd:NTScalar
int value 1

New :
uri:ev4:nt/2012/pwd:NTScalar
int value 4

bash-4.1$ pvput -r "field(value.index)" enum01 111111111
Old :
uri:ev4:nt/2012/pwd:NTScalar
int value 4

New :
uri:ev4:nt/2012/pwd:NTScalar
int value 27591

[Matej Sekoranja]

pvaSrv should reject invalid enum values, not pvput (eput could in practice since it knows NTEnum).
However, it is still up to the pvaSrv do reject such values.

Note that EPICS softIOC (V3) behaves the same way, so it might be
wrong to reject such puts.

[Ralph Lange]

Moved to GitHub (pvaSrv Issue #7).