Hi,
I'm trying to understand the internals of alarm acknowledgement. Here's
my interpretation of putAcks().
static long putAcks(paddr,pbuffer,nRequest,no_elements,offset)
DBADDR *paddr;
unsigned short *pbuffer;
long nRequest;
long no_elements;
long offset;
{
dbCommon *precord=(dbCommon *)(paddr->precord);
if(*pbuffer >= precord->acks) {
precord->acks = 0;
db_post_events(precord,NULL,DBE_ALARM);
db_post_events(precord,&precord->acks,DBE_VALUE|DBE_ALARM);
}
return(0);
}
1. Only do anything when the acknowledge severity is higher than or
equal to the currently unacknowledged severity.
Assuming this condition is met then
2. Reset the unacknowledge severity.
3. ???Send an alarm monitor to all clients monitoring at least one field
in this record.???
4. Send a monitor to all clients monitoring the ACKS field value or
alarm in this record.
I'm uncertain as to the purpose of step 3. Would someone please
explain.
Thanks
Geoff
- Replies:
- Re: putAcks Marty Kraimer
- Navigate by Date:
- Prev:
Re: Build static libraries on WinNT Vladimir Sirotenko
- Next:
Re: putAcks Marty Kraimer
- Index:
1994
1995
1996
1997
1998
1999
<2000>
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Capfast for Linux? William Lupton
- Next:
Re: putAcks Marty Kraimer
- Index:
1994
1995
1996
1997
1998
1999
<2000>
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|