Version 2003.06.14
Release Date: December 2004
Last Updated: 12/09/2004
Material ID/Part Number: GI11-5904-04
© Copyright IBM Corporation. 1999, 2004. All Rights Reserved.
Any reproduction or distribution of this work is expressly prohibited without the prior written consent of IBM Corporation.
These Release Notes are accurate at the time this product was prepared for release.
The most recent version of this file is available in the IBM Publications at
www.ibm.com/shop/publications/order.
Search for GI11-5904-04
to find the latest version of these Release Notes in the IBM Publications Center.
(To search for the IBM Publications Center, go to www.ibm.com and enter
"IBM Publications Center" in the Search field.)
These IBM Rational Rose RealTime release notes provide:
Go to Rational Rose RealTime Service Release Notes if you are upgrading for Service Release note information.
When you are ready to install IBM Rational Rose RealTime, be sure to check the Web for the latest available downloads:
1. Go to http://www.ibm.com/software/rational/support/.
2. Then, go to the Download Center and navigate to Rational patches and service releases.
Also remember to have the Rational Rose RealTime Installation Guide available to provide all the information you need to complete your installation.
Important
Notice !!
(Read before Installing)
What's New in This Release
Product Documentation
Late
Changes to Documentation
Hardware/Software Information
Getting Started
Service Release Notes
Contacting IBM Rational Customer Support
We recommend that you read this Release Note file before you install or use Rational Rose RealTime.
Note: In some cases, you may notice discrepancies between the printed documentation, the online documentation, and this file. In these cases, this Release Note file (located in the directory <ROSERT_HOME>/rosert_readme.html) is the most up-to-date and should be followed.
The Rational Rose RealTime Service Release 2003.06.14 Release Notes contain updates for the version 2003.06.14 product release by addressing defects identified in Rational Rose RealTime. For more information on the defects addressed in this release, see Defects Fixed in This Release. This Service Release also includes an Addendum document. This addendum provides you with important information regarding Rational Rose RealTime versions. The information in this addendum supersedes the information found in the online Help and hardcopy documentation included in Rational Rose RealTime version 2003.06.00. You can find the pdf for the book Addendum, Rational Rose RealTime located in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf.
The following table identifies some of the Rational Web addresses that were updated in this release. If you encounter a link that is no longer active, use the http://www.ibm.com/ link and perform a search on your desired topic.
| Area | Web Address | Phone |
| Support | http://www.ibm.com/support/ | 1-800-IBM-SERV |
| AccountLink | http://www.ibm.com/software/rational/support/licensing/ | 1-800-IBM-SERV |
| Training and Education | http://www.ibm.com/services/learning/ | 1-800-IBM-TEACH
(1-800-426-8322) |
| Technical Publications | http://www.ibm.com/software/rational/support/documentation/ | 1-800-IBM-SERV |
| Rational Software Products | http://www.ibm.com/software/rational/ | 1-800-IBM-SERV
|
Note: It is only necessary to utilize this enhancement if you are encountering slow performance when attempting to display the Sequence Diagram Role List.
A new option has been included in the Rose RealTime Tools > Options dialog, which can significantly enhance performance when attempting to display a large role list. A new check-box option "Sequence diagram role list size" is added to the "Picklists" section of the Options dialog. By default, the check-box is unchecked and there is no limit to the size of the role list to be displayed (role list size < 0 also produces default behavior).
Checking the "Sequence diagram role list size" will allow you to enter a threshold value of the maximum role list size. Adding a new interaction instance which causes the role list to exceed the set threshold value, will produce the following results which ultimately improves the role list display performance.
- Role list efficiently displays and scroll bar of the list becomes inactive.
- You may traverse the list, using the Up and Down arrows, Page Up / Page Down, Home / End to move to the starting / end of the list, or enter the starting letter of the role name.
The following new methods have been added, equivalent to the methods
shown in parentheses. The new methods will return a boolean value
(True = successful, False = Failed).
A new Add-In called RUPSE(Rational Unified Process Systems Engineering) is shipped with this release. Refer to the file "Add-In Release Notes.doc" in the [ROSERT_HOME]/RUP-SE folder for more information on how to install and use this Add-In.
Two new operators may be used in search expressions:
- "&" = "and" (To find entries in the model having both "foo" and "bar" the following search expression can be used - "foo & bar")
- "|" = "or" (To find entries in the model having either "foo" or "bar" the following search expression can be used - "foo | bar")
To search for '&' and '|' use the escape character, for example to search for '&' the search string would be \&.
- Move the Source Control file of a controlled unit to a different directory under source control.
This moves the controlled unit under source control (i.e. corresponding file) to the destination directory (i.e. another package)Syntax: Moved = theApplication.move( pElements, destDirectory )
Moved As Boolean - Returns a value of True if the controlled unit in pElement was moved to the directory 'destDirectory' successfully.
theApplication As RoseRT.Application - The running instance of Application.
pElements As RoseRT.ControllableElementCollection - The collection of elements to move.
destDirectory As RoseRT.ControllableElement - Destination directory where this file (containing the controlled unit) to be moved.
- Remove the Source Control file of a controlled unit from the model as well as from source control.
Removes the model element and also removes the controlled unit from source control.Syntax: Removed = theApplication.remove( pElement, comment )
Removed As Boolean - Returns a value of True if the controlled unit in pElement was removed successfully from source control.
theApplication As RoseRT.Application - The running instance of Application.
pElements As RoseRT.ControllableElementCollection - The collection of elements to remove.
- Rename the Source Control file of a controlled unit.
Renames the model element and also renames the controlled unit in source control.Syntax: Renamed = theApplication.rename( pElement, nameTo )
Renamed As Boolean - Returns a value of True if the name of the controlled unit in pElement was changed to 'nameTo' successfully.
theApplication As RoseRT.Application - The running instance of Application.
pElement As RoseRT.ControllableElement - The controlled unit to rename.
nameTo As String - New Name for the file containing this element.
comment As String - Comments to provide to Source Control server for the operation.
To create a #defined constant or a constant variable - please refer to Rose RealTime online Help. The information below explains how to create a constant global variable using Rose RealTime.
To Create a Global C/C++ constant
- Create a class and name it appropriately.
- Create an attribute in this new class. This will be the constant In the New Attributes C++ Properties tab, change the AttributeKind field to Global.
- In the Attributes Detail tab, set the Type and Initial Value for the constant.
- Set the changeability option to Frozen.
- Add a dependency between the class where the constant is defined, and the capsules or classes that use the constant.
- If the constant is Global, ensure that the Dependency C++ Properties are: KindInHeader = inclusion, and KindInImplementation = none.
To Use a Global constant variable
- Create an explicit dependency between the class which uses the constant and the class where the constant is defined. (This was not previously required.)
- While using the constant in the cardinality, use the fully qualified name of the constant. For example:- The constant is defined as "const1" in the class "A" and class "B" has an aggregation relation with class "C". The aggregation relation has a cardinality of const1, it has to be defined as "A::const1" instead of "const1".
- Also, in order to export the constant as a variable you will need to use the flag ( -fexport-constant-as-variable in addition to the flags -spacedeps, dq, -system etc. ) for exporting the constant as a variable to a header file while generating the source code for the model. In order to utilize cardinality make these changes to your "<ROSERT_HOME>\C++\targetRTS\codgen\rtgen.mk" file, by adding
RTGEN = rtcppgen -fexport-constant-as-variable, as indicated above.A #define May be Used to Define Cardinality
Previously, Rose RealTime used to extract the value of the constant and insert it where the #define / constant was being utilized. Now, you may use the variable name, instead of the constant value. The variable will also get exported in a *.h file as a #define / constant.
By default the operations dropdown list of the Specification dialog of a Call Message would only include the public operations of the receiver class. This default behavior has been enhanced when using RTJava such that the operations list will display only those operations that are valid according to Java language specifications (see below).
Validity of the operations depend upon the following access specifications:
- Public - Any sender class in any package has access to a receiver class's public operations
- Private - Accessible only when sender class and receiver class are the same
- Protected - Accessible to subclasses (which can be in other packages) and all sender classes in the same package
- Implementation or Default - Accessible to the sender classes which are in the same package of the receiver classes
You will now be able to access the RTJava operations (from the "Call Message Specification" dialog) according to the access rules indicated above.
If the user wants to see all the operations of the receiver class, the registry string value "OpsVisibility" under the registry key "HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose RealTime\6.5" should be set to “1”. Then, the list will display public, private, protected and implementation operations of the receiver class.Note: If the receivers class language is not RTJava, the original behavior remains - only the public operations of the receiver class are listed.
RTJava Example
Consider the following example where a Rose RealTime model has two classes. Let the class names be class1 and class2. The Receiver's class language type is RTJava.
Assume class1 has the following operations
1. class1_public_op() - public operation
2. class1_protected_op() - protected operation
3. class1_private_op() - private operation
4. class1_implementation_op() - implementation operation
and class2 has the following operations
1. class2_public_op() - public operation
2. class2_protected_op() - protected operation
3. class2_private_op() - private operation
4. class2_implementation_op() - implementation operationLet class1 be the sender class and class2 be the receiver class.
Case 1: Default behavior
- Sender and Receiver are in Same Package
The public, protected and implementation operations of the receiver class are displayed (class2_implementation_op(), class2_protected_op(), class2_public_op()).
- Receiver Class is an Outer Class of the Sender Class
As the Inner Sender Class can see all of the operations of the Outer Receiver Class, the list includes the private, protected, public and implementation operations of the receiver class (class2_implementation_op(), class2_private_op(), class2_protected_op(), class2_public_op()).
Case 2: OpsVisibility="1"
The operations list will display all the operations of the receiver class class2:
(class2_public_op(), class2_protected_op(), class2_private_op() and class2_implementation_op())
Limitation:
The Rose RTJava Improvement to Method Visibility in Sequence Diagrams has the following limitation:
Hot Link "operation" will not work (i.e. operation specification dialog will not open) correctly on an operation, if we select an operation in the operations dropdown list when OpsVisibility =”1” (the operation should not be shown by default in the list), and then we reset the OpsVisibility to a value other than “1”.
Refer to http://www-1.ibm.com/support/docview.wss?uid=swg21117982 for further information, describing:
Known Issues related to this Add-In
How to Create a Shareable External Library Interface without utilizing the External Library Generation Add-In
Documentation for IBM Rational is available on-line at http://www.ibm.com/software/rational/support/documentation/.
Additional information about this release is available in the Addendum, Rational Rose RealTime, located in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf.
You can find the minimum supported configuration requirements for running Rational Rose RealTime on Linux, UNIX, and Windows platforms in the chapter "Referenced Configurations" in the Addendum, Rational Rose RealTime located in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf.
In addition to the supported Operating Systems in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf, this Release supports the following Operating Systems.
The following files from LEAD Technologies, Inc., are included in this release:
For the most recent documentation updates, visit the Product Support section of the Rational Rose RealTime web site at:
http://www.ibm.com/software/rational/support/
Where printed documentation exists, always refer to the online Help or PDF versions of the book for the latest updates.
When you are ready to install IBM Rational Rose RealTime, be sure to check the Web for the latest available downloads:
1. Go to http://www.ibm.com/software/rational/support/.
2. Then, go to the Download Center and navigate to Rational patches and service releases.
Please read the following notes before you install Rational Rose RealTime:
Rose RealTime v2003.06.13 Required in order to Install Rose RealTime v2003.06.14
Notice to Customers Running Earlier Releases of Rational Rose RealTime on Windows
Rose RealTime v2003.06.14 is a Service Release which is installed onto Rose RealTime v2003.06.13. Rose RealTime v2003.06.13 must be installed on your machine before installing v2003.06.14. Rose RealTime v2003.06.14 is not a complete release, and includes only the updated files necessary to provide the Enhancements / Fixes described in this v2003.06.14 Release Note.
Review the Rational Rose RealTime Installation Guide for detailed instructions on how to install your license keys and how to request permanent license keys. To obtain permanent license keys, you can access AccountLink from http://www.ibm.com/software/rational/support/licensing/.
For information on contacting IBM Rational Customer Support, see Contacting IBM Rational Software Support.
You cannot run Rational Rose RealTime 2002.05.xx or earlier versions with the latest version of Rational Rose RealTime on Microsoft Windows NT, Microsoft Windows 2000, and Microsoft Windows XP Pro. You must uninstall Rational Rose RealTime 2002.05.xx and earlier versions before installing Rational Rose RealTime 2003.06.00 and this Service Release.
If you encounter any difficulties uninstalling previous versions of Rational Rose RealTime, refer to the Solutions document "Manually uninstalling Rose RealTime on Windows." for additional help.
For additional information on issues with Rational Rose RealTime (prior to v2003.06.13), see the chapter, "General Issues" in the Addendum, Rational Rose RealTime located in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf.
For help on the new and modified information included in this Service Release, see the Rose RealTime Release Notes, located in <ROSERT_HOME>/rosert_readme.html.
Run the toolset and ensure that the build number is correct. In Rational Rose RealTime, click Help > About Rational Rose RealTime and verify that the version number for Rational Rose RealTime is 6.5.1232.0. If the build number is not the same, this Service Release was not applied correctly.
Note: If you wish to take advantage of the problems fixed in the code generators, you need to rebuild and re-link your models.
No additional steps are required.
Note: If you wish to take advantage of the problems fixed in the RTJava code generator, you need to rebuild and re-link your Java models.
No additional steps are required.
Note: If you wish to take advantage of the problems fixed in the C++ TargetRTS, you need to rebuild your Target RTS libraries and re-link your models, including DCS.rtmdl.
The fields in the C Structs have be been reordered to remove padding between the fields. With this change the models using C TargetRTS must be recompiled at all ends (if model deployed, recompile at both server and client sides). The models compiled with this change may not be compatible with the models compiled earlier.
Note: If you wish to take advantage of the problems fixed in the code generators, you need to rebuild and re-link your models.
Note: If you wish to take advantage of the problems fixed in the DCS, you need to rebuild and re-link your models. It will also be necessary to rebuild the DCF library if your target is not one of the pre-built DCF libraries supplied in this Service Release.
For additional information on licensing, see You Must Install License Keys to Run this Product.
Rose RealTime v2003.06.14 is a Service Release which is installed onto Rose RealTime v2003.06.13. Rose RealTime v2003.06.13 must be installed on your machine before installing v2003.06.14. Rose RealTime v2003.06.14 is not a complete release, and includes only the updated files necessary to provide the Enhancements / Fixes described in this v2003.06.14 Release Note.
After you install a Rational product, you must restart your system before applying this service release. Do not apply this service release until you have restarted your system after installing a Rational product. See RATLC00516372, below.
RATLC00516372 - If the Rational Setup Wizard does not appear when you apply this service release, use Windows Task Manager to end one of the msiexec.exe processes. The Rational Setup Wizard window should appear. If it still does not appear, cancel the next msiexec.exe. As a result, installation of this service release should be successful. Workaround: Restart you system before applying this Service Release.
Under certain circumstances, file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has enabled the Windows "Change Journal" (log). This corruption is caused by a defect in Windows 2000. Before you install any Rational Version 2003 product on Computer that is running Windows 2000:
If you are installing Rose RealTime v2003.06.01 or greater as an upgrade to an existing installation of Rose RealTime 2003.06.00, the Rose RealTime TargetRTS files may not update (install) correctly. In order to avoid unpredictable results, uninstall Rose RealTime v2003.06.00 before installing Rose RealTime v2003.06.01 - v2003.06.13. This is a known issue: RATLC00517283.
Some features
included in AnalystStudio have duplicate component IDs causing issues with
upgrades to this product. As a result, if you are upgrading IBM Rational Suite
AnalystStudio v2003.06.01or v2003.06.12 to this service release, you must first
uninstall AnalystStudio before installing v2003.06.13 of this product.
Attempting to install this release as an upgrade to IBM Rational Suite
AnalystStudio v2003.06.01or v2003.06.12 will cause unpredictable runtime results
as release files may not be updated correctly.
If you install Rational Suite DevelopmentStudio, and then install the Rational Rose RealTime point product, select Add-Ins > Add-In Manager and select the appropriate add-ins, such as SoDA, RequisitePro, and Trace Tool. Selecting these tools activates the integration of Rational Rose RealTime with those tools.
When installing Rational Rose RealTime on Microsoft Windows, or starting Rational Rose RealTime for the first time after installing, you may receive an error message indicating the following:
"suite objects.dll" cannot be found in the path."
This problem only occurs on Microsoft Windows NT systems that have had a previous version of Rational Rose RealTime installed. To solve this problem, add "C:\Program Files\Rational\common" to your Path variable.
| RATLC00210339 / IC39660 | Rose RealTime Web Publisher can consume a large amount of memory when Web Publishing large models. |
| RATLC00246172 / IC41967 | Analysis RRTEI Collection classes will not work correctly with out-of-proc calls. |
| RATLC00515542 / IC37530 | Rose RealTime Web Publisher may not publish Activity Diagrams correctly. |
| RATLC00516159 / IC41774 | The
RRTEI functions componet.AddInclusionPath and component.AddUserLibrary
do not function as expected. Both functions return true which
indicates that the inclusion / userlibrary has been created although it
has not been. Workaround: Locate the property in the RRTEI associated with the data to be updated (i.e. "inclusion path") and override the value. |
| RATLC00516547 | Enhancement request for Rose RealTime Model Integrator to establish dependency information between nodes and automatically resolve dependent nodes and hide properties of little interest. |
| RATLC00520561 / IC40188 | Unable to rename a package using some Chinese characters when running Rose RealTime on Simplified Chinese or on English Windows with the system default locale set to Simplified Chinese. |
| RATLC00523150 / IC41231 | In Rose RealTime CPP, making a change to a large source file and subsequently requesting a codesync may cause Rose RealTime to hang. |
| RATLC00526499 / IC42118 | Connexis CRM connection not re-established in certain situations. |
For additional information on compatibility issues, see the Product Support section of the Rational Rose RealTime web site at:
http://www.ibm.com/software/rational/support/
Version 2003.06.14, December 2004
Product changes described in this document and contained within this service release apply to:
The Service Release Notes includes:
|
RATLC / APAR ID |
Description |
| RATLC00045230 RATLC00045807 | Unable to differentiate between ports with identical names
when inserting a Connector (Capsule Spec).
New description class to represent Port Roles has been added. It will display a Port Role using it's name followed by the containing Capsule Role's name in brackets. The lists presented will now request a "detailed" description of the items in the list vs. the simple name of the items (as requested previously). |
| RATLC00238358 | Unable to delete Activity Diagram through Capsule Specification dialog. |
| RATLC00249084 | The full association relation name may not display correctly. |
| RATLC00372858 | Opening a RoseRT model in which a null pointer was being de-referenced when attempting to draw relation views on the diagram would cause Rose RealTime to crash. |
| RATLC00513320 | Trigger is not displayed for transition for conjugated ports (if port created as aggregation on class diagram). |
| RATLC00515538 | Errors when launching Rose RealTime on Windows 2003 / XP
Platforms. Rose RealTime uses HKLM to write it's registry
settings. Since a restricted user does not have write access to HKLM,
Rose RealTime does not wok when run under a restricted user.
Now using HKCU for storing Rose RealTime registry settings. When Rose RealTime is installed, the installer will add all of the settings in HKLM. During runtime, Rose RealTime will add changes to the registry entries in HKCU. |
| RATLC00515540 / IC39587 | Attempting to select "Zoom > Fit In Window" from the diagram window or selecting "Fit to page" in Print dialog and then selecting "Print Preview" for an activity chart (i.e. 8 DIN A4 pages), may cause Rose RealTime to crash. |
| RATLC00516276 / IC37365 | Upon
adding a new Port to a CapsuleStructure there are no warnings or errors
shown when a Port with the same name already exists. When this
occurs the model will become inconsistent. In addition, when loading
a model with this issue warnings are shown indicating that duplicate Ports
need to be renamed. However, the StructureDiagram shows multiple
PortViews per Port.
Now an error message "The Name "duplicate_port_name" is illegal because it already exists."is displayed when attempting to add a port with a duplicate name. |
| RATLC00516283 | Rose RealTime Model Integrator can cause duplicate transitions and junction points. |
| RATLC00516562 | New attributes have been added to C and C++ properties. These changes are in the property files (.pty and .rtpty) found in the folder [ROSERT_HOME]/C and [ROSERT_HOME]/C++. |
| RATLC00517294 / IC38263 | All RRTEI API's for relocating classes, capsules,etc. from
one package to another package should return a boolean value to indicate
whether or not the move was successful. The following API's do not
return a boolean value:
New methods have been added, equivalent to the methods above, but which will return a boolean value:
Syntax of the new methods are the same as the original methods. |
| RATLC00517805 / IC38611 | Incorrect components are offered as a choice when attempting to Browser Header / Browse Brody. You must verify which class the component is associated with to determine which component to select. If you select the wrong component, you will encounter an error. |
| RATLC00518162 | RQA-RT executable may crash just prior to end of run. |
| RATLC00518863 / IC39179 | Rose
RealTime Model Integrator will not generate QUID for junction point views
upon merging in models created with Rose RealTime 2002. The
following steps, illustrate this behavior:
Rose RealTime 2002 does not generate QUID for junction point views after the first save. |
| RATLC00519064 | Enhancement allowing you to toggle transitions from self internal to external. You may now toggle multiple self transitions from either external to internal or from internal to external using the option from the Parts menu. You may also toggle single self transitions by right clicking on the self transition and choosing the toggle option from the context menu. |
| RATLC00520102 / IC39764 | When a Stop build request is made, the code generator stops
the build rather than terminating the worker thread. The termination
of the worker thread is instigated by the Rose RealTime viewer when all
dependents (including processes) are cleaned. In this case the
process (cmd.exe) which gets created does not terminate therefore Rose
RealTime does not terminate the build thread.
To resolve this issue, the termination of the worker thread is instigated from the code generator. |
| RATLC00520462 | Request to enable regular expressions in search function.
The following two new operators are added:
To search for '&' and '|' use the escape character, for example to search for '&' the search string will be \&. |
| RATLC00520463 / IC40056 | Find results not displayed properly when right clicking and
selecting "find in browser".
Now, the parent diagram of the Item view selected is highlighted in the Browser window, when the "Select In Browser" option is selected in the Find Pane. |
| RATLC00520597 / IC40273 | Model Integrator may produce a corrupt model when merging (i.e. rebasing) the file with Rose RealTime 2003 version 6.5.725.0. Model Integrator removes pipe "|" characters. Model Integrator does not handle merged multi line documentation correctly. |
| RATLC00521864 / IC40612 | The
following error message can occur when attempting to open a Rose RealTime
model through a workspace using a ClearCase Snapshot view:
Error: Could not run script to get source control capabilities: The shell command ""C:\Progra~1\Rational\RoseRe~1\bin\win32\rtperl" -w "C:\Program Files\Rational\Rose RealTime\bin\win32\cmscripts\cc\cm_getcaps"" did not terminate in the specified timeout.. Workaround: Open the *.rtmdl file and turn on SourceControl after the model is loaded. |
| RATLC00522023
/ IC40673 |
The
Rose RealTime C TargetRTS Build flat option does not include header
files from $ROSERT_HOME/C/TargetRTS/build-<your config>.
Workaround: Add the following line to your config.mk file: TARGETCCFLAGS = $(INCLUDE_TAG)"$(RTS_HOME)/build-$(TARGET).$(LIBRARY_SET) " |
| RATLC00522046 | Rose
RealTime C TargetRTS build flat option does not copy RSL.h and
UMLRT.h to the build-<your config>/RTPubl directory.
When building the Rose RealTime C TargetRTS flat, Rose RealTime regenerates the TargetRTS header files in the directory $ROSERT_HOME/C/TargetRTS/build-<your config>. All the #include <...> have been changed to #include "...". Unfortunately, two header files in $ROSERT_HOME/C/TargetRTS/include/RTPubl are not regenerated (RSL.h and UMLRT.h). Workarounds: Modifying RSL.h and UMLRT.h and placing them in libset/<your_libset>/RTPubl or changing the two files in include/RTPubl to use #include "...". |
| RATLC00522099 / IC41974 | RT Publ/CapClass.h: struct_RTCapsule_class should be
rearranged to remove padding inserted for alignment.
NOTE: With this change the models using C TargetRTS must be recompiled. The models compiled with this change may not be compatible with the models compiled earlier |
| RATLC00522227 RATLC00524492 |
Enhancement providing ability to paste messages in Sequence
Diagram in any location rather than just to the end of the role lifeline.
Three new menu items are added to the Sequence Diagram context menu. These menu items will be highlighted when right-clicking on a message:
|
| RATLC00522973 / IC41068 | Unable to compile classes with a nested class, which is
protected or private.
If the type descriptors are generated of non-public nested classes, the generated class files will not compile. This is due the design of the type descriptor structure. Now, for non-public nested classes a warning is displayed indicating that type-descriptors are not generated for this class rather than generating the descriptors silently. |
| RATLC00523798 / IC41976 | C TargetRTS RTPubl/Message.h padding warning when compiling the C TargetRTS with the Cygwin compiler and the -W padded option. |
| RATLC00524571 / IC41470 | Connexis
enabled application may cause exception when deregistering SPPs on
shutdown.
Workaround:
|
| RATLC00525237 / IC41575 | Using
Rose RealTime C, Timer_data_union doesn't compile when
RTMESSAGE_PAYLOAD_SIZE=0.
Timer_data_union.rtclass has been changed. The models need to be re-compiled at both ends ((if model deployed, recompile at both server and client sides). |
| RATLC00525328 / IC41600 | Rose RealTime link errors may occur due to the fact that the link order is determined by the order that the dependencies were added to the packages. Prior to Rose RealTime 2003, the order was based on the order of the dependencies added. Those added first were linked first. In Rose RealTime 2003 the reverse order is applied, which may cause link failures. |
| RATLC00525351 / IC41665 | Rose
RealTime / SoDA generated Sequence Diagrams are not identical.
In Rose RealTime, if the Sequence Diagram includes many arguments (args) to the method, the method signature is drawn as method(arg1, arg2, ...). However when the SoDA report is generated all the parameters are completely displayed which makes the report difficult to read. |
| RATLC00526175 / IC41994 | RTProtocol::size()
crash on Connexis
Rose RealTime applications may crash while calling port > size, when disconnections and reconnections of ports occur frequently. |
| RATLC00526263 / IC42051 | The size of activities in Activity Diagram elongate when launching Rose RealTime by double-clicking on the *.rtwks file. |
| RATLC00526855 / IC42203 | Rose RealTime C generates incorrect code if the end names of two or more aggregations are the same. |
| RATLC00529128 / IC42948 | Rose RealTime TargetRTS may read and write to deleted memory. |
[ROSERT_HOME]bin\win32\AddExternalJava.dll
[ROSERT_HOME]bin\win32\AddExternalJavaRes.dll
[ROSERT_HOME]bin\win32\modelintRT.exe
[ROSERT_HOME]bin\win32\modelintRTres.dll
[ROSERT_HOME]bin\win32\RoseRT.exe
[ROSERT_HOME]bin\win32\RrtRes.dll
[ROSERT_HOME]bin\win32\rtcbld.dll
[ROSERT_HOME]bin\win32\rtcgen.exe
[ROSERT_HOME]bin\win32\rtcppbld.dll
[ROSERT_HOME]bin\win32\rtcppgen.exe
[ROSERT_HOME]bin\win32\rtjavagen.exe
[ROSERT_HOME]bin\win32\rtjavaui.dll
[ROSERT_HOME]bin\win32\rtrun.exe
[ROSERT_HOME]bin\win32\cmscripts\cc\cm_remove
[ROSERT_HOME]bin\win32\cmscripts\cc\cm_rename
[ROSERT_HOME]bin\win32\cmscripts\cc\cm_move
[ROSERT_HOME]bin\win32\cmscripts\pvcs\cm_remove
[ROSERT_HOME]bin\win32\cmscripts\pvcs\cm_rename
[ROSERT_HOME]bin\win32\cmscripts\pvcs\cm_move
[ROSERT_HOME]bin\win32\cmscripts\msvss\cm_remove
[ROSERT_HOME]bin\win32\cmscripts\msvss\cm_rename
[ROSERT_HOME]bin\win32\cmscripts\msvss\cm_move
[ROSERT_HOME]\C\c.pty
[ROSERT_HOME]\C\CTargetRSL.rtpty
[ROSERT_HOME]\C\RTCClasses\TimerPackage\Timer_data_union.rtclass
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\Capsule.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\SystDesc.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\Message.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\MsgQueue.inl
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\ThrdDesc.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\Decoding.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\Control.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\CapClass.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\main.h
[ROSERT_HOME]\C\TargetRTS\include\RTPubl\Version.h
[ROSERT_HOME]\C\TargetRTS\src\include\RTPriv\LayerCon.h
[ROSERT_HOME]\C\TargetRTS\src\include\RTPriv\MsgBlock.h
[ROSERT_HOME]\C\TargetRTS\src\include\RTPriv\DebugInp.h
[ROSERT_HOME]\C\TargetRTS\src\include\RTPriv\Debugger.h
[ROSERT_HOME]\C\TargetRTS\src\Message\static.c
[ROSERT_HOME]\C\TargetRTS\src\main.mk
[ROSERT_HOME]\C\TargetRTS\src\main.nmk
[ROSERT_HOME]\C\TargetRTS\src\Build.pl
[ROSERT_HOME]\C\TargetRTS\lib\eCos20020128_uITRON302T.x86-gnu-2.95.3\*
[ROSERT_HOME]\C\TargetRTS\lib\NoRTOSS.sparc-gnu-2.8.1\*
[ROSERT_HOME]\C\TargetRTS\lib\NT40S.x86-VisualC++-6.0\*
[ROSERT_HOME]\C\TargetRTS\lib\NT40T.x86-VisualC++-6.0\*
[ROSERT_HOME]\C\TargetRTS\lib\NT40T.x86-VisualC++-7.0\*
[ROSERT_HOME]\C\TargetRTS\lib\NoRTOSS.x86-VisualC++-6.0\*
[ROSERT_HOME]\C\TargetRTS\lib\OSE411T.ppc603-Diab-4.3f\*
[ROSERT_HOME]\C\TargetRTS\lib\OSE411T.sparc-gnu-2.95.1\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO2S.m68040-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO2S.ppc-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO2S.x86-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO2T.m68040-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO2T.ppc-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO2T.x86-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO22T.ppc603-Diab-5.0.1\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO22T.ppc603-gnu-2.96\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO22T.simnt-gnu-2.96\*
[ROSERT_HOME]\C\TargetRTS\lib\TORNADO22T.simsparcsolaris-gnu-2.96\*
[ROSERT_HOME]\C++\cpp.pty
[ROSERT_HOME]\C++\C++TargetRTS.rtpty
[ROSERT_HOME]\C++\TargetRTS\include\RTVerson.h
[ROSERT_HOME]\C++\TargetRTS\src\RTActor\predestroy.cc
[ROSERT_HOME]\C++\TargetRTS\src\RTActor\get_indirect.cc
[ROSERT_HOME]\C++\TargetRTS\lib\CHORUS40T.ppc603-egcs-2.91.66\*
[ROSERT_HOME]\C++\TargetRTS\lib\LYNX30T.ppc-cygnus-2.7-97r1\*
[ROSERT_HOME]\C++\TargetRTS\lib\LYNX30T.x86-cygnus-2.7-97r1\*
[ROSERT_HOME]\C++\TargetRTS\lib\LYNX31T.ppc-gnupro-2.9-98r2\*
[ROSERT_HOME]\C++\TargetRTS\lib\NoRTOSS.sparc-gnu-2.8.1\*
[ROSERT_HOME]\C++\TargetRTS\lib\NoRTOSS.x86-VisualC++-6.0\*
[ROSERT_HOME]\C++\TargetRTS\lib\NT40T.x86-VisualC++-6.0\*
[ROSERT_HOME]\C++\TargetRTS\lib\NT40T.x86-VisualC++-7.0\*
[ROSERT_HOME]\C++\TargetRTS\lib\NUCLEUS11T.x86-VisualC++-6.0\*
[ROSERT_HOME]\C++\TargetRTS\lib\OSE411T.ppc603-Diab-4.3f\*
[ROSERT_HOME]\C++\TargetRTS\lib\OSE411T.sparc-gnu-2.95.1\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO2T.m68040-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO2T.ppc860-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO2T.ppc-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO2T.simpc-egcs-2.90.29\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO2T.simso-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO2T.x86-cygnus-2.7.2-960126\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO22T.ppc603-Diab-5.0.1\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO22T.ppc603-gnu-2.96\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO22T.simnt-gnu-2.96\*
[ROSERT_HOME]\C++\TargetRTS\lib\TORNADO22T.simsparcsolaris-gnu-2.96\*
[ROSERT_HOME]\C++\TargetRTS\lib\WINCE300T.sh3-eMVisualC++-3.0\*
[ROSERT_HOME]\Connexis\bin\win32\ConnexisViewer.exe
[ROSERT_HOME]\Connexis\bin\win32\ConnexisViewerRES.dll
[ROSERT_HOME]\Connexis\bin\win32\ConnexisRES.dll
[ROSERT_HOME]\Connexis\bin\win32\Connexis.dll
[ROSERT_HOME]\Connexis\bin\win32\TraceData.dll
[ROSERT_HOME]\Connexis\Model\DCS.rtmdl
[ROSERT_HOME]\Connexis\C++\examples\MetricsCollector.rtmdl
[ROSERT_HOME]\Connexis\C++\lib\LYNX30T.ppc-cygnus-2.7-97r1\*
[ROSERT_HOME]\Connexis\C++\lib\LYNX30T.x86-cygnus-2.7-97r1\*
[ROSERT_HOME]\Connexis\C++\lib\NT40T.x86-VisualC++-6.0\*
[ROSERT_HOME]\Connexis\C++\lib\OSE411T.ppc603-Diab-4.3f\*
[ROSERT_HOME]\Connexis\C++\lib\TORNADO2T.ppc860-cygnus-2.7.2-960126\*
[ROSERT_HOME]\Connexis\C++\lib\TORNADO2T.ppc-cygnus-2.7.2-960126\*
[ROSERT_HOME]\Connexis\C++\lib\TORNADO2T.simpc-egcs-2.90.29\*
[ROSERT_HOME]\Connexis\C++\lib\TORNADO2T.simso-cygnus-2.7.2-960126\*
[ROSERT_HOME]\RUP-SE\* (This is a new Add-In)
Note:
[ROSERT_HOME] is the
directory that the IBM Rational Products are installed in. This is
typically "C:\Program Files\Rational\Rose RealTime*".
Version 2003.06.13, September 2004
Product changes described in this document and contained within this service release apply to:
| RATLC00246421, 519781 / IC39701 | Rose RealTime may hang upon selecting File > Control Unit. When the model is controlled, each Model element (example UseCase etc) are stored in a separate file. Rose RealTime verifies that each file name is unique and generates unique file names for each element. The file name is generated based on the element name given by the user. The general form of the file name is <user given element name>. Extension. An error occurs when attempting to generate a unique file name if the element name contains a "." |
| RATLC00246676 / IC39633 | RoseRT may crash and produce the following error, when
loading a model with a hyperlink: NT Exception 001B:005C2C20 |
| RATLC00247365 | Enhancement to add Sequence Diagram name to RQART messages.
RQART now displays the name of the test along with the test number that had passed / failed in the test summary pages. |
| RATLC376345 / IC39736 | Expansion levels in the Query toolbar option, do not work properly. For example, the value levels in Selected Elements cannot be reset to 1 once they are set to level higher than 1. |
| RATLC00516355 | Toolset crash can occur after configuring capsule for both Connexis CRM and CDM, twice. For example, occurs when trying to configure the same capsule for Connexis after re-opening the model. |
| RATLC00516591 / IC37635 | Code generation HeaderPreface can be incorrect if the last character in the HeaderPreface is not a newline character. |
| RATLC00517053, 519068 / IC38052 | Rose RealTime Toolset times out when using the RoseRT / ClearCase / ClearQuest integration and "Window trigger selection" - "V2" |
| RATLC517297 / IC37917 | Slow display of role list for interaction instance on a Sequence Diagram. (See "Enhancement for Slow Performance when Displaying Sequence Diagram Role List", the Rose RealTime Release Notes). |
| RATLC00518307 / IC38924 | Generation of dependencies is incorrect for makefiles in relation to Java components. |
| RATLC00518507 / IC37876 | After modifying a controlled collaboration diagram which includes children ,under source control, then performing an undo checkout of the collaboration diagram may cause references to the children to be lost. |
| RATLC00518786 / IC39194 | Model corruption occurs, on Japanese OS, when including actors in collaboration diagrams. |
| RATLC00518787 / IC39069 | Connexis CDR / ASCII Encoding does not function correctly when working with data for which the size is greater than 64K. |
| RATLC00518788 / IC39070 | Connexis Viewer metrics collection does not function correctly if the component instance is using ASCII encoding / decoding (-CNXtde-1). |
| RATLC00518847 / IC37316 | Slow model validation for large enumeration (i.e. several attributes included). |
| RATLC00518960 / IC39135 | Nested classes result in an incorrect collaboration classifier role. (If a nested class is used as a collaboration classifier role, the classifier identified on the classifier role specification points to an incorrect class.) |
| RATLC00518986 / IC37640 | Rose RealTime Toolset may crash when copying and pasting Choice-point. |
| RATLC00519013 IC39198 | The Check Unique identifiers presence function does not scale to large models. |
| RATLC00519023 / IC37640 | RoseRT may crash and display the following error when
deleting send signal that has text attached and then saving the model: NT Exception 001B:0000.. |
| RATLC00519049 | Class shape becomes smaller on a diagram, upon adding an aggregation. |
| RATLC00519193 | Transition Labels may incorrectly relocate upon editing state diagrams. |
| RATLC00519208 / IC37851 | Unresolved references from Interactions to roles may occur, where for example a role is specified by a capsule which is included in nested capsule roles due to decomposition. |
| RATLC00519209 / IC37360 | Sending enum in Connexis does not function correctly in Rose RealTime 2003. When data is sent from the sender, Connexis tries to decode the data. If the decode fails, it is ignored. This is due to the fact that the CodeGen does not generate data type installer code for the enum datatype, which helps decoding data. |
| RATLC00519358 | Disabling the Add-In, "External Library Generation". See http://www-1.ibm.com/support/docview.wss?uid=swg21117982 for further information. |
| RATLC00519456 / IC39013 | The Connexis Viewer truncates long messages (longer
than 4096 bytes) even when the component uses the following command line
options: CNXatud=-1 -CNXtmts=CRM:65500 -CNXtbp=64:1,600,32:65500:16 |
| RATLC00519465 | Faulty renaming of state in superclass, causes RoseRT to crash upon loading model. |
| RATLC00519781 / IC39701 | RoseRT may hang upon selecting File > Control Unit if an included element name includes the "." character. |
| RATLC00520349 / IC39882 | Unable to decode nested enum implemented according to the enumerated stereotype. For a nested class, both the outer and inner class is installed. However, this is not the case for the enumeration. The code generator should install RT Type_Enuminner as well. |
| RATLC00520380, 520437, 520663 / IC39934 | Error executing "rterror.pl", due
to use of uninitialized variables: Use of un-initialized value at rterror.pl line xxx |
| RATLC00520393 / IC39947 | Unresolved pathmap occurs when relative pathmaps are used for external documents. (Sequence Diagram). |
| RATLC00520402 | Rose RealTime C++ code
generator will not build components where two components refer to the same
class. When the component being built references two different
components that have the same referenced items, the following error may
occur: Error: The name of this class (from component 'Component View::Three') is not unique in component 'Component View::One' NMAKE : fatal error U1077: 'rtcppgen' : return code '0x3' Stop. New command line option available, "-fignore-dup-names" which can be set to ignore the duplicate name conflicts when a component is referring to two other components, and both of which are referring to the same class. This would be allowed even if name conflicts exist. |
| RATLC00520425 / IC39999 | Enhancement to remove the "-nostdinc" flag from the TargetRTS for Tornado 2.2. |
| RATLC00520598 / IC40273 | Model Integrator may create corrupt model when merging file with Rose RealTime 2003, as pipe characters are incorrectly removed. |
| RATLC00521496 / IC40535 | Model line colors are not saved correctly. |
| RATLC00521728 / IC40581 | External document links don't work correctly when using pathmaps. |
| RATLC00521821 / IC40591 | Font color for Default Font is not saved correctly, if font color is set to black. |
| RATLC00522059 / IC40688 | TargetRTS may be missing in Tools Menu for Rose RealTime 2003.06.12. Corrected by adding the necessary registry entry. |
| RATLC00522223 | Enhancement in Rose RealTime Java to improve method visibility in Sequence Diagram. See "Rose RTJava Improvement to Method Visibility in Sequence Diagrams" in the Rose RealTime Release Notes. |
|
RATLC000522638 / IC41029 |
Upon attempting to load
the latest version of a Rose model could result in the following error: Error: Error reading file C:\rose_sample.mdl at line XXX Fix included to maintain compatibility with newer Rose petal file format. |
| RATLC00522942 | Connexis CRM application enters tight loop when Connection is broke at the server end. This consumes 100% of CPU cycles before the rtUnbound is received. The problem does not occur with CDM. |
|
RATLC00524473 / IC41405 |
Memory Leak in Connexis DCS.rtmdl |
A copy of the IBM Rational Rose RealTime Service Release 2003.06.12 Release Notes and list of fixed defects is available in the IBM Publications at www.ibm.com/shop/publications/order. Search for GI11-5904-00 to find the latest version of these Release Notes in the IBM Publications Center. (To search for the IBM Publications Center, go to www.ibm.com and enter "IBM Publications Center" in the Search field.)
The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support homepage can be found at http://www.ibm.com/software/support.
Voice Support is available to all current contract holders via a telephone number in your country (where available). For specific country phone numbers, please refer to the IBM Software Support Handbook, Appendix B: Contact Information, found at http://www.ibm.com/software/support.