IBM® Rational® Rose® RealTime Windows V2003.06.15 iFix 1 Release Notes

Release Date: April 2006
Last Updated: April 10, 2006 

© Copyright IBM Corporation. 1999, 2006.  All Rights Reserved.
Any reproduction or distribution of this work is expressly prohibited without the prior written consent of IBM Corporation. 
Legal Notices Information

Scope
This iFix is for configurations only, and it addresses defects (see Defects_Fixed_in_This_Release).
The iFix Release Note includes:
•	Upgrade information and instructions 
•	Defects fixed in the current iFix release v2003.06.15b
Getting Started
Installation Information
What to do Before Installation
Verify Rational Rose RealTime v2003.06.15 is installed and ensure that file and directory permissions allow writing to Release Area.  If you encounter problems during the unzip process regarding read-only files, change the permissions on the file system for all files under <ROSERT_HOME>C/TargetRTS and <ROSERT_HOME>C++/TargetRTS.

Note: Some Windows virus checking software will warn you about gzip type files (with a .gz extension). This warning can be safely ignored. There should be no viruses reported during the extraction of the iFix files when using WinZip.
Hot Fixes Not Included in Rose RealTime V2003. 06.15 iFix 1
The Fixes (shown for the Hot Fixes/Test Fixes) listed in the table below are not included in this iFix.  These fixes were finalized after the code was complete for iFix 1.  The following fixes will be included in the next Rose RealTime Fix Pack or Service Release.
Rose RealTime V2003.06.15 Hot Fixes / Test Fixes	
Test Fix 11	Rose RealTime Model Integrator	RATLC00542123 / IC48675	Version stamps in petal files cause Rose RealTime Model Integrator to generate a non trivial merge.	
Test Fix 12	Rose RealTime Toolset	RATLC00963322 / IC48989	Rose RealTime may crash upon opening a custom framework model and then loading another model.	
How to Install this iFix
To install the Rational Rose RealTime v2003.06.15b iFix:
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_2003r5_iFix_03.30.2006.bat” file before proceeding with the next steps:
@set HF_INSTALLDIR="C:\Progra~1\Rational\Rose RealTime"
1.	Ensure there is no running instance of Rational Rose RealTime on the computer you want to update.
2.	Verify Rose RealTime V2003.06.15 is installed. 
3.	Copy the iFix Rose_RealTime_2003r5_iFix_03.30.2006.exe into a temporary directory
4.	Copy the Install batch file install_Rose_RealTime_2003r5_iFix_03.30.2006.bat into the same temporary directory.
5.	Run install_Rose_RealTime_2003r5_iFix_03.30.2006.bat  (This will extract and register the necessary files.)
What to do After Installation
The accompanying .exe file from the iFix is no longer required.
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.6.2052. If the build number is not the same, this Service Release 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
Note: If you wish to take advantage of the problems fixed in the RQA-RT, you need to rebuild and re-verify your test runs.
RTJava Models
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.
Model Integrator 
No additional steps are required.
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 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 & 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. 
Targets Requiring Re-Build after Installing this iFix
To determine which TargetRTS or Connexis libraries require immediate rebuilding, please refer to the following directories of your release after installing this iFix.  
o	$ROSERT_HOME/C++/TargetRTS/lib/<config>
o	$ROSERT_HOME/C/TargetRTS/lib/<config>
o	$ROSERT_HOME/Connexis/C++/lib/<config>
If the TargetRTS or Connexis libraries you require have timestamps older than July 30th 2005, it will be necessary for you to rebuild the applicable libraries before utilizing.
Licensing
For additional information on licensing, see You Must Install License Keys to Run this Product.
Compatibility Issues
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/
Late Changes to Documentation
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. 
Enhancements & Defect Fixes
•	Rose RealTime v2003.06.15 Enhancements
•	Rose RealTime v2003.06.15b Enhancements
Rose RealTime v2003.06.15b Enhancements
•	Rose RealTime C++ 
o	Ability to generate code for operation parameter documentation, signals documentation in protocol, enum, and attribute documentation fields 
o	Ability to include dependent component paths
•	Rose RealTime ClearCase Integration 
o	Options to check-out (check-in) all controlled units recursively 
o	New Maintain last controlled unit state option available
•	Rose RealTime Toolset 
o	Force save all units 
o	Ability to set user defined sort order in browser 
o	Automatic refresh before editing a source controlled element 
o	Ability to show Choicepoint code 
o	Note view link check & correct updates when diagrams moved 
o	Display sequence diagram name when using Find 
o	Addition of RRTEI function to obtain all selected classes in browser

