Experimental Physics and
Industrial Control System

Stephanie Allison 926-4534 <[email protected]> (415) · Thu, 19 Oct 1995 18:02:33 -0700 (PDT)

>EPICS status code proposals
>
>William Lupton, 10/19/95
>[email protected]

Hello William,

Thanks for the opportunity to comment on your EPICS status code proposals.
We are like Keck in that we have a mix of EPICS and non-EPICS systems,
both of which log error messages.  We want to get the messages from both
systems to the same error logging service.  (Let me know if anybody
answers your question about a documented way of using a different
errPrintf without changing EPICS base code).

You mentioned that you need the ability to make a message log-only and
not visible to the operator.  We have the same requirement.  We also have
the requirement that some fatal messages generate a particular noise
in the control room (like a bomb drop - I kid you not!).  We will probably
end up doing the same thing as you - encoding this kind of information by
convention.

On our non-EPICS (VMS) system, we use a different kind of severity
(success, informational, warning, error, fatal).  I suppose we can
do some sort of translation from the SEVR values if necessary.  The 
non-EPICS system also uses "facility" which is like your group/subsys.

Just to make sure I'm not missing something but with the existing system
or even with your proposed changes, if I make a typo in my error text or 
if I pick text that is user-unfriendly (which is common thing for some
programmers), in order to change the text, I have to recompile and 
reboot the IOC?

Thank you,

++ Stephanie Allison ([email protected]) 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System