caput tool won't write to mbbo w/o state strings
Observed by Heinz Junkes <junkes_
If a mbbo record only defines the state values, but no state strings, the caput command line utility is not able to write to the record's value.
While this configuration is certainly unusual, it is legal, and caput should be able to write to such records.
Background: caput first reads the ENUM choice set from the record. It exits with an error message if the string set point is not found in the choice set, or if the numerical index set point is larger than the number of choices. While the string behaviour seems reasonable, the numerical put should just print a warning and still write the value to allow writing to such records.