Rose RealTime C++ Enhancements
Ability to generate code for operation parameter documentation, signals documentation in protocol, enum, and attribute documentation fields
The generated documentation appears as shown below:
enum AnEnumeration 
{ 
// {{{RME classEnum 'red' 
// {{{RME general 'documentation' 
/* {{{USR 
....................... 
}}}USR */ 
// }}}RME 
// }}}RME
Generates documentation for protocol fields 
----------------------------------------------------- 
// {{{RME inSignal 'ack1' 
// {{{RME general 'documentation' 
/* {{{USR 
............................. 
}}}USR */ 
// }}}RME 
inline RTInSignal ack1( void ); 
// }}}RME
Ability to include dependent component paths
This enhancement assures that the inclusion path of the component, which the component being built is dependent upon, is included to facilitate a successful compilation. A new code generation flag (-finclude-dependentpath) is now available, as described below.
•	In order to utilize this feature, set -finclude-dependentpath in the ROSERT_RTGENOPTS pathmap variable. 
•	To unset the flag, -finclude-dependentpath, either set ROSERT_RTGENOPTS to -ignore-flag or restart Rose RealTime (to remove the pathmap variable from memory).
Rose RealTime ClearCase Integration Enhancements
Options to check-out (check-in) controlled units under currently selected controlled unit recursively
You now have the ability to check-out or check-in all appropriate controlled units recursively under the currently selected controlled unit.
Steps below describe how to utilize this feature:
1.	Right click on the controlled unit you wish to check-out and select Source Control > Check Out (recursively all Child Units). Alternatively, you will also see the option Source Control > Check In (recursively all Child Units) to check-in all controlled units. 
2.	A dialog box will appear, listing all applicable checked-in or checked-out units. You have the ability to de-select any units you do not wish to check-out or check-in.
Note:
Doc-link documents attached to any model element will not be checked-out or checked-in utilizing this functionality. It is not necessary to check-out these documents when performing petal version update.
New Maintain last controlled unit state option available
Originally, when trying to control a unit, a message would be displayed asking you to confirm the request. Also, you had the option to control all the subunits. If the unit being "controlled" belonged to a unit  which was NOT controlled, a warning was displayed.
Now, you have the flexibility to control the unit, which may not belong to a controlled unit (no warning messages are displayed). Also the state is preserved for the last control/uncontrol operation and is carried across units.
A new check-box Maintain last controlled unit state is available in the File tab of the Tools > Options dialog.
When checked you may control a unit which does not belong to a controlled unit (no warning is displayed). Also, the state of this option is preserved throughout the existing and new Rose RealTime sessions, when controlling / un-controlling units. The setting is maintained in the RoseRT.ini file.
Rose RealTime Toolset Enhancements
Force save all units
You may now automatically save all write-able units in an existing Rose RealTime model to the new Rose RealTime V7.0 petal version, as described below.
1.	A new option Force save all units is available in the File tab of the Tools > Options dialog (default value is un-checked = False). 
2.	Select the Force save all units option. 
3.	Check-out all the units which need to be saved (updated). 
Note:
Refer to a new feature Options to check-out (check-in) all controlled units recursively for instructions.
4.	Save the Model.
All write-able units will now be updated with the new petal file format and version.
Note:
Once models are upgraded to new petal version it is strongly recommended that you disable the Force save all units option. Otherwise, you may notice a performance delay in subsequent model Save operations due to unnecessary petal updates.
Ability to set user defined sort order in browser
You now have the opportunity to display elements (within the same hierarchy) in user defined sort order. This new feature is described below.
Note:
The User Defined Order option may only be used for elements in the Model view tab of the Rose RealTime browser. You will not be able to utilize this feature in other view tabs (i.e. Containment view tab, Inheritance view tab, etc.).
•	A new context menu item User Defined Order is available in the Sort menu option. 
•	The model file maintains sort order and sort option between sessions (if desired), for example: 
o	The changes made to the display order by selecting the additional new option Edit Display Order are saved to the model's petal file by checking Save user defined sort order under the Tools > Options > File tab. If this option is not selected, then all changes made to the display order which were not saved will be lost. 
o	If a model includes user defined sort order information and Save user defined sort order is checked, the elements will be displayed in that order. 
o	If a model does not include user defined sort order information, the elements will be displayed in Internal Order.
•	Changes made in User Defined Order are preserved when switching between different sort orders. 
o	For example, if Edit Display Order is used to make changes to the User Defined Order, and then Internal Order is selected - if User Defined Order is later again selected, the original changes made using Edit Display Order are still available.
•	Using User Defined Order to make changes in browser. 
o	From browser context menu, select User Defined Order from the Sort menu option. 
o	Also from browser context menu, select the Edit Display Order menu option. 
o	Edit in the browser using drag and drop. 
o	Once editing completed, activate browser context menu and again choose (un-check) Edit Display Order, to exit the edit mode.
•	Drag and drop functionality when User Defined Order and Edit Display Order are enabled. 
o	Dragging element A over element B, A is placed after B (if both elements have the same immediate parent).
Automatic refresh before editing a source controlled element
While the model is refreshing (in the background), you may automatically refresh a specific element you wish to update by double-clicking on the element in the browser. Once the element is refreshed, the standard action which occurs when double-clicking is applied (i.e. displaying the specification dialog, opening diagram, etc.).
Note:
The automatic refresh will only occur the first time the user double-clicks on the element, while the model is refreshing in the background.
Ability to show Choicepoint code
A new context menu option called Show Choicepoint Code has been added to the context menu of the state diagram editor. Using the Show Choicepoint Code option it is possible to display code for choicepoints on the diagram, similar to transitions.
Note view link check & correct updates when diagrams moved
See RATLC00519038 - Note view links to diagrams that are moved are now updated. A check is also added when opening a model. If there is an invalid note view link to class diagram "Logical View/NewDiagram" in the class diagram "Logical View/Main", while loading the model the following warning message appears in the toolset Log window:
Warning: Invalid noteview link "Class Diagram: Logical View / NewDiagram" in diagram "Class Diagram: Logical View / Main."
You may also see the following types of warning messages:
Warning: Invalid noteview link "Class Diagram: Logical View / NewDiagrams" in diagram "Class Diagram: Logical View / Main"
Warning: Invalid noteview link "Component Diagram: Component View / NewDiagram" in diagram "Component Diagram: Component View / Main"
Display sequence diagram name when using Find
When using Find function in a collaboration diagram to search for attributes in the code - the interaction diagram name was displayed instead of the sequence diagram name.
A new function is available to construct the qualified name so that the corresponding sequence diagram name is now displayed in the result.
Addition of RRTEI function to obtain all selected classes in browser
Description: Returns all ClassDiagram selected in the current model. 

Syntax: 

Set theClassDiagramCollection = theModel.GetSelectedClassDiagram() 
theClassDiagramCollection 
As RoseRT.ClassDiagramCollection - Returns the collection of ClassDiagram currently selected in the model.theModel 
As RoseRT.Model - Instance of the model from which protocols are being retrieved. 

Sample Code: 
Sub Main Viewport.Open Viewport.Clear. 
    Print "Selected ClassDiagram Count",RoseRTApp.CurrentModel.GetSelectedClassDiagram.count 
     If (RoseRTApp.CurrentModel.GetSelectedClassDiagram.count>=1) Then 
           msgBox("Element Selected") 
    Else 
        msgBox("Nothing Selected") 
    End If 
End Sub
Rose RealTime v2003.06.15 Enhancements
Core Rose RealTime Enhancements
•	Enhancement for Slow Performance when Displaying Sequence Diagram Role List
•	New RRTEI Methods
•	RRTEI:  Enhancement to Provide Access to Note Content
•	RRTEI:  Enhancement to Retrieve Message Number from Message
•	Ability to Build CORBA Component through RRTEI
•	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
•	Enhancement to Add “Find References” to Code Editor Selections
•	Enhancement for using Find In dialog to Search Inherited Fields within Composite Items
Rose RealTime Model Integrator Enhancement
•	Rose RealTime Model Integrator Filter Enhancement
Rose RealTime CPP Enhancement
•	Provide Better Support for C++ Nested Namespaces
•	Ability to Define Cardinality in External Header File

Rose RealTime / ClearCase Integration Support
•	Ability to Check-In / Check-Out External Files
Rose RealTime Java Enhancement
•	Rose RealTime Java Improvement to Method Visibility in Sequence Diagrams
Addition of CORBA 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).
o	RelocateClassEx (original:  RelocateClass) 
o	RelocateClassDiagramEx (original:  RelocateClassDiagram) 
o	RelocateLogicalPackageEx (original:  RelocateLogicalPackage) 

Also, new RRTEI methods to provide access to Note Content and to retrieve message number from message.
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) is 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.
Rose RealTime Model Integrator Filter Enhancement
Selecting Rose RealTime 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):
o	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) 
o	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) 
o	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) 
o	Colors (color, fill color, default color, line color) 
o	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 RealTime 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 (i.e. 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 
o	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()).
o	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.15 Patch.

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.	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.
2.	The Help documentation for the CORBA Add-In may indicate Rose instead of Rose RealTime.
Enhancement 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
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.
Code Editor Windows & Dialogs Added or Enhanced
o	Code Window

                                         Original Code Window								New Code Window
