John Said:
>Look, what we NEED is a real error messaging system that allows code to
>log meaningful, arbitrairly complex, appropriate messages.
>
>I object to the idea of basing the error message and logging scheme on
>a return code to message mapping system. And that goes for anywhere,
>including on the IOCs themselves.
Wholeheartedly agree! Both EZCA and CDEV are attempting to move away from
this, but much work remains.
John also proposed a basic error logging system, and I would suggest that
log messages consist of the following "atoms":
severity
status code (a ---small--- set)
originating node
originating application/sub-system/whatever
time stamp
arbitrarily long text
SLAC's error code system is like this, but heavily VMS. A browser tool could
filter based on any of the atoms. The status code could be useful to tell
the browser to NOT display any more of that particular flavor of message.
Something at the level of the EZCA or CDEV enumerated error codes.
Chip
- References:
- Re: EPICS status codes proposal winans
- Navigate by Date:
- Prev:
Re: EPICS status codes proposal William Lupton
- Next:
Re: EPICS status codes proposal Jim B. Kowalkowski
- 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: EPICS status codes proposal winans
- Next:
Re: EPICS status codes proposal William Lupton
- 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
|