RS01962: BOTH THEN AND ELSE PART OF FASTPATH RULE MAY FIRE

Operational Decision Manager V8.6.0.2: Interim Fix 18
Operational Decision Manager V8.7.1.1 Fix Pack
Operational Decision Manager V8.0.1.2: Interim Fix 52
Operational Decision Manager V8.6.0.3 Fix Pack
Operational Decision Manager V8.5.1.3 Fix Pack
Operational Decision Manager V8.5.1.2: Interim Fix 56
Operational Decison Manager z/OS 8.6.0.3 Fix Pack
Operational Decision Manager V8.5.1.2: Interim Fix 48
Operational Decision Manager V8.7.1.1 Fix Pack

APAR status

• Closed as program error.

Error description

• A rule may have both its Then and Else action parts executed
  when using the Fastpath algorithm and the Classic Rule Engine.
  This happens with the following type of combination of rules,
  where someRule is fired for both Then and Else parts:
  ruleset fastpathElse
  {
  };
  flowtask mainflow {
  property mainflowtask = true;
  body {
  mainflow#myFastpathRules;
  }
  };
  ruletask mainflow#myFastpathRules {
  algorithm = sequential;
  property ilog.rules.engine.sequential.fastpath = true;
  ordering = sorted;
  body {
  someRule,
  someRule2
  }
  };
  rule someRule {
  when {
      IlrContext() from ?context;
      evaluate (variable1 : ("AAA"));
      evaluate ((variable1.equals("AAA")));
   } then {
      System.out.println(instance.ruleName+" THEN");
   } else {
      System.out.println(instance.ruleName+" ELSE");
   }
  
  };
  rule someRule2 {
  when {
      IlrContext() from ?context;
      evaluate (variable1 : ("AAA"));
      evaluate ((variable1.equals("BBB")));
   } then {
      System.out.println(instance.ruleName+" THEN");
   } else {
      System.out.println(instance.ruleName+" ELSE");
   }
  };
  

Local fix

• -use Sequential or RetePlus algorithm instead of Fastpath with
  Classic Rule Engine
  -or use Decision Engine instead of Classic Rule Engine
  

Problem summary

• error in condition sharing with static values leads to
  incorrect test during execution
  

Problem conclusion

• The code is fixed
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• None
  999
  

Fix information

• Fixed component name

  WS DECISION SVR

• Fixed component ID

  5725B6901

Applicable component levels

• R860 PSY

     UP