PM54373: OSLC REQUESTS DO NOT RETRIEVE NEWLY CREATED FIELDS UNTIL CM SERVER IS RESTARTED

APAR status

• Closed as Permanent restriction.

Error description

• If a new field is added to a schema and the user database is
  updated, an OSLC request to get the value of that new field in a
  record will not return it.
  
  A query to get the properties of the record will not return the
  newly added field in the list of existing fields. In the same
  way, fields that have been removed will continue showing up as a
  record property.
  
  Schema updates are not retrieved, the original schema revision
  is cached.
  
  Workaround: Restart the IBM Rational Change Management (CM)
  Server profile.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  ClearQuest OSLC requests do not retrieve newly created fields
  (or updated schema) until CM Server is restarted
  

Problem conclusion

• After analysis of this APAR, we have determined we won't fix thi
  s issue due to (1) the large effort and risk of a fix and (2) a
  straightforward workaround of restarting the ClearQuest Web Serv
  er (see http://www-01.ibm.com/support/docview.wss?uid=swg2165099
  9).
  
  A priority decision has been made that this defect cannot be add
  ressed in the next 18 months without neglecting issues of higher
   importance and less risk.  Thank you for your understanding.
  

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

Applicable component levels