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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | getting streamDevice exception handler replyTimeout to write to a record [SEC=UNCLASSIFIED] |
From: | "CORNALL, Terry via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 1 Apr 2020 00:58:53 +0000 |
Hi All. In streamDevice protocol, how can I send something to a record when @replyTimeout gets triggered, in order to detect complete comms failure? I've used exec and dbpf successfully e.g. something like @replyTimeout {exec 'dbpf \$5 1'} and that works, but I really don't like it that dbpf causes the IOCsh output to be cluttered up.
Or is a different approach needed? Say something in the database that if a successful 'in' hasn't happened recently causes a 'comms error' to be set, rather than using streamDevice replyTimeout. Thanks for your thoughts, Terry |