RS02988: EXCEPTION WHEN OPENING A DECISION TABLE IN BUSINESS CONSOLE

Operational Decision Manager V8.9.2 Download Document
Operational Decision Manager V8.9.2 Mod Pack
Operational Decision Manager for z/OS 8.9.2 Mod Pack
Operational Decision Manager V8.9.1.0: Interim Fix 31
Operational Decision Manager V8.9.1.0: Interim Fix 33
Operational Decision Manager V8.9.1.0: Interim Fix 34
Operational Decision Manager V8.9.1.0: Interim Fix 35
Operational Decision Manager V8.9.1.0: Interim Fix 36
Operational Decision Manager V8.5.1.3: Interim Fix 79
Operational Decision Manager V8.9.1.0: Interim Fix 38
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

• A single project Decision service that contains DTs and rules,
  is visualized perfectly on  Rule Designer or Enterprise Console
  but leads to an error on Business Console :
  The log is explicit :
  Dec 29, 2017 5:57:50 PM com.ibm.rules.decisioncenter.web.core.
  servlets.DtxEditorServlet loadEnvironment
  WARNING: Failed to get DT editor environment for element 'brm.
  DecisionTable:11': java.lang.Exception: Error encountered when
  loading table
  Dec 29, 2017 6:04:07 PM com.ibm.rules.decisioncenter.web.core.
  DtxEditorHelper loadDt
  WARNING: Error encountered when loading table brm.DecisionTable:
  11:11: java.lang.ArrayIndexOutOfBoundsException
  Dec 29, 2017 6:04:07 PM com.ibm.rules.decisioncenter.web.core.
  servlets.DtxEditorServlet loadEnvironment
  WARNING: Failed to get DT editor environment for element 'brm.
  DecisionTable:11': java.lang.Exception: Error encountered when
  loading table
  

Local fix

• open it in Enterprise Console
  

Problem summary

• The DTX editor has its own "DT model" (aka tabular) and XML
  loader. We do not use IlrDTModel in the DTX editor. The DTX XML
  loader doesn't allow for corrupted models, like the one in this
  defect. It reports an error. The "old" IlrDTModel / XML loader
  will load this .dta, even if it is corrupted, making it
  possible to see the DT in RD/EC, whereas you should not. In
  RD/EC, you can corrupt the DT even more, to the point that the
  editor gets in an invalid state (with higher partitions from
  left to right etc).
  When the DTX loader fails to parse the corrupted model, we now
  try to load it using the old APIs. If it loads, we check the
  IlrDTModel's integrity, and try to detect corruptions like the
  one in this bug.
  The check also determines if the table is "fixable", ie if we
  can fix the corrupted model and make it valid again.
  If the model if fixable, we fix it when converting to the DTX
  model (corrupted IlrDTModel -> valid tabular model).
  The DTX editor then loads the tabular model as usual.
  

Problem conclusion

• The code was fixed.
  

Temporary fix

• Open it with the Enterprise Console
  

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

• 999
  

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R890 PSY

     UP