RS02987: IN ODM 8.8.0.1 WITH IF072, CUSTOM VALUE EDITOR IS NOT FIRING FOR EXISITNG VALUES IN A DECISION TABLE.

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 26
Operational Decision Manager V8.8.1.4 Fix Pack
Operational Decision Manager V8.9.1.0: Interim Fix 30
Operational Decision Manager V8.9.1.0: Interim Fix 31
Operational Decision Manager V8.8.0.1: Interim Fix 83
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

• In ODM 8.8.0.1 with IF072, custom value editor is not firing
  for exisitng values in a decision table. On the other hand,
  custom value editor is firing successfully for new values in a
  decision table. This problem started happening after upgrading
  ODM 8.8.0.0 environment to 8.8.0.1 with IF072. Hence this is
  possibly a regression.
  

Local fix

Problem summary

• In the Business console, when editing a cell that was
  previously set in a decision table with the custom value
  editor, it does not open. The following exception can be found
  in the logs:
  [1/10/18 17:45:38:024 EST] 000000a9 DtxEditorServ E
  Unexpected exception while processing command
  com.ibm.rules.bdsl.dtx.commands.GetValueEditorKey@6b6ca7bb
                                   java.io.IOException
      at
  ilog.rules.shared.json.IlrJsonScanner.scanString(IlrJsonScanner.
  java:184)
      at
  ilog.rules.shared.json.IlrJsonScanner.nextLexicalUnit(IlrJsonSca
  nner.java:111)
      at
  ilog.rules.shared.json.IlrJsonScanner.next(IlrJsonScanner.java:6
  6)
      at
  ilog.rules.shared.json.IlrJsonParser.nextLexicalUnit(IlrJsonPars
  er.java:149)
      at
  ilog.rules.shared.json.IlrJsonParser.parsePair(IlrJsonParser.jav
  a:181)
      at
  ilog.rules.shared.json.IlrJsonParser.parseObject(IlrJsonParser.j
  ava:157)
      at
  ilog.rules.shared.json.IlrJsonParser.parse(IlrJsonParser.java:14
  3)
      at
  ilog.rules.shared.json.IlrJsonSerializer.readObject(IlrJsonSeria
  lizer.java:90)
      at
  com.ibm.rules.bdsl.dtx.DtxEditorServlet.execCmd(DtxEditorServlet
  .java:200)
      at
  com.ibm.rules.bdsl.dtx.DtxEditorServlet.doPost(DtxEditorServlet.
  java:123)
      at
  com.ibm.rules.decisioncenter.web.core.servlets.DtxEditorServlet.
  doPost(DtxEditorServlet.java:411)
      at
  com.ibm.rules.bdsl.dtx.DtxEditorServlet.doGet(DtxEditorServlet.j
  ava:51)
  

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

• 999
  

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R880 PSY

     UP