IBM® Rational® Rose® RealTime V2003.06.13 & V2003.06.14 Fix Pack 1 Readme
June 2005

© Copyright IBM Corporation. 1992-2005. All Rights Reserved.
Any reproduction or distribution of this work is expressly prohibited without the prior written consent of IBM Rational.
Legal Notices Information

Scope
This Fix Pack includes Defect Fixes and Enhancements for Rose RealTime Windows V2003.06.13 and V2003.06.14.
Hardware/Software Information
Hardware / Software requirements for this Fix Pack are the same as those described in the Installation Guide for Suites v2003.06.00.
Getting Started
In addition to the instructions provided in the "Getting Started" section of the Rose RealTime Windows 2003.06.00 Release Notes, please review the following information new in this Fix Pack for Rose RealTime V2003.06.13 or V2003.06.14.
Hot Fixes Not Included in Rose RealTime V2003. 06.13 / V2003.06.15 Fix Pack 1
The Fixes (shown for the Hot Fixes) listed in the table below are not included in this Fix Pack.  These fixes were finalized after the code was complete for Fix Pack 1.  The following fixes will be included in the next Rose RealTime Service Release V2003.06.15.
Rose RealTime V2003.06.14 Hot Fixes	
Hot Fix 8	Model Integrator	RATLC001077226 / IC44949	Rose RealTime Model Integrator may generate incorrect output causing Rose RealTime to crash.	
Hot Fix 9	Model Integrator	RATLC00142245 / IC45775	Model Integrator truncates the state names in transition source points.	
Hot Fix 10	rtcgen	RATLC00142221 / IC45742	The struct _RTLogicalThreadInstanceDescription was updated in TargetRTS.  The fields in the struct were re-ordered to remove padding between the fields and the structs.  An update was required in the Codegen (rtcgen).	
Licensing
No licensing changes are required when installing this Fix Pack.
Installation Instructions
Note:  [Release_Location] is the Rational Products installation directory.  This is typically "C:\Program Files\Rational".  If your [Release_Location] is not “C:\Program Files\Rational”, edit the following entries in your ”install_Rose_RealTime_2003r3_r4_FixPack1_06.09.2005.bat” file before proceeding with the next steps:
@set HF_INSTALLDIR="C:\Program Files\Rational\Rose RealTime"
@set CORBA_REG="C:\Program Files\Rational\Rose RealTime\CORBA\CorbaRegistry65.reg"

To Complete Installation:
1.	Rose RealTime V2003.06.13 or V2003.06.14 must be installed prior to installing this Fix Pack.  (This Fix Pack is applicable to Rose RealTime V2003.06.13 or V2003.06.14.)
2.	Backup your existing release.
3.	Place the following files in a temporary directory: 
o	install_Rose_RealTime_2003r3_r4_FixPack1_06.09.2005.bat
o	Rose_RealTime_2003r3_r4_FixPack1_06.09.2005.exe
Run  install_Rose_RealTime_2003r3_r4_FixPack1_06.09.2005.bat

The following preliminary information will display – press Enter to continue:
=======================================================
Rose RealTime 2003.06.13 or 2003.06.14 Fix Pack 1
                  Product:  Rose RealTime
Installs and Registers
Rose RealTime 2003.06.13 or 2003.06.14 Fix Pack 1
%TEMP%\RoseRT_2003r3_r4_FIXPACK1_ERRORLOG.log will include a listing
of any errors encountered while installing this Fix Pack. 
Contact Rational Technical Support if you encounter any Installation Errors.
=======================================================
Press any key to continue . . .
Rose RealTime 2003.06.13 or 2003.06.14 Fix Pack 1...
•	The “WinZip Self_Extractor” dialog will display.  Change to the correct [Rational_Location] if it is not “C:\Program Files\Rational”.  Select “Unzip”.

You will see the following message box, Select “OK” and then Select “Close” in the original “WinZip Self_Extractor” dialog (see, above).

In the Command Prompt Window you will see the following messages:
Rose RealTime 2003.06.13 or 2003.06.14 Fix Pack 1...
Registering Rose RealTime Fix Pack1 DLLs ...
Creating CORBA Add-In Registry Entries ...
All Registrations Completed Successfully!
•	You will then see a message in the Command Prompt Window indicating that the Fix Pack was successfully installed:
Removing %TEMP%\RoseRT_2003r3_r4_FIXPACK1_ERRORLOG.log
=======================================================
Rose RealTime 2003.06.13 or 2003.06.14 Fix Pack 1
    Successfully Installed
