Hi Pete,
I think you are right - the put callback may complete before the record is processed the 2nd time due to the severity change. And vice-versa - once the communication is good again, you will have a bad severity on that mbbo until it is processed the 2nd time when the downstream record goes good again.
Stephanie
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Leicester, PJ (Pete)
> Sent: Wednesday, April 22, 2009 10:15 AM
> To: Andrew Johnson; [email protected]
> Subject: RE: back propagating error states
>
> Thanks Andrew and Stephanie. The addition of the CP flag does work as
> far as I can see. It certainly seems ok from edm.
>
> My one concern now is if I have a client using put callback to change
> the mbbo record will it see the error state in the mbbo record or is the
> callback complete before the SDIS MS CP updates the mbbi's error status.
> Perhaps there is a race condition here?
>
> Pete
>
> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: 22 April 2009 16:29
> To: [email protected]
> Cc: Leicester, PJ (Pete)
> Subject: Re: back propagating error states
>
>
> Hi Pete,
>
> On Wednesday 22 April 2009 09:27:57 Leicester, PJ (Pete) wrote:
> >
> > I tried linking the SDIS from the mbbo to the longout record with
> > maximise severity set. This did make the mbbo reflect the longout's
> > error state but only after being processed a second time so is far
> > from ideal.
>
> If you were to add a CP flag to that SDIS link it would cause the mbbo
> record
> to get processed whenever the field it was pointing to changed. I would
>
> suggest pointing it to the SEVR field of the longout record, but make
> sure
> that you also set the mbbo.DISV field to something outside the range
> 0..3.
>
> I'm not 100% sure this will work, but I think it should.
>
> - Andrew
> --
> The best FOSS code is written to be read by other humans -- Harold Welte
> This e-mail and any attachments may contain confidential, copyright and or privileged
> material, and are for the use of the intended addressee only. If you are not the intended
> addressee or an authorised recipient of the addressee please notify us of receipt by returning
> the e-mail and do not use, copy, retain, distribute or disclose the information in or attached
> to the e-mail.
> Any opinions expressed within this e-mail are those of the individual and not necessarily of
> Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free
> from viruses and we cannot accept liability for any damage which you may sustain as a
> result of software viruses which may be transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and Wales
> with its registered office at Diamond House, Harwell Science and Innovation Campus,
> Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
- References:
- Re: back propagating error states Andrew Johnson
- RE: back propagating error states Leicester, PJ (Pete)
- Navigate by Date:
- Prev:
RE: back propagating error states Leicester, PJ (Pete)
- Next:
Re: back propagating error states Andrew Johnson
- 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:
RE: back propagating error states Leicester, PJ (Pete)
- Next:
Re: back propagating error states Andrew Johnson
- 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
|