o	Open Specification Code Window

                           Original Open Specification Code Window					       New Open Specification Code Window
                             Original Specification Window							New Specification Window
Find / Replace Dialogs now include Regular Expression Searches and the Ability to “Mark All” or Replace In “Whole file”

Original Find / Replace Dialogs								   New Find / Replace Dialogs

Selection button will be enabled only when there is a selection.  To remove markings created by “Mark All” select context menu > Search > Clear Markings.

o	New Options (Font, Color…, Line Numbers) added to the Documentation/Code (Ctrl+3) window pane (right bottom).

 

o	Capsule Operation, Detail tab, Code window context menu.

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 

o	Print Code Dialog now includes “Options Tab”, which is shown below (Can be accessed through Context menu > File > Print…)

Paper Type Selection & Orientation may be accessed through the “Properties…” button.

o	New Print Code > Options Dialog providing user defined settings for Header, Footer and Line Number

o	New Code Print Preview Window Available 

o	Ability to use "Find References" which utilizes selected code as a search parameter.

New Context Menus:  Search > Find in Model... and Search > Replace in Model...
Both new menu selections invoke the TreeBrowser Find Dialog.

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.
Enhancement to Add “Find References” to Code Editor Selections

A selection made in the Code Editor can now be used as a search parameter for the Find tool.

Two new context menu items are have been added to the Find Context Menu:

•	Find in Model… (Ctrl Shift+F)
•	Replace in Model… (Ctrl+Shift+R)

Select text in the Code Editor and Select Search > Find in Model or Replace in Model.  Alternatively, you may select the Ctrl+Shift+F or Ctrl+Shift+R, after selecting the text in the Code Editor.

Defects Fixed & Enhancements
•	Defects Fixed in Rose RealTime v2003.06.15
•	Defects Fixed in Rose RealTime v2003.06.15b
Defects Fixed in Rose RealTime v2003.06.15b
RATLC / APAR ID	Component	Description	
IC43412 / RATLC00530604	Rose RealTime C++	Rose RealTime C++ code generator does not generate correct BackwardsCompatibility for RTDataObjects. 

Now the proper code will be generated for the protocols when the backwards compatibility option is enabled.	
IC46706, PK14613; RATLC01089732, 

RATLC00539535	Rose RealTime C++	The following compilation errors may occur when building the TargetRTS: 
undefined symbol: ___divdi3 
undefined symbol: ___moddi3

due to 'long long' and _int64. 
This is due to the fact that some compilers do not support "long long". The capacity of the fields, tv_sec and tv_nsec within the RTTimespec structure of Rose RealTime were changed to 'long long' in Rose RealTime V2003.06.15. The fields were converted to unsigned long as some compilers in the embedded space do not support long long resulting in compilation errors on some platforms. 

You will need to recompile both Rose RealTimeTargetRTS and the DCS.rtmdl in the same order and recompile all the models built using Rose RealTime and/or DCS library to enable this fix.	
RATLC00144783	Rose RealTime C++	Solaris:  Slow performance generating C++ code from Solaris Rose RealTime v2003.06.15.	
RATLC00211839	Rose RealTime C++	Enhancement: Ability to include dependent component paths	
RATLC00533446	Rose RealTime C++	Enhancement: Ability to generate code for operation parameter documentation, signals documentation in protocol, enum, and attribute documentation fields	
IC46894; RATLC01095072	Rose RealTime ClearCase Integration	Unable to change Rational ClearCase activity selection within Rational Rose RealTime. 
The view path was not calculated properly prior to calling the Rational ClearCasechange activity operation.
Now, the activity will be changed to the newly selected activity.	
IC47180, RATLC01097262	Rose RealTime ClearCase Integration	When utilizing the Rational Rose RealTime / ClearCase integration and attempting to view the version tree from within Rational Rose RealTime, the following error message occurs:

Undefined error in opening the element. Please check if pathname is a versioned object.	
IC47263; RATLC01097786, RATLC00144165	Rose RealTime ClearCase Integration	Solaris:  When attempting to synchronize the model (under ClearCase control), Rose RealTime may crash.

The following may appear in the automatically generated stack trace. 

__1cTCOImportStagingAreabACheckForUniqueId 
Collisions6MpnGDesign_pnEItem_rnIErrorLog 
_rnFCOSet__i_(0x0, 0xc7af00, 0x0, 0xffbed124, 
0xffbed030, 0xffbed010) + 0xbc	
IC47333; RATLC01101803	Rose RealTime ClearCase Integration	Upon check-in or check-out of Rational Rose RealTime model in Rational ClearCase, a dialog appears for each element and Rational ClearCase becomes the active window.	
RATLC00210762	Rose RealTime ClearCase Integration	Enhancement: New Maintain last controlled unit state option available	
RATLC00516650	Rose RealTime ClearCase Integration	Enhancement: Ability to check-out / check-in external objects through Rose RealTime.	
RATLC00521140, RATLC00962965	Rose RealTime ClearCase Integration	Enhancement: Options to check-out (check-in) all controlled units recursively	
IC42118; RATLC00526499	Rose RealTime Connexis	Connexis CRM connection may not be reestablished correctly.	
RATLC00962122	Rose RealTime Connexis	Connexis Viewer may crash upon refresh. 
During a refresh, the Connexis Viewer resets (disconnects and then connects) all the connections with the ports associated with the saps and spps. However, if the connection with the sap and spp port has not completed once the reset is complete, the system used to access an invalid port results in a crash.	
IC47164; RATLC01097019	Rose RealTime CORBA	CORBA generated code with class type as CORBASTRUCT cannot be reverse engineered. 

Forward declarations generated within a module for the CORBA elements, were not correct. Now, the Forward declarations are generated within a module only for the CORBA elements such as interfaces and valuetypes.	
RATLC00472839	Rose RealTime CORBA	Rose RealTime may crash when reverse engineering CORBA IDL file when only specifying the root directory of the IDL files.	
RATLC00960539	Rose RealTime CORBA	Moving or Renaming referenced CORBA type would not update the references with location or name change.
 
The class name changes in the Logical view were not updating the attributes, operations and/or parameters whose types were set to that class.

Now, the attributes, operations and/or parameter types are updated with the changed class name. Updating also occurs when the class is moved across the packages. 

Note:
Limitation: The class name is assumed to be unique. For example, there are no two or more classes with the same name. If there are two or more classes with the same name, that class name change will not be propogated. 

