Handling epicsParseDouble Errors from SNMP PVs Returning Empty or Unexpected Values

[Varuna Crishan Meddage via Tech-talk <tech-talk at aps.anl.gov>]

I have the following EPICS record defined

==================================================================

record(ai, "$(acc):$(sys)_$(group):nsRbDiscStatus")

{

  field(SCAN, "10 second")

  field(DTYP, "Snmp")

  field(INP, "@$(HOST) $(COMMUNITY) $(W)::nsRbDiscStatus.$(id)  ( 100 i")

  field(DESC, "Rb Discipline Status")

  #field(HIGH,"2")

  #field(HIHI,"3")

  #field(LOW,"0")

  #field(LOLO,"-1")

  #field(LLSV, MAJOR)

  #field(LSV, MINOR)

  #field(HSV, MINOR)

  #field(HHSV, MAJOR)

}

===================================================================

For this EPICs record I get the following error during runtime.

devSnmp AI read error 'PIP2:TIME_CTRL_GPS:nsRbDiscStatus' : epicsParseDouble failed on 'should be INTEGER): ""'

In the MIB file this variable is defined as follows

======================================================================

nsRbDiscStatus OBJECT-TYPE

    SYNTAX      INTEGER { disciplinewait(0),disciplinegood(1),holdover(2) }

    MAX-ACCESS  read-only

    STATUS      current

    DESCRIPTION 

        "Rb Discipline Status: 0=Disc Wait, 1=Disc Good, 2=Holdover"

    ::= { nsRubidiumObjs 4 }

========================================================================

When I ran the snmpwalk command, the output for this variable is

NOVUS-SECURE-MIB::nsRbDiscStatus.0 = Wrong Type (should be INTEGER): ""

Any suggestions to solve this issue ?

Thanks

Varuna Meddage