Re: timestamp issue

2005-11-30 Thread David T. Perkins
Time in > mib2c code, Since you are telling for dateAndTime, i have to give hexa format > string for > dateAndTime type scalars. > > > Regards > Kanda, > > -Original Message- > From: David T. Perkins [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 27, 2005 4:01 AM >

Re: timestamp issue

2005-11-30 Thread Dave Shield
On Wed, 2005-11-30 at 21:06 +0530, [EMAIL PROTECTED] wrote: > I had tried the value, what you had send, > still i am getting some big number. > I had filled the snmp_set_var_typed_value as >snmp_set_var_typed_value (requests, ASN_OCTET_STR, > "0x07C8051a0d1e0e002d0

Re: timestamp issue

2005-11-30 Thread kanda.samy
Title: Re: timestamp issue Hi David,     Thank you for quick the response     I had tried the value, what you had send, still i am getting some big number. I had filled the snmp_set_var_typed_value as snmp_set_var_typed_value (requests,ASN_OCTET_STR,"0x07C8051a0d1e0e002

Re: timestamp issue

2005-11-26 Thread David T. Perkins
HI, It appears that you have misunderstood the definition of the DataAndTime textual convention. Here is the definition from RFC 2579: DateAndTime ::= TEXTUAL-CONVENTION DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d" STATUS current DESCRIPTION "A date-time specificatio

timestamp issue

2005-11-26 Thread siddesh.rajappa
Hi One of our Property MIB is defined as "SYNTAX DateAndTime MAX-ACCESS read-only". For this mib i had generated c code , using mib2c script ( mib2c.scalar.conf). In the code, for that particular scalar i am sending string "1992-5-26,13:30:15.0,-4:0" by filling set_var