Currently, the deletion of the class will not update the attributes, operations and/or parameter types.	
RATLC00961869	Rose RealTime CORBA	CORBA project specification dialog does not open.	
RATLC00962059	Rose RealTime CORBA	CORBA Add-In missing latest initialization file (corba.ini). 
Upon browsing code using the built-in editor, CORBA keywords not highlighted correctly.	
RATLC00518525	Rose RealTime Eclipse Integration	Unable to build in Eclipse if CompiliationMakeType has been modified in Rose RealTime since project creation	
RATLC00518527	Rose RealTime Eclipse Integration	Edit transition code in Eclipse incorrectly displays parent transition code for child transition.	
RATLC00518531	Rose RealTime Eclipse Integration	Cursor is not positioned correctly in Eclipse from Rose RealTime build error for capsules & classes in C.	
RATLC00518984	Rose RealTime Eclipse Integration	Edit Code in Eclipse from Rose RealTime for CommonPreface syntax error should position cursor between USR tags in Eclipse.	
RATLC00518996	Rose RealTime Eclipse Integration	Cursor is not positioned correctly when attempting to edit C code in Eclipse.	
RATLC00519036	Rose RealTime Eclipse Integration	Cursor is not positioned after the //{{{ USR tag for the transition code if transition docs have also been generated.	
RATLC00519068	Rose RealTime Eclipse Integration 	Edit Operation Code for original operation incorrectly positions cursor in OverLoaded operation - CC Class only.	
RATLC00519069	Rose RealTime Eclipse Integration	Need additional classifier argument for OnEditCodeInEclipse event.	
RATLC00519081	Rose RealTime Eclipse Integration	Rose RealTime build error parser reports wrong line number if method includes generated documentation. 
1.	Compile transition code with syntax error in Rose RealTime. 
2.	In the Build Errors list, right-click on the error and choose Edit Code in Eclipse. 
3.	In Eclipse, the file will open, but the cursor will go to the wrong location if there is documentation code generated for that transition.	
RATLC00519168	Rose RealTime Eclipse Integration	Error message should be displayed indicating unable to navigate from Eclipse build errors, if code has been generated without model tags.	
IC46547; RATLC00142926	Rose RealTime Model Integrator	Rose RealTime Model Integrator may not merge models correctly if they include passive class triggers.
Utilization of passive class trigger may cause all capsules to lose their triggers when using the Model Integrator.	
IC47078; RATLC00143285	Rose RealTime Model Integrator	Rose RealTime Model Integrator may crash when merging specific models.	
PK09126; RATLC01094676	Rose RealTime Model Integrator	A corrupted Rose RealTime model may be created when performing a merge utilizing the Rose RealTime / ClearCase integration.

This problem could occur while merging, if there are "multiple conflict points" and you choose one of the "contributors", even if the string contains a blank line. In this case, the closing "eol" (end-of-line) is ignored, resulting in an inconsistent final model containing no newline.	
RATLC00514816	Rose RealTime Model Integrator	Rose RealTime Model Integrator may create model with invalid petal format when performing a merge.

The problem was caused by the fact the model contained a sequence diagram inside a Protocol. sequence diagrams in a Protocol are slightly different than sequence diagrams that are in any other location. Under a Protocol, the Interactions are called ProtocolInteractions. In all other cases they are called RTInteractions. The Model Integrator was unable to correctly handle ProtocolInteractions. This resulted in Model Integrator creating an invalid petal file.	
RATLC00962169	Rose RealTime Model Integrator	Final model may not include newline character when merging different versions of Rose RealTime models while using Rose RealTime / ClearCase integration.	
IC38418; RATLC00517047	Rose RealTime Toolset	Illegal instantiates relation error message may occur when attempting to create a dependency between an instantiated class and a regular class. 
Workaround: Include #include regular_class.h in the HeaderPreface in the C++ tab of the instantiated classes specification. It will not show the dependency, visually.
Now, a check is done to determine whether the dependency is allowed between both classes and will allow creation of the dependency, if appropriate.	
IC39208; RATLC00519038	Rose RealTime Toolset	A note view link is not valid after moving a diagram across packages. 
This problem would occur when a diagram the note view link is pointing to is moved across packages. When this occurred the note view link reference to the diagram was deleted. Now, the note view link is correctly updated. A check is also added when opening a model. If a model contains invalid note view links, a warning will be reported.	
IC42096; RATLC00526420	Rose RealTime Toolset	Derived capsule does not display inherited composite relationships in RTS Browser Navigator.	
IC42609; RATLC00527799	Rose RealTime Toolset	Rose RealTime may not be able to compile applications with circular dependencies. 
#include of RTStructures.h does not get generated for non-leaf components.
Workaround: Add inclusion of RTStructures.h manually.	
IC43651; RATLC140920	Rose RealTime Toolset	Slow performance when opening the Rose RealTime aggregation tool class list.

Using the Aggregation Tool to generate an aggregation between two classes, the generation of the class pick list for end b is very slow and it depends on the number of classes in the model.	
IC44190; RATLC00141225	Rose RealTime Toolset	Rose RealTime may crash when sequence diagrams includes duplicate references to sender/receiver end of message. 

This was corrected by not allowing more than a single reference to the message end to be created.

An error message will be logged if a message is corrupted, i.e.: 
•	No reference to sender end 
•	No reference to receiver end 
•	Multiple references to sender end 
•	Multiple references to receiver end	
IC46204; RATLC00142629	Rose RealTime Toolset	Diagram may appear much larger than expected.

This may cause information on the diagram to appear in the top left corner when printed or extracted with IBM Rational SoDA. 
This was indirectly caused by the fix for IC44325/RATLC00141283 (Connector label may cause structure diagram to inappropriately resize(grow larger)). There were hidden labels associated with the Association lines. The value of these labels could grow, increasing white-space.
If your diagram has already been impacted by this defect, contact Rational Technical Support for script to help correct your model.	
IC46706; RATLC01089732	Rose RealTime Toolset	Error could occur when loading model to target: 
ld < TEMPTEST 
undefined symbol: ___divdi3 
undefined symbol: ___moddi3 
ld error: error reading file (errno = 0x1c0001). 
value = 0 = 0x0 
Updated TargetRTS tv_sec and tv_nsec data types to long from long long..	
IC46768; RATLC01090028	Rose RealTime Toolset	Rose RealTime may crash when user selects Edit > Replace as described below. 
1.	Open a Model 
2.	Clic on Edit > Replace
In this case, Rose RealTime may crash with the error An unsupported operation was attempted.	
IC46925; RATLC01095321	Rose RealTime Toolset	Solaris:  Entering text in Rose RealTime Code Editor may inadvertently insert “^M” characters, seen when displaying to external editor.	
IC47208; RATLC01097116, RATLC00962026	Rose RealTime Toolset	When a model includes elements that are referenced via a PATHMAP, the model build will fail with an I/O Error. 
This error was due to a DLL version change in Rose RealTime from 6.5. To 6.6 and registry entries of only 6.5 in Software\Rational Software\Rose RealTime\<<VERSION>>\...	
IC47263; RATLC01097786, RATLC00144165	Rose RealTime Toolset	Solaris:  When attempting to synchronize the model (under ClearCase control), Rose RealTime may crash.
 
