RS03662: INCORRECT ARL FILE GENERATED IN THE DEBUG MODE FOR A RULEFLOW WHEN THERE ARE AT LEAST 2 TASKS AFTER CONVERGING BRANCHES

IBM Operational Decision Manager V8.10.5 Download Document
IBM Operational Decision Manager V8.10.5 Refresh Pack

APAR status

• Closed as program error.

Error description

• If a ruleflow contains a decision node and the two branches are
  converging to 2 tasks or more then the ARL file generated for
  the ruleflow when exporting the ruleset with the option "Include
  debugging information for IBM customer support" enabled is
  incorrect: the calls to those 2 tasks are concatenated without
  any separator in-between (see Logging and Logging2 in the
  example below).
  However the ruleset executes normally.
  
  
  flowtask rf1($EngineData){
   initial {
  
  $EngineData.this.report = new test.Report("default message");
  
  }
   {
   call task : rf1>Common;
   if (true) {
   call task :
  rf1>BusinessAccountPolicyFlow;
   label_0 call task :
  rf1>Loggingcall task : rf1>Logging2;
   }
   else {
   call task :
  rf1>Risk;
   call task : rf1>Overriding;
   goto : label_0;
   }
  
  
  }
  }
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users generating rulesets with Decision Engine in debug      *
  * mode.                                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If a ruleflow contains a decision node and the two branches  *
  * are converging to 2 tasks or more, then the ARL file         *
  * generated for the ruleflow when exporting the ruleset with   *
  * the option "Include debugging information for IBM customer   *
  * support" enabled is incorrect: the calls to those 2 tasks    *
  * are concatenated without any separator in-between (see       *
  * Logging and Logging2 in the example below).                  *
  * However the ruleset executes normally.                       *
  *                                                              *
  * flowtask rf1($EngineData){                                   *
  *   initial {                                                  *
  *     $EngineData.this.report = new test.Report("default       *
  * message");                                                   *
  *   }                                                          *
  *   {                                                          *
  *     call task : rf1>Common;                                  *
  *     if (true) {                                              *
  *       call task : rf1>BusinessAccountPolicyFlow;             *
  *       label_0 call task : rf1>Loggingcall task :             *
  * rf1>Logging2;                                                *
  *     }                                                        *
  *      else {                                                  *
  *       call task : rf1>Risk;                                  *
  *       call task : rf1>Overriding;                            *
  *       goto : label_0;                                        *
  *     }                                                        *
  *                                                              *
  *   }                                                          *
  * }                                                            *
  ****************************************************************
  * 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

• R8A0 PSY

     UP