Version 2003.06.13
Release Date: September 2004
Last Updated: 09/02/2004
Material ID/Part Number: GI11-5904-03
© 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-03
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
Compatibility
Issues
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.13 Release Notes contain updates for the version 2003.06.13 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 |
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.
Previously, upon clicking on the operations dropdown list of the Specification dialog of a Call Message, the operations listed would only include the public operations of the receiver class. This has been enhanced when using RTJava.
Now, the operations dropdown list of the Call message Specification dialog will display operations of the receiver class, as described below.
A new registry string value "OpsVisibility" under the registry key "HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose RealTime\6.5" will determine the method visibility behavior (per user basis) in Sequence diagrams.
- If OpsVisibility="2", the operations list will display all operations. The list will include public, private, protected and implementation operations of the receiver class.
- If OpsVisibility="1", the operations list will only display 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 OpsVisibility is set to a value other than "1" or "2", or the OpsVisibility registry entry is not included in the registry, the Operations list will only display the public operations, as before.
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: OpsVisibility="2"
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())
Case 2: OpsVisibility="1"
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 3: OpsVisibility is not set to "1" or "2" or the registry entry of OpsVisibility is not included in the registry
The operations list will display the public operations of the receiver class (original default behavior).
Limitations:
The Rose RTJava Improvement to Method Visibility in Sequence Diagrams has the following limitations:
If OpsVisibility="1":
When the Receiver class is a nested (inner) class, the operations drop-down list does not show any operations.
In the example above, when the Receiver class "class2" is a nested class of the Sender class "class1", the operations list will be empty.
Workaround: Set "OpsVisibility" to "2". The operations list will then display all of the Receiver class operations.
Hot Link "operation" will not work (i.e. operation specification dialog will not open) correctly on an operation after resetting OpsVisibility to a value more restrictive than originally used to display the operation in the operations list.
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:
Reviewing the Latest version of the Release Notes and Service Release Notes
Notice to Customers Running Earlier Releases of Rational Rose RealTime on Windows
Reviewing the Latest version of the Release Notes and Service Release Notes
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/or 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.
The accompanying .gz or .exe files from the Service Release are no longer required. However, if you want to retain these files if a re-installation is required, you can move the tar files to <ROSERT_HOME>/specials.
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.825.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.
No additional steps are required.
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.
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.
For additional information on licensing, see You Must Install License Keys to Run this Product.
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 RATLC516372, 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 or greater. 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.
Note: In any cases where name shortening is applied to the name/SQL name of the data-modeling element, the SQL name field in the model will not be updated in the model.
RATLC00246172 / IC41967 | Analysis RRTEI Collection classes will not work correctly with out-of-proc calls. |
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 a activity chart (i.e. 8 DIN A4 pages), may cause Rose RealTime to crash. |
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. |
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. |
RATLC00517294 / IC38263 | All RRTEI Relocate Methods should return Boolean values, as indicated in Online Help. Some of the methods that currently do not return Boolean values are "RelocateClass", "RelocateLogicalPackage" and "RelocateClassDiagram". The methods "RelocateCapsule", "RelocateProtocol" and "RelocateCollaboration" currently do return Boolean values correctly. |
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. |
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. |
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. |
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 / IC40673 | 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 | Rose RealTime C TargetRTS RTPubl/CapClass.h: struct _RTCapsule_class should be rearranged to remove padding inserted for alignment. |
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. |
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. |
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. |
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/
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.