The following may appear in the automatically generated stack trace. 

__1cTCOImportStagingAreabACheckForUniqueId 
Collisions6MpnGDesign_pnEItem_rnIErrorLog 
_rnFCOSet__i_(0x0, 0xc7af00, 0x0, 0xffbed124, 
0xffbed030, 0xffbed010) + 0xbc	
IC47322; RATLC00962093	Rose RealTime Toolset	Solaris:  Unable to use standard copy & paste scenarios (i.e. middle mouse button and Ctrl+C + Ctrl+V).	
IC48354: RATLC00479853	Rose RealTime Toolset	Cursor should be positioned at the beginning of the code when the code editor is invoked.	
PK04686; RATLC00142322	Rose RealTime Toolset	Cursor in specification dialog code editor changes position to the end of the code when making a change and pressing the Apply button.	
PK10704; RATLC00143335	Rose RealTime Toolset	The Revert To Default option in the specification dialog may not retain value.
 
Once the Revert To Default option is applied and the dialog window is closed, the change may not be saved.	
PK11370; RATLC00143422, RATLC00534553	Rose RealTime Toolset	Rose RealTime includes incorrect default exception E-Mail address.

Displaying default exception E-mail address as RoseRT_exception@rational.com instead of rosert@ca.ibm.com.	
PK11504; RATLC00962072, 
RATLC00962049	Rose RealTime Toolset	Rose RealTime may redraw the elements on the diagram each time the cursor is moved.

This issue will only occur in class diagrams which include > 100 inherited signals.	
PK11589; RATLC00143473	Rose RealTime Toolset	RRTEI function OpenSpecification opens the wrong specification dialog for the types: 
•	Action 
•	EntryAction 
•	ExitAction	
PK11936; RATLC00143512	Rose RealTime Toolset	RRTEI inserts message incorrectly. Not possible to identify whether to insert synchronous vs asynchronous message. 
To create an 'asynchronous' message you may now use the RRTEI call to theInteraction.AddMessageWithAction with the parameter rsSendAsynchronousAction.
The line theMessage2.Action.Mode = rsASynchronousMode does not have any effect through RRTEI.	
PK12703; RATLC00143592	Rose RealTime Toolset	Vertical scroll bar incorrectly positioned at the top of text in code editor when accessing error/search results. 
When the code editor is opened, the appropriate text is selected (but, vertical scroll bar still shows at the top of the window no matter where the selected text is located). Now, the scroll bar will appear in the appropriate location relative to the selected text.	
PK13407; RATLC00143654	Rose RealTime Toolset	Using & and | (regular expression search) may not produce expected results and depends upon order in which words are used in the search. 

For Example: Right click on the Top most model element "Model" and select Find In... from the context menu and perform the following search on the model. Search string Returned transitions computer & system Initial, t2 (WRONG), system & computer t2 (CORRECT), or 

Open the code editor for a transition 
Right click to open the context menu 
Select Search --> Find 
Check the Regular expression check box (in the Find dialog) and type "system & computer" 
Click button Mark All
An error message appears indicating nothing is found. 

Now, with the fix for this issue 

•	If the Search String contains any regular expression, Rose RealTime will ignore the space(s) around the logical operator(s). 
•	Search String using & will report on the intersection of two sets of strings. 
•	Search String using | will calculate the union of two sets of strings. 
•	When a Search String contains both operators | and &, Rose RealTime will calculate the union and perform intersection operations as it encounters the operator while scanning the pattern searched for, starting from the left-most character.

Refer to the list below, which includes Search String examples and expected results. 

•	xyz & abc - Searches for occurrences of both strings xyz and abc. 
•	x y z & abc - Searches for occurrences of both string x y z and abc. 
•	xyz | abc - Searches for occurrences of xyz, abc and if any of the strings are present, include the string in the results. 
•	xyz | abc & def - Calculates the intersection of the results of searching xyz, ab". Using the previous result set, again calculates the union with the results found while searching for "def". 
•	xyz & abc & def - Calculates intersection of the results while searching for xyz, abc. Using the previous result set, again calculates the intersection with the results found while searching for "def".	
PK14369;  RATLC00143829	Rose RealTime Toolset	The code window and scroll bar immediately move to the beginning of the transition code, upon changing transition code at the end of the code and pressing the Apply button.

In this case the focus (location) should remain the same.	
PK15015; RATLC00539958	Rose RealTime Toolset	Invalid TAG_CPU arm: Target is Unknown error may occur when loading a VxWorks binary from Rose RealTime. 
Required ARM processor entries added:
•	#define ARM7TDMI_T 125 
•	#define ARMARCH3 126 
•	#define ARMARCH4 127 
•	#define ARMARCH4_T 128 
•	#define STRONGARM 129 
•	#define XSCALE 1120 
•	#define ARMARCH5 1121 
•	#define ARMARCH5_T 1122	
PK15577;  RATLC01103859	Rose RealTime Toolset 	Transition may lose Documentation and Name when utilizing “Toggle SelfTransition to Internal/External”.

When an external self-transition is transformed into an internal self-transition by using the function “Toggle SelfTransition to Internal/External”, the transition loses its documentation and name.	
PK15802; RATLC00143950	Rose RealTime Toolset	Solaris:  Rose RealTime may crash when performing a print preview and selecting OK/Cancel in the specification dialog if using CDE display on Solaris.

This will result in stack trace beginning with:

