PM03053: ROSE IMPORT RENAMES ALL FORKS SEQUENTIALLY AND CONSIDERED NAMING JOINS ALSO AS FORKS

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 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