IBM Support

PM87802: Importing a Rose model gives a 'IRJA0172W ...' error on a message that is valid

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you import an IBM Rational Rose model into IBM Rational
    Software Architect, the ' IRJA0172W '??Rose Message?? ?Message?
    foo( )' should be a(n) asynchCall or synchCall named foo.' '
    error results for a message on a sequence diagram that is valid.
    
    The following steps reproduce the problem:
    
    1. Create a Rose model with two classes A and B
    2. Add an operation 'foo' to the class B
    3. Add a sequence diagram
    4. Drop the two classes onto the sequence diagram
    5. Draw a message from the A object to the B object
    6. Assign 'foo()' to the message
    7. Save the changes and close Rose
    8. Import the Rose model into RSA
    9. Validate the model
    
    Result: The 'IRJA0172W '??Rose Message?? ?Message? foo( )'
    should be a(n) asynchCall or synchCall named 'foo.' error
    message appears, even though the message was a valid one in the
    Rose model.
    
    Workarounds:
    
    --?Right click on the error message ? Disable the 'Message
    signature' constraint
    OR
    --?Right click on the error message ? Fix the message name
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In Rational Rose, the message name is set as operation name
    followed by parameter types in parenthesis and the same gets
    imported into Rational Software Architect. This name is
    invalid according to UML constraints in Rational Software
    Architect.
    

Problem conclusion

  • This problem was fixed by setting the message name as just
    the operation name if such a pattern is detected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM87802

  • Reported component name

    RATL SW ARCHITE

  • Reported component ID

    5725A3000

  • Reported release

    851

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-25

  • Closed date

    2013-06-17

  • Last modified date

    2013-06-17

  • 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

    RATL SW ARCHITE

  • Fixed component ID

    5725A3000

Applicable component levels

  • R851 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"851","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"851","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2013