PM55494: Updating dependent list in 7.1.2.* Clearquest using OSLC fails when parent fields share a value

Rational ClearQuest Fix Pack 07 (7.1.2.7) for 7.1.2
Rational ClearQuest Fix Pack 03 (8.0.0.3) for 8.0
Rational ClearQuest Fix Pack 14 (7.1.2.14) for 7.1.2
Rational ClearQuest Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearQuest Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearQuest Fix Pack 15 (7.1.2.15) for 7.1.2
Rational ClearQuest Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearQuest Fix Pack 16 (7.1.2.16) for 7.1.2
Rational ClearQuest Fix Pack 17 (7.1.2.17) for 7.1.2
Rational ClearQuest Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearQuest Fix Pack 18 (7.1.2.18) for 7.1.2
Rational ClearQuest Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearQuest Fix Pack 19 (7.1.2.19) for 7.1.2
Rational ClearQuest Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearQuest Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearQuest Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearQuest Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearQuest Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearQuest Fix Pack 21 (8.0.0.21) for 8.0

APAR status

• Closed as program error.

Error description

• Updating three level ( or more)  dependent  list   doesn't work
  in 7.1.2.* Clearquest with OSLC ( 1.0 ? 2.0)  when a value is
  common between the two parent fields.
  
  Let's say dependency is between Project-? Subproject-?SW_num,
  all three being stateless record types.
  Project b1p1 has subprojects b1p1s1 and b1p1s2.
  Project b1p2 has subprojects b1p2s1 and b1p1s2. See how  b1p1s2
  is common between the two, although they are two separate
  subproject records.
  Each Subproject has its own separate set of SW_NUM values.
  Say  there is a Defect with value b1p1 for project and b1p1s2
  for Subproject and then corresponding SW_NUM. If you try to
  modify the record  using 'PUT'  call in OSLC  giving  values
  b1p2 for Project,  b1p1s2 for Subproject and  correct SW_NUM for
  this combination, it fails  saying  'The field 'SubProject' is
  mandatory; a value must be specified' and ' The field 'SW_num'
  has values not permitted by its choice list'....
  
  Same use case works  in 7.1.1.* with OSLC 1.0, but errors out in
  7.1.2. *.  Fails using 7.1.2.4 and  technote
  http://www-01.ibm.com/support/docview.wss?uid=swg21507620.
  It  works using OSLC if  I update   b1p2 for Project,  b1p2s1
  for Subproject (value not shared between projects).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Updating three level (or more) dependent list fields using
  OSLC ( 1.0 ? 2.0) gives an error on ClearQuest 7.1.2.x when
  a value is common between the two parent fields.
  

Problem conclusion

• A fix is available in ClearQuest 7.1.2.7 and 8.0.0.3.
  

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 UNIX

• Fixed component ID

  5724G3601

Applicable component levels

• R712 PSN

     UP