=======================================================
Press any key to continue . . .
If you encounter any errors during the installation of this Fix Pack, refer to the error log:  
%TEMP%\ RoseRT_2003r3_r4_FIXPACK1_ERRORLOG.log which will include a listing of the errors.  If no errors were encountered, this file will not exist.
Product Documentation
Documentation for IBM Rational is available on-line at http://www.ibm.com/software/rational/support/documentation/.
Compatibility Issues
This section describes any compatibility issues that could arise from use of this Fix Pack.
With Rational Products
This Fix Pack does not introduce any compatibility issues with other IBM Rational products.
With Third-Party Products
This Fix Pack does not introduce any known compatibility issues with third-party products.
Enhancements & Defect Fixes
Core Rose RealTime Enhancements
•	Enhancement for Slow Performance when Displaying Sequence Diagram Role List
•	New RRTEI Methods
•	Enhancement to Enable Regular Expressions "and" & "or" in Search Functions
•	Ability to invoke Rename, Move and Remove commands on Controlled Units through RRTEI
•	Enhancements to the Rose RealTime Code Editor
•	New Option for Protocol Inheritance when Overriding Signals
Rose RealTime Model Integrator Enhancement
•	Rose RealTime Model Integrator Filter Enhancement
Rose RealTime CPP Enhancement
•	Ability to Define Cardinality in External Header File
Rose RealTime Java Enhancement
•	Rose RealTime Java Improvement to Method Visibility in Sequence Diagrams
Addition of CORBA Add-In
Addition of RUPSE Add-In
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 [Release_Location]/RUP-SE folder for more information on how to install and use this Add-In.

Enhancement for Slow Performance when Displaying Sequence Diagram Role List
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.
1.	Role list efficiently displays and scroll bar of the list becomes inactive.  
2.	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. 
New RRTEI Methods 
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).
•	RelocateClassEx (original:  RelocateClass) 
•	RelocateClassDiagramEx (original:  RelocateClassDiagram) 
•	RelocateLogicalPackageEx (original:  RelocateLogicalPackage) 
Enhancement to Enable Regular Expressions "and" (&) And  "or" (|) in Search Functions 
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 \&.
Ability to invoke Rename, Move and Remove commands on Controlled Units through RRTEI 
1.	Move the Source Control file of a ControllableElement to a different directory under source control.  
This moves the controllable unit under source control (i.e. corresponding file) to the destination directory (e.g., another package)  
Syntax: Moved = theApplication.move( pElements, destDirectory )
Moved As Boolean - Returns a value of True if the Controllable Element 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 element) to be moved.
2.	Remove the Source Control file of a ControllableElement from the model as well as source control.  
Removes the model element and also removes the controllable unit from the source control.  
Syntax:Removed = theApplication.remove( pElement, comment )
Removed As Boolean - Returns a value of True if the Controllable Element 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.
3.	Rename the Source Control file of a ControllableElement. 
Renames the model element and also renames the controllable unit in the source control.  
Syntax: Renamed = theApplication.rename( pElement, nameTo )
Renamed As Boolean - Returns a value of True if the name of the Controllable Element in pElement was changed to 'nameTo' successfully.
theApplication As RoseRT.Application - The running instance of Application.
pElement As RoseRT.ControllableElement - The controllable element 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.
Enhancements to the Rose RealTime Code Editor 
Note:  Word-wrap no longer an available or supported option in Rose RealTime Code Editor 
o	Automatic Syntax Highlighting

Language Keywords will appear in color.  You may choose a color preference for the automatic syntax highlighting feature, utilizing one of the following options: 
·         Change Color for Current Language – Right click on the Code Window and select Font, Color… 
·         Configure Color for any Language – Select Tools > Options > Font / Color tab, choose a language option from Code editor Font/Color pick list and click Configure. 
o	Automatic Auto Indent

The Rose RealTime Code Editor now automatically appends white spaces / tabs to a new line to create similar indentation to the previous line. 

o	Ability to search using regular expressions (and, searching a session) when utilizing Find / Replace capabilities 

o	Improved Undo / Redo Capabilities 

