IBM Support

PI35223: Sub-states terminating prematurely

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • The model has parallel substates.
    
    The first substate has parallel substates.  This returns
    immediately, without processing the substates.
    The second substate has parallel states (not substates) and
    returns after both have received and event.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of version 810                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Sub-states terminating prematurely in an AND State           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please look at UML specification in section regarding        *
    * "Completion transitions and completion events" (completion   *
    * transitions are null transitions in Rhapsody). This section  *
    * defines that when completion transitions are going from      *
    * composite states (states that contain other states) or       *
    * submachines (sub-statecharts in Rhapsody) the source state   *
    * should reach a termination state in order to decide it was   *
    * completed. So, it is mandatory for such states to contain    *
    * termination state. Once a termination state is added to      *
    * waitingOne sub-statechart, the behavior is as expected and   *
    * the null transition from it is not activated. A new          *
    * code-generation check was added and Rhapsody generates a     *
    * warning "Composite state that has a null transition leaving  *
    * it must contain a termination state." to notify the user for *
    * the need of adding termination state.                        *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI35223

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    810

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-02-17

  • Closed date

    2015-06-26

  • Last modified date

    2015-06-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R813 PSY

       UP



Document information

More support for: Rational Rhapsody

Software version: 8.1

Reference #: PI35223

Modified date: 26 June 2015