RS03349: "THE END NODE IS DUPLICATED" ERROR WITH MULTIPLE END NODES IN BC RULEFLOW EDITOR

IBM Operational Decision Manager V8.10.2 Mod Pack
IBM Operational Decision Manager V8.10.2 Download Document
Operational Decision Manager V8.9.1.0: Interim Fix 35
Operational Decision Manager V8.9.2.2 Fix Pack
Operational Decision Manager for z/OS 8.9.2.2 Fix Pack
Operational Decision Manager V8.9.1.0: Interim Fix 40
Operational Decision Manager V8.9.1.0: Interim Fix 41
Operational Decision Manager V8.9.1.0: Interim Fix 42

APAR status

• Closed as program error.

Error description

• It is legal to have multiple end nodes, or rather multiple
  graphical reference to an end node.
  Unfortunately, the ruleflow editor in BC does define only one
  end node (which is correct) but repeats the definition of that
  end node for each reference in the ruleflow view.
  This creates duplicated definition and when you try to export
  the ruleapp, the compiler is complaining about those duplicates.
  

Local fix

• If you need to have multiple End Nodes (which is valid) you
  should use the Ruleflow Editor of the  Rule Designer, and
  synchronize with DC.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * users generating ruleset archive or running test suite       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * It is legal to have multiple end nodes, or rather multiple   *
  * graphical reference to an end node.                          *
  * If you create multiple end node in Rule Designer there will  *
  * be only one internal reference to that node created. Note    *
  * that all graphical end node are referencing the same end     *
  * node definition.                                             *
  *                                                              *
  * Unfortunately, the ruleflow editor in BC does the same so    *
  * there is only one end node defined (which is correct) but    *
  * repeats the definition of that end node for each reference   *
  * in the ruleflow view.                                        *
  * This creates duplicated definition and when you try to       *
  * export the ruleapp, the compiler is complaining about those  *
  * duplicates.                                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

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:

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R890 PSY

     UP