__1cRCOAdvTextEditCtrlOGetDisplayName6M_rknHCString__(0x0, 0xfce34ed4	
PK15803;  RATLC00143954	Rose RealTime Toolset	Inconsistent display of "Blue Delta" when opening model.

When opening a model file saved in version prior to v2003.06.15 from the command line, no blue delta appears for the top model element “Model”.  However, when opening the same model from within Rose RealTime (File > Open) the blue delta appears.	
PK16568: RATLC00144013	Rose RealTime Toolset	Search Find in option incorrectly ignores trailing space in search string.

In a search string that does not include any logical operators (i.e. &, |), white spaces will not be removed. This is the same algorithm present in previous versions of Rose RealTime.
 
For Example: 
Search String: xyz abc 
Rose RealTime will provide results for search string: xyz abc 

Search String: abc 
Rose RealTime will provide results for search string: abc	
PK16570; RATLC00144015	Rose RealTime Toolset	Scroll bar not working when attempting to insert a data class.

To reproduce: 
1.	Open a specification window for a capsule, a class or protocol. 
2.	Select the Resolution tab. 
3.	Right click to insert a new relation.
In the dialog that opens there is a scroll bar, but it does not respond. 
Workaround: Use the arrow keys (or Pg Dn / Pg Up) to traverse up and down the list.	
PK17247; RATLC00479487	Rose RealTime Toolset	Loss of overridden transition code, triggers/ports and failure to propagate the logical name and external doc list when performing internal to external toggle. 
The following toggling actions are not available due to undesirable side-effects or limitation in of the Rose RealTime Framework:
•	Toggling of a self transition from a derived capsule's state machine has been disabled. 
•	Deleting a "toggled" transition in a derived capsule and then attempting to do a toggle again.	
PK19219; RATLC00481706	Rose RealTime Toolset	Scroll bar appears to move in Create a Protocol/Port dialog, but is not functional.	
RATLC0045705	Rose RealTime Toolset	Enhancement: After selecting multiple diagrams you may utilize the Find In function for all diagrams selected.	
RATLC00046354	Rose RealTime Toolset	Enhancement: Ability to set user defined sort order in browser	
RATLC00141891, RATLC00520461	Rose RealTime Toolset	Enhancement: Note view link check & correct updates when diagrams moved	
RATLC00213368	Rose RealTime Toolset	Enhancement: Display sequence diagram name when using Find	
RATLC00248787	Rose RealTime Toolset	Actor class role name may not display correctly in sequence diagram. 
In this case, the instance name width may appear small.
Resolved by limiting labels to parent size if parent is in ICON view.	
RATLC00372093	Rose RealTime Toolset	Enhancement: Addition of RRTEI function to obtain all selected classes in browser	
RATLC00516576	Rose RealTime Toolset	Enhancement: Ability to show Choicepoint code	
RATLC00520460	Rose RealTime Toolset	Enhancement: Automatic refresh before editing a source controlled element	
RATLC00521139	Rose RealTime Toolset	Enhancement: Force save all units	
RATLC00961789	Rose RealTime Toolset	DCS.rtmdl model will not compile correctly, displaying the following type of errors: 

!> Generating RTDStats 
Error: The default CopyFunctionBody requires a public copy constructor. 
!> Generating RTDTransportStats 
Error: The default CopyFunctionBody requires a public copy constructor. 
NMAKE : fatal error U1077: 'rtcppgen' : return code '0x3' 
Stop. 
NMAKE : fatal error U1077: 'rtperl' : return code '0x2' 
Stop. 
Error: Build failed status 0x2 
Build failed. 

For this model only ("DCS.rtmdl") the Rose RealTime Toolset was found to inadvertently change some of the arguments while reading in the model file. Updates have been made to both "DCS.rtmdl" and the Rose RealTime Toolset, to correct this issue.	
RATLC00961816	Rose RealTime Toolset	Perl version updated to v5.8.3.	
RATLC00962874	Rose RealTime Toolset	Pressing the Apply button causes the Documentation window to jump to the beginning.

When Documentation text is changed at the end of the text and then the Apply-button is pressed, the Documentation window and scrollbar jump to the beginning of the Documentation window. This is because the position of the scroll bar was not correctly maintained.

Now, the scroll bars position will be set to the appropriate position when the Apply button of the Documentation window is pressed.	

Defects Fixed in Rose RealTime v2003.06.15
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).	
RATLC00140872 / IC43498	Rose RealTime Model Integrator may crash while merging changes in the same Rose RealTime class file.	
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.	
RATLC00141602 / PK01193	Unable to launch Rose RealTime when Tornado installed or running.	
RATLC00141729 / PK01846	Information in the data field may incorrectly be deleted.	
RATLC00141744 / PK01890	Unable to drag classes, operations, attributes, ports, capsule roles, states, etc. into the Code Window.	
RATLC00141757 / PK01951	C++:  The visibility for data members created with an association may be generated as private even if it is declared as public or protected.	
RATLC00141936 / IC45284	Copying and pasting an inherited state in a Capsule's state diagram may cause the following exception: 

RoseRT.exe caused a EXCEPTION_ACCESS_VIOLATION in module RoseRT.exe at 001B:004F064E	
RATLC00142008 / PK02802	Copying and Pasting between Rose RealTime instances and from xterms may not work correctly.	
RATLC00142188 / PK03813	Incorrect line highlighted when reporting compile error.  Highlights the line after the one on which the error was reported.	
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).	
RATLC00142245 / IC45775	Model Integrator truncates the state names in transition source points.	
RATLC00142319 / PK04683	Rose RealTime could crash when using "Find in..." function.	
RATLC00142468 / IC45964	The following crash could occur in Rose RealTime for Solaris:

Rose RealTime unix exception: :__1cICRoseAppVBringDownSplashScreen6M_v_	
RATLC00246172 / IC41967	RRTEI Collection Classes will not work with out-of-proc calls.	
RATLC00248919 / IC40612	Unable to open a model through a Workspace when using a snapshot view.  The following error message may appear: 
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..	
RATLC00249200 / IC42295	Copying a structure diagram to Microsoft Word will cause corruption to the image.	
RATLC00249224	Double-clicking on a Rose RealTime CORBA element could cause Rose RealTime to hang.	
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 Patch:
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.	
RATLC00512873	Enhancement to provide better support for C++ Nested Namespaces. 
Two scenarios described below:

CASE 1:
------------
Using the flag "RTGEN = rtcppgen -fusenamespaces" you may generate namespaces for all packages. For example - if the package tree is similar to the following:

Logical View
|
--------------------- Package1-Level1
| 
|                     | ----------------------- Package1-Level2
| 
|                     | ----------------------- Package2-Level2
|
|--------------------- Package2-Level1

For all capsules which occur under the package "Logical View" namespace "Logical_View" would be generated in the source code.

All capsules which are added under "Package2-Level2" will have the nested namespace as shown below.

namespace Logical_View
{
    namespace Package1-Level1
     {
        namespace Package2-Level2
          {
             ..............
          }
     }
}

CASE 2:
------------
The case mentioned above doesn't provide the flexibility to control namespace generation at the package level.  If you require control at the package level, open the specification dialog of the package and enter the stereotype as "Namespace".  A namespace in this case gets generated for only those packages which has the stereotype set to "Namespace".  The codegen flag "RTGEN = rtcppgen -fuse-namespaces" should not be used in this case.	
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.	
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.	
RATLC00516572	Addition of CORBA Add-In.  See CORBA Add-In under Enhancements, above.	
RATLC00516650	Enhancement to provide ability to Check-In or Check-Out external documents.	
RATLC00516580	Enhancement to add "Find References" for Code Editor selections.	
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.	
RATLC00522229	RRTEI:  Enhancement to provide Access to Note Contents 

Two New methods added to RRTEI Interface:

IsHyperLink() (desc: check whether the current note content is a hyperlink to a diagram or not)

IsExternalDocLink() (desc: check whether the current note content is a hyperlink to an external doc or a URL)

