IBM Support

Transition Priority sometimes ignored in Rational Statemate

Question & Answer


Question

Why is transition priority in IBM Rational Statemate sometimes ignored in simulation, in code generation and by Rational Statemate ModelChecker tool?

Cause

A statechart, which contains transition priority settings, changes its execution behavior when transition priority is ignored. This usually results in non-determinism errors.

Answer

Transition priority can only be used when Rational Statemate is running in developer mode (run_stmm.bat is started with switch -Extended).

Developer mode is the default installation mode when MicroC code generation and Design Attributes are available.

The other mode is classic mode where transition priority is not available in all functions like code generation, simulation and in external add-ons.

Note: As of Rational Statemate 4.6.1.5, an additional check model warning has been added to warn you when a model contains transition priority settings but Rational Statemate is running in classic mode:

Example:

(2123) Transitions with priority settings (not supported in current mode).

[{"Product":{"code":"SSYQ4J","label":"Rational Statemate"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General Information","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.5;4.6;4.6.0.1;4.6.0.2;4.6.0.3;4.6.1;4.6.1.1;4.6.1.2;4.6.1.3;4.6.1.4;4.6.1.5;4.6.1.6;4.6.1.7;4.6.1.8","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21470930

Page Feedback