PK89236: Irrelevant error message and inconsitent ReqWeb behaviour trying to (un)mark an indirect trace suspect

APAR status

• Closed as program error.

Error description

• In IBM Rational RequisiteWeb 7.1:
  When opening a traceability matrix that shows indirect traces -
  and then try to 'mark suspect' an indirect trace, the following
  error occurs:
  'Number of relationships for which this operation failed: 1
  The traceability relationship for Requirement xx has changed sin
  ce your last update'
  
  This is an inappropriate error message.
  It should simply say: 'You cannot (un)mark suspect an indirect t
  race' - or something like that.
  In fact it should not even be possible to (un)mark an indirect t
  race suspect.
  This is inconsistent compared to RequisitePro client: In ReqPro
  client these options are greyed out for indirect traces.
  ================
  Steps to reproduce:
  1) In ReqWeb 7.1 create traceability matrix view and activate th
  e 'Indirect traces'-Flag.
  2) Show the view and make sure that there is a indirect trace.
  
  3) Right-click on the indirect trace and select 'add suspect'
  
  --? Error 'Number of relationships of which this operation faile
  d: 1
  The tracability relationship for requirement XX has changes sinc
  e your last update'.
  
  ================
  

Local fix

Problem summary

• Invalid error message when trying to Add/Remove Suspect from
  an indirect trace
  

Problem conclusion

• Ignore request to Add/Remove Suspect for indirect traces.
  

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

  REQUISITEPRO WI

• Fixed component ID

  5724G3900

Applicable component levels

• R701 PSN

     UP