RS02668: EMPTY RULES CONTENT AFTER MERGE

Operational Decision Manager V8.8.0.1: Interim Fix 49
Operational Decision Manager V8.8.0.1: Interim Fix 51
Operational Decison Manager z/OS 8.8.1.2 Fix Pack
Operational Decision Manager V8.8.1.2 Fix Pack
Operational Decision Manager V8.7.1.2: Interim Fix 67
Operational Decision Manager V8.9.0.1 Fix Pack
Operational Decision Manager z/OS 8.9.0.1 Fix Pack
Operational Decision Manager V8.7.1.2: Interim Fix 69
Operational Decision Manager V8.8.0.1: Interim Fix 62
Operational Decision Manager V8.8.0.1: Interim Fix 65
Operational Decision Manager V8.8.0.1: Interim Fix 72
Operational Decision Manager V8.9.1 Download Document
Operational Decision Manager V8.9.1 Mod Pack
Operational Decision Manager V8.7.1.2: Interim Fix 73
Operational Decision Manager V8.8.0.1: Interim Fix 79
Operational Decision Manager V8.7.1.2: Interim Fix 75
Operational Decision Manager V8.7.1.2: Interim Fix 76
Operational Decision Manager V8.7.1.2: Interim Fix 65
Operational Decision Manager V8.8.0.1: Interim Fix 83
Operational Decision Manager V8.7.1.2: Interim Fix 77

APAR status

• Closed as program error.

Error description

• After adding an additional checkpoint/category on rules, and
  merged these rules from main branch to release branch,  some
  merged rules on release branch show empty rule content (rule
  properties still exist)
  

Local fix

Problem summary

• When mergin changes occured in rules from a branch b1 to a
  branch b2. The rules are merged but the rules content are lost
  in branch b2.  The cause here is that queries that retrieve the
  element details in a branch needs all the element information
  to be available in this branch. If the element is not updated
  in this branch, the queries will retrive information from
  parent branch hierarchy. However, once an element is updated in
  a branch, all its data including aggregations need to be
  available in this branch. This part was missing. Only data
  updated by the first merge was recorded in the branch, then
  aggregations are missing.
  

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