o	New Context Menu Options (Font, Color…, Line Numbers) added to the Documentation/Code (Ctrl+3) window pane (right bottom) and Capsule Operation, Detail tab.

o	Ability to Enable / Disable Line Numbering 

o	To Change Setting for Current Code Window – Right click on the Code Window and select or uncheck Line Numbers 
o	To Change Global Settings – Select Tools > Options > Editor, and check or uncheck Display Line Number

o	Ability to Create Custom Tab Size

The length of the tab character can now be varied.  To set the tab size: 

o	Select Tools > Options > Editor and set the Tab Size 

o	Ability to Expand Tabs with White Spaces

Tab characters may be replaced with white spaces.  To set tab character replacement: 

o	Select Tools > Options > Editor and check or uncheck Expand Tabs 

o	Improved Code Printing Features (Print Code dialog can be accessed via context menu > File > Print…) 

o	Ability to Print Preview Code document (This feature is not available for Browse Header and Browse Body functions) 
The following settings are set in the Options tab of the Print Code dialog and are persistent in the registry: 
o	Ability to add Header and Footer  - New variables added for Header / Footer ($page, $pages, $title) 
o	Ability to Enable / Disable Line Number when printing   
      Paper Type Selection & Orientation may be accessed through the “Properties…” button.
o	User Preferences for Color, Tab Size, Line Numbering, Header & Footer are automatically saved in registry when selections made from Toolset.  The default settings for these preferences are located in %ROSERT_HOME%\csyntax.ini and %ROSERT_HOME%\javasyntax.ini. 
Note:  Word Wrap is no longer included in these context menus as an option and is no longer supported. 
o	Internal Code Editor Options now available on Options > Editor Property Window

o	Code Editor Font / Color Options Available in the Options > Font / Color Window 

o	New Font / Color Configuration Dialog Available 
New Option for Protocol Inheritance when Overriding Signals
All changes in signals, which are inherited and overridden in children from the base class, will now show one additional message box asking if you would like to change all inherited overridden signals recursively. 

 Selecting “No” will lead to existing behavior  Upon selecting “Yes” all the overridden signals will be changed to the new parent signal type in all the inherited overridden instances of all Childs. 
On class diagram, the protocol context menu will carry one additional option “Show All overridden Signals”

Selecting "Show All Overidden Signals" will show all overridden signals only (not all inherited) in addition to current selections.
This preference can be applied globally by selecting the option "Show overridden Signals" @ Tools->Options->compartments->Protocols. This will be saved in $ROSERT_HOME/RoseRT.ini and will be effective once the toolset is restarted.

