On 12/2/20 11:42 AM, Daykin, Evan via Tech-talk wrote:
> Hi again and thank you all for your suggestions.
>
>
>
> I spent some time creating a minimal example, and it behaves, of course, as you all said it does – a simple printf works. The problem is that one of my input links was not resolved, so it did not call the subroutine. I didn’t think of this possibility since TPRO showed the record processing, but Martin pointed me to the documentation where it says:
>
> · If all input-link fetches succeeded, call the routine specified by SNAM.
>
> Now my question becomes: is there a field that can be set such that this failure is not silent, e.g. raise LINK alarm or output some error message indicating which fetch failed?
Not a field, but you can (and imo. should) add the "MSI" modifier to all of your links.
- Replies:
- Re: aSub debug output Johnson, Andrew N. via Tech-talk
- References:
- aSub debug output Daykin, Evan via Tech-talk
- Re: aSub debug output Johnson, Andrew N. via Tech-talk
- RE: aSub debug output Daykin, Evan via Tech-talk
- Navigate by Date:
- Prev:
RE: aSub debug output Daykin, Evan via Tech-talk
- Next:
RE: Epics Archiver not pushing to STS? Manoussakis, Adamandios via Tech-talk
- 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: aSub debug output Daykin, Evan via Tech-talk
- Next:
Re: aSub debug output Johnson, Andrew N. via Tech-talk
- 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
|