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: | aSub, EFLG, and array length changes |
From: | Michael Davidsaver <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Tue, 02 Oct 2012 15:17:39 -0400 |
All,I've come across an unexpected behavior with monitors on the VAL* fields of the aSub record. It seems that the default is to post monitors only on change (EFLG="ON CHANGE").
Unfortunately, the calculation to determine if the value has changed doesn't work correctly in some cases. The issue is that while the previous values are saved, the length of the previous values are not. So the comparison test uses the same length (NEV*) for VAL* and OVL*. Thus, if the change is that the array gets smaller, but the remaining values are unchanged, then no monitor is posted.
The obvious solution is to add another set of fields to track the number of element in the old value. Does this seem reasonable? Also, how to express "the number of element in OVLA" in 4 characters or less?
Michael