This option will be effective for all protocols added to diagram after this change without restarting the toolset.
Rose RealTime Model Integrator Filter Enhancement
Selecting Rose Model Integrator  Options > NewFiltering... presents a new Model Integrator Filter Settings dialog.  This dialog allows you to "Ignore All" of the GUI filter groups (including, properties) listed below, or you may select each GUI filter group individually (that you wish to ignore in the Model Integrator comparison or merge):
•	Locations (label location, coordinate data of an object, name location, coordinate data of the origin of an object, origin_x, origin_y, x_coord, x_offset, y_coord, y_offset) 
•	Dimensions (margin locations & margin width, grid size X & Y settings, height of diagram, icon height & width & Y offset, justify setting, maximum height & width of label tags, orientation, overlap setting of diagrams (for diagrams larger than one page), size, Bool value of snap to grid, Bool value of object visibility, width of object, zoom factor) 
•	Fonts (Bool value of bold, strike, underline & italics settings, default font value, font setting, icon style, line style, number of lines of text that must be written) 
•	Colors (color, fill color, default color, line color) 
•	Visibility (Bool value settings for autoresize, clip icon labels, show stereotypes, hidden,  include attributes, include operations, show message numbers in Sequence Diagram, show signatures for operations, suppress attribute & suppress operation.  Also includes boxed, icon, and navigable properties) 
By checking any of the filter groups (listed above) or "Ignore All", the Model Integrator will suppress all the differences associated with the selected filter groups among two or more contributors.  For example, checking the "Colors" filter group will ignore the differences in the color related properties while performing a compare and/or merge.
Selecting (checking)  Ignore All disables the individual selection of the filter groups as Ignore All will suppress the differences for all of the filter groups listed.
The Locations and Dimension filter groups allows you to enter the filter value in their respective edit box (positioned to the right of the "Locations" and "Dimension" filter check-boxes, respectively.  If the value entered (in pixels) for the two contributors is less than or equal to the property value then that property will not be shown with a difference or a conflict.  The other properties, "Fonts", "Colors" and "Visibility" do not have associated filter values.
Selecting the Filter options and selecting OK will save the filter settings for future sessions.
After loading two or more contributors in the Rose Model Integrator and subsequently changing the filter settings a message box indicating "You must reload contributors for this change to take effect" will be displayed.  In this case it will be necessary to open the Add contributor dialog again and click on Merge or Compare buttons depending on the operation being performed.  This message will not appear if the filter options are selected before adding any contributors.
The Rose RealTime Model Integrator Add-In lets you compare model elements from up to seven contributor files, discover their differences, and merge them into the base model.

Note:  The filter works only with values which have been set.  If any of the contributors don't have the value set ( ie. value set to <default> ), the filter will report a conflict, irrespective of the filter being chosen.  Those differences will be reported as conflict even if the option "ignore all" is chosen.
Ability to Define Cardinality in External Header File 
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
1.	Create a class and name it appropriately.   
2.	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.   
3.	In the Attributes Detail tab, set the Type and Initial Value for the constant.   
4.	Set the changeability option to Frozen.   
5.	Add a dependency between the class where the constant is defined, and the capsules or classes that use the constant.   
6.	If the constant is Global, ensure that the Dependency C++ Properties are: KindInHeader = inclusion, and KindInImplementation = none. 
To Use a Global constant variable
1.	Create an explicit dependency between the class which uses the constant and the class where the constant is defined. (This was not previously required.) 
2.	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". 
3.	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. 
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.
Rose RTJava Improvement to Method Visibility in Sequence Diagrams 
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 receiver’s 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 operation
Let 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”. 
You may disable this dialog box by enabling the check box. 
Addition of CORBA Add-In 
The CORBA Add-In is included in the Rose RealTime V2003.06.13 / V2003.06.14 Fix Pack 1.

To Enable the CORBA Add-In
Select Tools ->Option Click on the "Language/Environment" tab 
Under "Default language:" select CORBA 
Under "Default environment:" select CORBA

CORBA Add-In Limitations and Known Issues

1.  An explicit left click is required to select an element in the browser followed by a right click to display a context menu.
     Directly doing a right-click gives error in some situations.

2.  If an external process makes  "out_of_proc" COM REI calls, ensure that the desired program (either Rose or Rose RealTime, but not both) is registered as the REI COM server.

3.  The Help documentation for the CORBA Add-In may indicate Rose instead of Rose RealTime.
Note:  External Library Generation Add-In No Longer Available in this Release
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 
What To Do After Installation
Toolset
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.1536.0.  If the build number is not the same, this Fix Pack was not applied correctly. 
Code Gen
Note: If you wish to take advantage of the problems fixed in the code generators, you need to rebuild and re-link your models. 
RQA-RT
No additional steps are required.
RTJava Models
Note: If you wish to take advantage of the problems fixed in the RTJava code generator, you need to rebuild your Java models.
C TargetRTS
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.
C++ TargetRTS
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. 
C & C++ 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.
Connexis
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 DCS library if your target is not one of the pre-built DCS libraries supplied in this Service Release.

Rose RealTime Fix Pack 1 Defects Fixed
Rose Fix Pack1 includes the following Defect Fixes.

1.	Installing Fix Pack 1 in Rose V2003.06.14 -  Fixes from Table A.  Rose RealTime Fix Pack 1 Defect Fixes are included.
2.	Installing Fix Pack 1 in Rose V2003.06.13  - Fixes from Both Tables A. Rose RealTime Fix Pack 1 Defect Fixes; and Table B. Rose RealTime V2003.06.14 (Service Release 4) Defect Fixes are included.

Table A.  Rose RealTime Fix Pack 1 Defect Fixes

RATLC / APAR ID	Description	
RATLC00046261	Request to change RTTimespec member tv_sec from long to unsigned long.
 
Fixed by changing the variables holding the time info (fields in the structure "struct timespec") from "long" (32 bits wide) to "long long" (64 bits wide).	
RATLC00141022 / IC43828	Eclipse Integration files (EclipseIntegration.dll, EsclipseIntegrationRes.dll & EclipseIntegration.mnu) missing from Rose RealTime Release.	
RATLC00141283
RATLC00532405 / IC44325	Connector label may cause structure diagram to inappropriately resize (grow longer). 

The docking point of labels were not calculated until they were drawn.  Since the connector label was hidden, when user moved its parent, the move calculation returned a large move difference causing the issue.	
RATLC00141295 / IC44339	The field OperationKind (located in the Operation Specification > C++) set to "friend" is not working for an operation function with two arguments, for example: 

friend VirtualOstream & operator<<( VirtualOstream & Ostr,FocusLimitsEntity & FocusLimits );	
RATLC00141437 / PK00485	Rose RealTime may crash and dump core if OpenSpecification is used in RRTEI. 

The crash is happening due to accessing a member when the pointer is null.  In this case, the message is null and the code tries to get sender for that message.	
RATLC00141441
RATLC00529923 / IC44660, 44660	Rose RealTime Model Integrator may crash when petal files are large.	
RATLC00141729 / PK01846	Information in the data field may incorrectly be deleted.	
RATLC00249200 / IC42295	Copying a structure diagram to Microsoft Word will cause corruption to the image.	
RATLC00379154	RRTEI Model.FindModelElementWithID(id) doesn't return the ModelElement if id identifies a AnalysisStateDiagram. 
"FindModelElementsWithID" could not be used to find diagrams, since diagrams are not of type ModelElement.  The correct function is FindDiagramWithID, unfortunately this method was not exported in RRTEI.  Also, crash could occur while calling "GetFileName":- In this case, the crash is due to a null pointer access.  This happens, when the function is called on an object, that cannot be written into a separate file.	
RATLC00442471 / IC43154	Problems could occur with Protocol inheritance when overriding signals. 
When a protocol 'B' is derived from protocol 'A', 'B' inherits all the signals of 'A' with "Data Class".  However it is possible to override the inherited signals "Data Class" to any other type(Bool, int, char etc).
Once overriding the inherited signal, there is only one way to get back to the parent signal type and that is to manually find the signal type from parent('A') specifications or class diagram and then edit the child ('B') specifications appropriately.
If parent signal is changed, then that change is propagated only to those children who have NOT overridden that particular signal.
In a class diagram, there is no way to display inherited/overridden signals for children.  Only protocol specifications display the information about signals "Data Class".
Therefore, if one protocol is inherited by protocols, which override inherited signals, it is not possible to determine the overridden signals from the class diagram.
Fix included in Rose RealTime Fix Pack 1:
If a signal inherits and is overridden, and is changed at parent, a message box now displays and asking:
"Do you want to change all inherited overridden signals recursively?”

1.	Selecting "NO" will present the current behavior (described above). 
2.	Selecting "YES" will change all overridden signals (even if the signal is overridden in more than one child).

The protocol display on class diagram will now show an additional right click context menu option, "Show all overridden signals", which on selection will show all inherited overridden signals (both in and out signals).  This option is saved by Rose RealTime and the view attributes will be saved in the petal file.  Also to make this option available by default, one checkbox is added to options dialog (Tools->Options->Compartments->Protocols) "Show all overridden signals". Selecting this option, will by default show all overridden signals for newly added protocols.  This setting will be saved in <$ROSERT_HOME>/RoseRT.ini.	
RATLC00450865 / IC42649	Long Capsule Names are only partially shown with no indication that name is truncated.	
RATLC00513216	SingleDataCompilationUnit doesn't function correctly when passive classes generates statemachines.	
RATLC00515542 / IC37530	Rose RealTime Web Publisher may not publish Activity Diagrams correctly.	
RATLC00516473 / IC37543	RRTEI returns 6 instances of a single ChoicePoint in ModelElements for a StateDiagram. 

Now, filters the views obtained so as to eliminate the duplicate views related to each choice point.	
RATLC00516572	Addition of CORBA Add-In.  See CORBA Add-In under Enhancements, above.	
RATLC00517892 / IC38722	Rose RealTime Model Integrator merge result may become corrupted when calling Clear DiffMerge more than once during merge. 

When the Model Integrator writes out the merged file, it uses the data from only one of the calls to Clear DiffMerge.  It is not using the areas from which the information is displayed in the GUI.	
RATLC00519105 / IC39264	"Find In.." Dialog does not find inherited triggers and signals. 
The "Find In..." Dialog includes the following updates:

1.	“Find In” Dialog includes a new check box Item “Search Inherited fields within composite items”  
2.	This Check Box item is enabled when “Find In” Dialog is opened by right clicking on any item in the Browser Pane of Rose RealTime. This Check Box item is disabled when the “Find” Dialog is opened from Menu > Edit > Find. 
When this new Check Box Item is checked, Find includes Inherited properties of the current Item in the search and displays the results if the search criterion matches.	
RATLC00520196 / IC41972	RRTEI: "This object has been deleted" message can occur when using GetSendAnalysisAction().Arguments / Target.	
RATLC00522592 / IC41017	Transition name may move in State Diagrams.	
RATLC00526150 / IC41937	The code generator (C++) does not complete generation for bidirectional Composite associations when more than one exists for a given class at the Composite end.	
RATLC00528974 / IC42924	Error: Unable to find the component that owns this class.  Error message needs more information. 

Error message "Unable to find component that owns this class", has been enhanced to specifically indicate:i.e.:   "Unable to find the component that owns class SOMECLASSA Is <<C++ Library>> or <<C++ External Library>> component which references the class SOMECLASSA".	
RATLC00530195 / IC43296	Model Integrator unable to correctly merge Sequence Diagrams. Unable to handle conflicts when two new interactions have received the same interaction number by Rose RealTime.	
RATLC00530648 / IC43442	Rose RealTime Crash / Exception may occur after performing the following: 

1.	With any model enabled for Connexis running "Build > Add Class Dependencies". 
2.	Select all the dependencies the script finds and move them to the right side of the dialog and click OK. 
Add dependency if the class is modifiable by the mode.  if dependency cannot be added the following error message is displayed: 

"Dependency {ClassName} --> {Dependency Qualified Name} could not be added because it is not modifiable in this model."  ({ClassName} and {Dependency Qualified Name} are variables and are substituted with the actual names.)	
RATLC00531927	Edit in New Window not working properly. 

1.	Select Edit In New Window..., the Editor is invoked, but any code that was present in the original window/pane is not displayed. 
2.	Entering code and clicking OK to close the window (the code is not saved, so any original code is not overwritten).  If there was no original code, your work in the New Window is lost due to the failure to save the contents of the New Window when clicking OK. 	
RATLC00531328 / IC43845	When the Pick List is active, it’s not possible to use the scrollbar.  Only scroll wheel on the mouse or the arrows or page up and down are possible to use.  Request to fix, or to disable the scrollbar. 

1.	Enable the check box in the Rose RealTime Tool options (Tool->Options) dialog box.  Under the General tab find the checkbox for 'Sequence Diagram role list size' in the section Pick lists.  Check this box and enter a value > 0. 
2.	When the Specification dialog is open, only arrowkeys, pgup, pgdown, home, end and any single characters are allowed. 
3.	Now open the Specification dialog for an interaction instance.  You may observe a scroll bar but it has no affect.  You may only use the key strokes mentioned in #2, above. 	
RATLC00531332 / IC43845	When Tools->Options->General->Pick Lists is active the entries in the picklist will be shown when adding a new role.  However, after selecting one and opening the interaction instance specification for the newly created role, the list no longer displays.  See below for description of fix. 

1.	The option "Tools->Options->General->Pick Lists->Sequence diagram role list size" should be checked and a positive value entered in the edit option. 
2.	When an Interaction Instance is created, it will not populate the entire list in the list box.  Also, when the Specification for an Interaction Instance is opened it will only display a fixed number of elements in the Path combo window located under the General tab of Specification dialog. 
3.	When the drop down list displays, you may use the arrow keys, PgUp, PgDown, Home and End keys.  You may also use the character keys to quickly display the first role in the list, which starts with the letter entered.  After displaying the first role in the list, beginning with the letter entered, you may only use the down arrow key to traverse through the next listed roles. 
4.	Though the vertical scroll bar appears it is not functional.  The scroll bar is visible to alert the user, there are more elements in the list. If you wish to use the scroll bar then you will need to disable the Pick List option. 
5.	The list is sorted in the Combo box. 
Additionally, memory leak could occur whenever opening a Specification dialog for interaction instances by either checking the checkbox for "Sequence diagram role list size" under the "picklists" section in the options dialog or without checking the box. It could also occur when clicking the dropdown box after the Specification dialog box appears. This issue has also been fixed.
LIMITATION: If the role name is edited inside the combo box, when it is not drop down then pressing down arrow will not bring you to the next match in the list.  (However you may use a single character to take you to the next role name that starts with that character).  Once you enter the first character to move to a location in the list starting with that character you may navigate sequentially using the arrow key or page-up / page-down key.	
RATLC00532240	Class Diagram Toolbar may become truncated. 
After loading Rose RealTime model:
1.	Open a class diagram and a capsule state or structure diagram.  
2.	Click the mouse anywhere in the capsule diagram.  
3.	The toolbar looks ok.  
4.	Now, click anywhere in the class diagram.  
5.	The toolbar is missing some icons.  
6.	Now, click on the right or left edge of the toolbar 
7.	The remaining icons will suddenly appear.
 
Workaround:  Uncheck the "Allow Docking" feature by right clicking on toolbox and reposition toolbar so that it is in its own window in a non-docking state.	
RATLC00532473 / IC44661	QUID changes when moving an operation for a class / capsule causing incorrect results from Rose RealTime Model Integrator.	
RATLC00532502 / IC44770	Class Diagram may resize (elongate).	
RATLC00960034 / IC43498	Performing Rose RealTime Model Integrator merge may cause Model Integrator to crash saving an incomplete file.	
RATLC00960707	Rose RealTime sequence numbers for messages in sequence diagrams are not visible as attributes. 
Introduced a new RRTEI function GetMsgNumber() for Message which returns a string containing the number, displayed on side of the messagelabel.  This function calls returns the string retrieved by calling COMessage::GetNumber().	
RATLC00960983	Rose RealTime Model Integrator may crash upon saving model after merging.	
RATLC001079281 / IC45231	Updated LIBSET.MK file for TORNADO22T.PPC603-GNU-2.96 included in Rose RealTime Fix Pack 1.	
RATLC00960425	Unable to build CORBA component using RRTEI.

Now, you may build a component in automation mode by calling the Build/RebuildAll method on the component.  However RRTEI Add-Ins won't get enabled by default.  You will have to activate the CORBA Add-In from your code.	

Table B.  Rose RealTime V2003.06.14 Defect Fixes

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 Spec 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 work 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 a 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 [Release_Location]/C and [Release_Location]/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: 

RelocateClass 
Relocate ClassDiagram 
RelocateLogicalPackage 
New methods have been added, equivalent to the methods above, but which will return a boolean value:

RelocateClassEx 
RelocateClassDiagramEx 
RelocateLogicalPackageEx 

The 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: 

1.	Start Rose RealTime 2002 
2.	Switch on the generate unique IDs option.  
3.	Create a capsule, add a state and an initial transition to it.  
4.	Save the model (base.rtmdl).  
5.	Add a transition to self to the state.  
6.	Save the model with a new name (2002.rtmdl).  
7.	Study the model file, the junction point views for the junction created at the time of first save have a QUID.  The junction point views created at the time of the second and consequent saves do not have a QUID.  
8.	Open base.rtmdl in Rose RealTime 2003.  
9.	Add a transition.  
10.	Save the model as 2003.rtmdl.  
11.	Merge the base, 2002 and 2003 models, save the result.  
12.	Study the resulting model file. The junction points created in step 5-6 are still missing QUIDs. 

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:
"&" = "and" 
"|" = "or" 

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:

1.	Copy a message  (To copy a right-clicked message to Copy Buffer) 
2.	Insert Before (Insert a copied message(s) before a message) 
3.	Insert After (Insert a copied message(s) after 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:

1.	Rebuild the DCS library with RTD_STATISTICS=0.  This causes the two SPPs cnxMetrics and vuMetrics not to be registered. 
2.	Modify your model so that the Top Capsule contains the RTDBase and another capsule representing the rest of the model.  Make the application capsule optional and make sure it is destroyed before the context abort is called which destroys the RTDBase capsule. 	
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.	
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.	

Additional Information
Contacting IBM Rational Customer Support
Contacting Rational Customer 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 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 www.ibm.com/software/support.