RS02954: PARSING AND EXECUTING A CRE RULESET WITH NUMEROUS PACKAGES IS TOO SLOW

Operational Decision Manager V8.7.1.2: Interim Fix 74
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.8.1.4 Fix Pack
Operational Decision Manager V8.10.2.0: Interim Fix 12 for Engine
Operational Decision Manager for z/OS 8.10.2.2 Fix Pack
IBM Operational Decision Manager V8.10.2.2 Fix Pack
Operational Decision Manager V8.10.2.2: Interim Fix 2
Operational Decision Manager V8.10.2.2: Interim Fix 5 for Engine

APAR status

• Closed as program error.

Error description

• With a large ruleset
  11298  packages
  2 ruleflows
  79882  action rules
  197 decisions tables
  10/6/17 4:55:50 PM [INFO]      GBRXU5073I - -.- - Parsing
  ruleset /xxxxxxx/1.0/xxxxxxx/7.0 with the following properties:
  {ruleset.debug.enabled=false, .......}
  10/6/17 5:33:45 PM [INFO]      GBRXU5074I - -.- - Ruleset
  /xxxxxxxx/1.0/xxxxxxxxx/7.0 was parsed successfully.
  Parsing around 38 minutes is what we have measured in  various
  testing.
  But then the execution is quite different there. It  takes 2
  hours 30 minutes to execute 2 rules
  10/6/17 5:33:45 PM [FINE]      GBRXU5054I /xxxxxxxx/1.
  0/xxxxxxxxx/7.0 1.1 - Rule engine, sets parameters (
  /xxxxxxxxx/1.0/xxxxxxxx/7.0). Measures: {Duration(ms)=3,
  TimeStamp(ms)=1507336425678}.
  10/6/17 8:13:31 PM [FINE]      GBRXU5050I /xxxxxxxx/1.
  0/xxxxxx/7.0 1.1 - Rule engine, executes task (/xxxxxxxx/1.
  0/xxxxxx/7.0). Measures: {Duration(ms)=9585360, Number of rules
  that were executed before this execution(quantity)=0, Number of
  rules that were executed per millisecond(quantity/ms)=2.
  0865152691187394E-7, Number of executed rules (quantity)=2,
  TimeStamp(ms)=1507336425682}.
  

Local fix

Problem summary

• We need to speed up ruleset parsing and rules compile in CRE to
  improve the performance.
  

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

  WDS FOR RULES

• Fixed component ID

  5725B6903

Applicable component levels

• R891 PSY

     UP