These methods are added to the NoteView and both return a boolean value.	
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).	
RATLC00535425 / IC45937	Toggle from Selftransition(s) to Internal/External could cause Rose RealTime to crash.	
RATLC00960034 / IC43498	Performing Rose RealTime Model Integrator merge may cause Model Integrator to crash saving an incomplete file.	
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. 
The following sample code disables the  launch of Rose RealTime UI and enables the CORBA Add-In.

$roseRT->{"Visible"} = 0; 
my $addinManager = $roseRT->{"AddInManager"}; 
my $addinCollection = $addinManager->{"AddIns"}; 
my $addinCount = $addinCollection->{"Count"}; 
for ( my $index = 0; $index < $addinCount; $index++) 
  { 
  my $addin = $addinCollection->GetAt($index); 
  if ( $addin->{"Name"} =~/^CORBA$/i) 
    { $addin->Activate(); 
    } 
  }	
RATLC00960539	Moving or Renaming referenced CORBA type would not update the references with location or name change.

The class name changes in the Logical view were not updating the attributes, operations and/or parameters whose types were set to that class.

Now, the attributes, operations and/or parameter types are updated with the changed class name. Updating also occurs when the class is moved across the packages.

The current limitation is that the class name is assumed to be unique.  For example, there are no two or more classes with the same name.  If there are two or more classes with the same name, that class name change will not be populated.

Currently, the deletion of the class will not update the attributes, operations and/or parameter types.	
RATLC00960633	An explicit left click was required to select an element in the browser, followed by a right click to display the context menu (i.e. browsing or generating code for a component).	
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.	
RATLC00961493	After installing Rose RealTime Solaris Patch Tornado Library libTornado2.dll cannot load correctly.	
RATLC00961282	Rose RealTime could crash while clicking on the scrollbar of pick list.	
RATLC00961214	EclipseIntegration.dll fails to un-register when explicitly trying to un-register or when performing uninstall of Rose RealTime.	
RATLC00961451	Reverse Engineering may remove artifacts in the Logical View. 
When you Reverse Engineer CORBA IDL files, Rose RealTime CORBA deletes the old artifacts from the Logical View.

This behavior was introduced as part of the defect fix RATLC00213825.

In order to balance both behaviors a new user level Registry entry is added:

[HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose RealTime\6.5\Addins\CORBA]

"OverWriteModule" = "No"

Rose RealTime CORBA will behave as follows during reverse engineering:

When the Registry Entry OverWriteModule is missing or its value is not set to "Yes" (case insensitive) Rose RealTime CORBA does not delete the artifacts from the Logical View.

When the Registry Entry OverWriteModule value is set to "Yes" (case insensitive) Rose RealTime CORBA deletes the artifacts from the Logical View, keeping the model latest as per the current IDL file only.	
RATLC01075928 / IC44768	Performing Undo-Checkout can cause Model corruption.	
RATLC001079281 / IC45231	Updated LIBSET.MK file for TORNADO22T.PPC603-GNU-2.96 included in Rose RealTime Patch.	
RATLC01077226 / IC44949	Rose RealTime Model Integrator may generate incorrect output causing Rose RealTime to crash.	
RATLC01079281 / IC45231	Updated LIBSET.MK file for TORNADO22T.PPC603-GNU-2.96 included in Rose RealTime V2003.06.15.	
RATLC01079771 / IC45309	Changes made, using the External Editor, were not being saved properly.  After modifying, saving and closing the External Editor the Apply button was grayed out.  Clicking "OK" caused any changes to be lost.	

Known Issues
RATLC / APAR ID	Description	
RATLC00046261	Request to change RTTimespec member tv_sec from long to unsigned long.

Unable to change time data members to long as not all compiler support long long (unsigned long).	
RATLC00141357	Models do not display correctly, using Exceed V6.1.  It is necessary to use Exceed versions 8 or 9.	
RATLC00142001 / IC45453	Attempting to build Rational Rose RealTime application with Rational ClearCase omake may produce the following error message.

: > Compiling comp 
comp.cpp omake: Error: Don't know how to make ""../../libComp/build/libComp.LIB"". 
Stop. 
omake: Unable to lookup target "comp.EXE" . 
Stop. 
omake: Shell line exit status 1. 
Stop. 
Error: Build failed status 0x3 
Workaround: When this occurs use this option/value: CompilationMakeArguments: -k -s -EN.	
RATLC00142586	The following crash may occur when using VNC version 3.3.3:

:MwIGetDIBits(0xf, 0x20, 0x25f, 0xfc801364, 0x0, 0x0) + 0x1638

Workaround:  Use VNC version 3.3.4 or higher.	
RATLC00144439 / IC48737	Editing a class attribute name for an attribute which is same type as the class may cause the following crash:
Rose RealTime exception: 0xC0000005: Access violation writing location 0x00030f40
Workaround:
Assume that there is a class class1. It has an attribute attr1 of type class1. To change the name of attribute from attr1 to attr12:
1.	Open the attribute attr1 specification dialog. 
2.	Change the type of the attribute to some other type (i.e. to basic type or some other class type, say int or class2). 
3.	Click on the Apply button. 
4.	Rename the attribute from attr1 to attr12. 
5.	Click on the Apply button. 
6.	Set the attribute type to the original class type (class1 i.e. the class to which this attribute belongs to ). 
7.	Click on the Apply button. 
8.	Close the attribute specification dialog.	
RATLC00210339 / IC39660	Rose RealTime Web Publisher can consume a large amount of memory when Web Publishing large models.	
RATLC00512567	Online help example for RTMessage_getPortIndex is incorrect.

The code sample included in online help causes compilation errors.
To avoid these errors, change the example to the following:
const RTMessage * msg = RTCapsule_getMsg( &this->std ); 
/* reply to message */ 
RTPort_sendAt( 
&this->port, 
RTMessage_getPortIndex( msg ), 
RTPort_createOutSignal( port, reply ), 
RTPriority_High, 
&someData, 
&RTType_typeOfSomeData );	
RATLC00512572	The code from the online help example for RTS and RTCapsule, context located in <$ROSERT_HOME>/C
 /C Reference/ Services Library API Reference/Minimally Configured Services Library/rts and RTCapsule context causes compilation errors.

The code example currently states the following:

int result = 
RTPort_send( port,RTPort_createOutSignal( port, hey ), RTPriority_General, (void *)0, (RTObject_class
*)0 );
if( ! result ) 
{ 
      RTController * context = RTCapsule_context( this ); 
      log.show("Error on physical thread: "); 
      RTLog_show( RTController_name( context ) ); 
      RTController_perror( context, "send"); 
}

The following corrections are required for the online help example to compile without errors:

Change the first parameter of the method RTPort_send() to be a const RTPort *.  Use &this->port because port refers to the name of the port.

