PM18221: SITEAREAS CANNOT BE ORDERED AS REQUIRED

APAR status

• Closed as program error.

Error description

• Unable to move siteareas within a single parent. When you try to
  move, you get the message that the move was successful but the
  structure remains the same and the sitearea has not moved.
  
  In the JCR Explorer, the site area nodes have the same position
  which is an exponential number, for example:
  
  /contentRoot/icm:libraries[20]/Content/Site/SiteArea1
  ibmcontentwcm:position[1.2749989484E12]
  
  /contentRoot/icm:libraries[20]/Content/Site/SiteArea2
  ibmcontentwcm:position[1.2749989484E12]
  
  The position also remains the same after trying to move one of
  the siteareas.
  

Local fix

Problem summary

• The positioning calculations are done using doubles but
  converted to floats to work around a JCR issue. The precision of
  the double calculation was lost in the conversion which (when
  the position number was large enough) caused the siteareas to
  remain in the same position.
  

Problem conclusion

• The position is now kept as a double when setting the value in
  the JCR which maintains the necessary precision. Testing proved
  that this no longer is an issue for the JCR.
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R615 PSY

     UP