lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 67eb163 3/5: Add an assertion, exposing a def


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 67eb163 3/5: Add an assertion, exposing a defect
Date: Fri, 15 Sep 2017 07:51:30 -0400 (EDT)

branch: master
commit 67eb1639e501abf62b76f52e05dcb8c6eb95d546
Author: Gregory W. Chicares <address@hidden>
Commit: Gregory W. Chicares <address@hidden>

    Add an assertion, exposing a defect
    
    This assertion fired for an inforce test case with
      <cell version="6">
    and a specified amount higher than the specified-amount-load basis.
    The defect exposed is in the backward-compatibility code, which uses
    the former as a proxy for the latter. This shouldn't matter now in
    production if vendor extracts are current and correct, which isn't
    necessarily the case. At any rate, the assertion is valuable because
    it can detect an implausible value in a current extract.
---
 ihs_avmly.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ihs_avmly.cpp b/ihs_avmly.cpp
index fe08de2..7b9dc5d 100644
--- a/ihs_avmly.cpp
+++ b/ihs_avmly.cpp
@@ -1599,6 +1599,7 @@ void AccountValue::TxSetBOMAV()
             {
             LMI_ASSERT(0.0 == InvariantValues().TermSpecAmt[0]);
             }
+        LMI_ASSERT(yare_input_.InforceSpecAmtLoadBase <= SpecAmtLoadLimit);
         SpecAmtLoadBase =
             (0 == Year && 0 == Month)
             ? InvariantValues().TermSpecAmt[0] + InvariantValues().SpecAmt[0]



reply via email to

[Prev in Thread] Current Thread [Next in Thread]