Thank you very much. now ok for me.
Vishnu
From: Mark Rivers <
[email protected]>
Sent: Mon, 18 Mar 2013 21:56:34
To: Vishnu Patel <
[email protected]>, "Andrew Johnson " <
[email protected]>
Cc: "
[email protected]" <
[email protected]>
Subject: Re: mbboDirect record questions
No, I don't think that's true. Your .db file only sets the initial value of SEVR, if it changes later it will still be reported.
Mark
________________________________
From:
[email protected] [
[email protected]] on behalf of Vishnu Patel [
[email protected]]
Sent: Monday, March 18, 2013 11:13 AM
To: Andrew Johnson
Cc:
[email protected]
Subject: Re: mbboDirect record questions
Hello Andrew,
If i write SEVR in .db file, it will become constant and so during normal operation if some thing makes it INVALID_ALARM, it will not be reported.
In this case i will bypass SEVR and make it constant.
Thanks
--Vishnu
From: Andrew Johnson <
[email protected]>
Sent: Mon, 18 Mar 2013 20:14:01
To: "Vishnu Patel" <
[email protected]>, "
[email protected]" <
[email protected]>
Subject: Re: mbboDirect record questions
Hi Vishnu,
On 2013-03-16 Vishnu Patel wrote:
> So it think some thing make prec->sevr = INVALID_ALARM
> which lead first time caput sets Bn to the value.
> I don't know how prec->sevr sets INVALID_ALARM, and it is expected or not.
The default value for the SEVR field is INVALID_ALARM (in dbCommon.dbd), but
you can override that value in your .db file for each individual record.
- Andrew
--
There is no such thing as a free lunch. When invited for lunch,
it is best to check if you are there to eat, or to be eaten.
-- Clive Robinson
[
http://sigads.rediff.com/RealMedia/ads/adstream_nx.ads/www.rediffmail.com/signatureline.htm@Middle]<http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline.htm@Middle?>
Get your own FREE website and domain with business email solutions, click here<
http://track.rediff.com/click?url="">