APAR status
Closed as program error.
Error description
Summary: -------- Rose import renames all forks sequentially and considered naming joins also as forks Description: ------------ Rose import renames all forks sequentially rather than accepting the name in the Rose model. This appears to only happen with the fork, not the join which means that there is no correlation between the fork-join pair in naming. Business Impact: ---------------- Affects the naming convention as part of the model integrity checking. Steps to reproduce: -------------------- Attached is the Rose model and the Rhapsody results. 'Import from Rose' entry on the 'Tools' drop down. Observe: Neither the fork nor the join imported the name. Additionally, the join is named as a fork. PMR 80808,033,000
Local fix
Problem summary
Rose import renames all forks sequentially and considered naming joins also as forks
Problem conclusion
Fixed in 7.5.2
Temporary fix
Comments
APAR Information
APAR number
PM03053
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-08
Closed date
2010-06-11
Last modified date
2010-06-11
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
R750 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
11 June 2010