The method RTCapsule_context( const RTCapsule * ) expects a parameter that is a pointer to a RTCapsule. The parameter "this" in the example points to a Capsule's instanceData struct. Use &this->std as a pointer to the RTCapsule.  Use RTLog_show_string() instead of log_show().  Use RTLog_show_string() instead of RTLog_show().

After you apply the changes, the example read:

int result = 
RTPort_send( &this->port,RTPort_createOutSignal( talk, ack ), RTPriority_General, (void *)0,
(RTObject_class *)0 );
if( ! result ) 
{ 
      RTController * context = RTCapsule_context( &this->std ); 
      RTLog_show_string("Error on physical thread: "); 
      RTLog_show_string( RTController_name( context ) ); 
      RTController_perror( context, "send"); 
	
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.
The Inclusionpaths in the C++ Compilation tab of the Component specification dialog can be set using the Component.OverrideProperty method.
An example script, shown below. 
------------------------------------------------------------------------------------------------------ 
line 0: Dim otExtMsgPath As String 
line 1: otExtMsgPath = "$(CCASE_PATH)/Messaging/otExtMsg/include" 
line 2: otExtMsgPath = Chr(34) + otExtMsgPath + Chr(34) + Chr(10) 
line 3: otExtMsgPath = OldPaths + otExtMsgPath ' append the new path to the old paths 
line 4: isOverridden = theComponent.OverrideProperty("C++ Compilation", "InclusionPaths", otExtMsgPath) ' 
------------------------------------------------------------------------------------------------------ 
Line2 description: 
To enable the Compute Dependencies flag in the 
"inclusion paths" dialog change line 2: 
otExtMsgPath = Chr(34) + otExtMsgPath + Chr(34) + "ComputeDeps" + Chr(10) 
To add more number of paths change line 2: 
otExtMsgPath = Chr(34) + "Path1" + Chr(34) + Chr(10) + Chr(34) + "Path2" + Chr(34) + Chr(10) 

Line3 description: 
To append new path to existing path change line 3: 
otExtMsgPath = OldPaths + otExtMsgPath 
To override the path with new path, append to the OldPaths string. 
To set the UserLibraries:Dim UsrPath As String UsrPath = "new path" 
isOverridden = theComponent.OverrideProperty("OT::CppExec","UserLibraries", UsrPath)	
RATLC00517276 / IC38249	C and C++ reference manuals not updated regarding passive class state machines.

The rosert-home-dir\help\rosert_c_ref_guide.pdf and the rosert_cpp_ref_guide.pdf do not include updated information in relation to passive class state machines. On page 16 in the C guide it indicates: "Note: Protocol and Class State diagrams are ignored by the C generator." And on page 46 in the CPP guide it indicates: "Note: Protocol and Class State diagrams are ignored by the C++ generator".

This is now only true for Protocol state diagrams.	
RATLC00518524	Cursor incorrectly positioned in Eclipse when Generate Model Tags is unchecked for component.

RME tags are necessary to position the cursor correctly.	
RATLC00518895	If the CodeSyncEnabled option on the C++ Generation tab is disabled in Rational Rose RealTime, USR tags are not created when the component is generated.  

Although there are no USR tags, you can navigate to that corresponding element in Eclipse.  Instead of positioning the cursor after the // {{{USR tag and before the // }}}USR tag, the cursor is positioned at the top of the file.	
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.	
RATLC00524885	Compute dependencies and Rational ClearCase.

InclusionPaths (Component, C++ Compilation) are for dependency checking between the executable being built and include files such as stdio.h (system files) and my.ext.h (external library include files). If ClearCase/clearmake is used and configured properly, compute dependencies for InclusionPaths should not be necessary for wink-in, assuming that the *.h files are stored in the VOB. The config records will reference the *.h files for the derived object(s). The benefit of turning off compute dependencies would be negligible compared to other build factors, unless there are an unusually large number of include files to check.	
RATLC00526499 / IC42118	Connexis CRM connection not re-established in certain situations.	
RATLC00526781 / IC42179	The following section in the on-line help is incorrect: 

Toolset Guide -> Creating Class Diagrams -> Using State Machine Code Generation for Classes -> Configuring the trigger Stereotype for an Operation.

According to this on-line help documentation, functions with the <trigger> stereotype cannot have arguments. These functions are used to trigger state transitions in passive classes.   

This should correctly state that functions with the <trigger> stereotype can have parameters/arguments (are supported) and in this case the correct code is generated.	
RATLC00530980 / IC43605	Checking out a file from ClearCase through Rose RealTime causes Rose RealTime to lose focus.	
RATLC00531216 / IC43776	Running multiple sessions of Rose RealTime simultaneously is not supported.  Problems may also occur when utilizing certain features of Rose RealTime (i.e. as COM servers), in concurrent sessions.	
RATLC00960625	Unable to Reverse Engineer CORBA, if IDL filename includes a hyphen "-".  This issue is due to current Rose RealTime constraint on component names in component view: 
Component Name can not be empty; can not contain spaces, must start with a letter or '_' and must be made up of ANSI alphanumeric characters"

When reverse engineering, the IDL file will be mapped to a component in the Rose RealTime model.	
RATLC00960634	When adding two classes with same name i.e. "ABC" in both UsecaseView and LogicalView, while adding the second class Rose RealTime displays a warning to the user that "Class 'ABC' now exists in multiple name spaces.  Rose RealTime will not display the qualified name in the Standard Specification dialog.	
RATLC00962126	Rose RealTime CORBA IDL may not generate correctly.

This problem occurs only when the nested classes are used and the non-nested class is assigned to the component, when user tries to model an IDL as shown below using the CORBA Add-In.
module myPkg 
{ 
interface Inter 
{ typedef long myType; 
struct myStruct 
{ 
myPkg::myStruct::myType somedata; 
}; 
}; 
};
It is recommended to create the class myType with stereotype CORBATypedef first. Then create the other elements such as myStruct which uses this type. If the above steps are not followed then the generated IDL may look like this:
module myPkg 
{ 
interface Inter 
{ struct myStruct 
{ 
myPkg::myStruct::myType somedata; 
}; 
typedef long myType; 
}; 
}; 
The error is that the type MyType is used before its definition.	
RATLC00962702	Unable to ignore userDefinedSortWeight flag while using Model Integrator.

This flag appears in petal file when user saves the changes made to the ability to change sort order in the browser.	
RATLC00962993	Horizontal Scroll bar is not positioned correctly when an error/search result's source is accessed.

Initially the slider is at the left of the scroll bar although the code window shows lines in the middle of the code. When clicking on the slider/scrollbar (Horizontal) the source window jumps to the left side of the line.	
RATLC00963015	DocLinks are not checked in/out by recursive check in/out feature.

As these are external documents they do not require petal version updates and are not expected to be included in recursive check in/out feature.	
 
Contacting IBM Rational Software 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.