Fixes are available
APAR status
Closed as program error.
Error description
If a filter is set on the requirments modules, Gateway sees the covered requirements even if they are ignored by the DOORS filter Consequently, Gateway may try to remove the links from UML to requirements but this operation is affected by the DOORS filter and is not able to find the requirements, causing a Can't find object error to be shown Workaround: close all modules (or turn off filters)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Clear DOORS filtering of other DOORS modules (covered DOORS documents for instance). Fixed problem when the Link target is pointing to a baseline (source object in the exported document, target object is selected in a baseline). (see also RTC bug 167835 that might be fixed now instead of Won?t Implement).
Problem conclusion
Fixed in Scorpio
Temporary fix
Comments
APAR Information
APAR number
PM38805
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
753
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-10
Closed date
2012-09-21
Last modified date
2012-09-21
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
TLOGIC RHAPSODY
Fixed component ID
5724V74RP
Applicable component levels
R753 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.3","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
27 October 2021