Errors returned for a set on non-existent scalars and non-existent column of a table

Hi All,
 
We are using Net-snmp-5.2.2 as Master agent and subagent.  We are using
helper functions defined in scalar.c and table.c for scalars and tables
respectively.
When a set request is given on a non-existing column of a table, request
reaches the subagent and and error "notWritable" is returned from
table.c helper function, which seems to be fine as per the description
given in set request processing in RFC 1905. 
But for a set request on a non-existing scalar, error "noCreation" is
returned from the scalar.c helper function. 
Please let me know why the error code returned for a set on non-existing
scalar is not same as set on a non-existing column of a table. ?
 
RFC 1905 says,
 
"if there are no variables which share the same OBJECT IDENTIFIER prefix
as the variable binding's name, and which are able to be created or
modified no matter what new value is specified, then the value of the
Response-PDU's error-status field is set to `notWritable', and the value
of its error-index field is set to the index of the failed variable
binding."

So, according to the above description, as there will be no variable
which has OID prefix as the non-existent scalar given in
variable-binding, notWritable shall be returned in the response.
 
Please clarify if this is a bug in scalar.c helper function or it is
correct.
 
 
Regards,
Suresh.

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users