IBM Support

PM36390: connector cannot be attached to an attribute

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Description
    -----------
    In the attached model, On drawing the binding connectors between
    the attributes and a constraint property, the binding connectors
    are not owned by Z; they have package scope.
    
    More importantly, the binding connectors are relationships
    between itsA and A in C, and between itsB and B in C. They do
    not relate to itsC at all!
    And the constraint blocks cannot be re-used to represent
    multiple constraint configurations.
    
    WA : For binding connector we have a way by doing 'Bind to
    Context' which will set tag values with the part context
    
    However binding connectors are terms based on flows and that is
    why they behave like that - in SysML binding connectors are
    stereotypes of connectors
    But in Rhapsody a connector cannot be attached to an attribute
    because of compliance issue.
    
    Customer stumbled on this non-compliant behavior.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    connector cannot be attached to an attribute
    

Problem conclusion

  • 1. We modified the policy of owning connectors in Libra -
    now connectors are owned by the "from" side. If you draw a
    binding connector from itsA:int and C::A the binding
    connector will be owned by Z. If you draw a connector from
    C::A to itsA:int, the connector will be owned by C. This is
    our new definition and I believe it is the best we can do
    for now.2. We have created "bind to context" especially to
    overcome the fact that we use flows for binding connectors
    instead of connectors. The reason for that is that Rhapsody
    does not allow links/connector between an attribute and a
    part. However we have it on our roadmap to allow such
    connectors in the future, and once we have that capability
    we will change binding connector to be applicable to
    connector/link instead of a flow. Please enter a customer
    enhancement request to re-enforce the need of this change
    (although it is already on our plan).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM36390

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-06

  • Closed date

    2011-06-23

  • Last modified date

    2011-06-23

  • 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

  • R752 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.2","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
06 January 2022