PH49193: INTERMITTENT DOWNCASING OF RECORD TYPE NAME 'RELEASE' TO 'RELEASE' IN OSLC XML OUTPUT, NOT JSON

APAR status

• Closed as program error.

Error description

• Use case - 1:
  When you run OSLC queries to fetch details of ClearQuest record
  type (ex: Release record type), the OSLC query output includes
  this record name as 'release' instead of 'Release'. Note that
  the first letter is lower case 'r' instead of upper case 'R'.
  
  Impact: If the OSLC tools are implemented in a way that they are
  searching for specific nodes via Xpath. And Xpath is
  case-sensitive. This means that usually the tool searches for an
  upper-case ⠜Release⠝ in the xml-file. If ⠜release⠝ is
  written lower-case it means that the tools will interpret it as
  0 result. In case of bad programming the result can even be a
  nullpointer-exception.
  
  
  Use case - 2:
  >> If you restart the CM server so nothing is cached yet, then
  run: "https://localhost:9451/cqweb/oslc/repo/<repo
  name>/db/<user db
  name>/record/?oslc_cm.query=belongsToProject.belongsToPoolProjec
  t="<record id>" and
  Type="PVER"&rcm.type=RELEASE&oslc_cm.properties=id,Title,Externa
  lTitle,LifeCycleState,PlannedDate,ActualDate,Tags&rcm.startIndex
  =1001&oslc_cm.pageSize=1000"
  
  you will get results containing all uppercase "RELEASE".
  
  >> Now go onto another machine and try the request with
  "Release" and you will also get results with "RELEASE" - the
  first request has initially cached "RELEASE".  Whichever case is
  used by the first session into cqweb through OSLC is persisted.
  
  
  >> Also, if another request goes to a different CM server
  through load balancer it is likely to be inconsistent this way.
  That could possibly be the case with a paged result which would
  explain some but not all of their inconsistencies.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ClearQuest OSLC                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In ClearQuest OSLC, if the record type name is input via     *
  * rcm.type in the request, it will display as case insensitive *
  * in the response.                                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A fix is available in ClearQuest 9.0.2.7 and 9.1.0.4.
  In ClearQuest OSLC, a property is introduced in
  cqrest.properties, so setting the value to true to display the
  record type name in the response with the case designed in
  schema.
  

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

  CLEARQUEST WIN

• Fixed component ID

  5724G3600

Applicable component levels