IBM® Rational® Rose® V2003.06.15 iFix 1 Readme
March 2006

© Copyright IBM Corporation. 1992-2006. 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 iFix includes Defect Fixes and Enhancements for Rose V2003.06.15.
Hardware/Software Information
Hardware / Software requirements for this iFix 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 2003.06.00 Release Notes, please review the following information new in this iFix for Rose V2003.06.13 or V2003.06.14.
Hot Fixes Not Included in Rose V2003. 06.15 iFix 1
The Fixes (shown for the Hot Fixes) listed in the table below are not included in this iFix. 
Rose V2003.06.13 Hot Fixes for Fix Pack 1	
Hot Fix 9	Core Rose	RATLC00484060 / PK21071	Activities lose their reference if containing package is not loaded.	
Rose V2003.06.15 Hot Fixes	
Hot Fix 9	Core Rose	RATLC01089730 / IC46713	The Fix DuplicateID's registry entry fixes the ID of an object, but does not change the ID of references to that object.
In some cases there is not enough information to automatically fix DuplicateID’s and therefore this defect will not be resolved.	
Test Fix 19	Rose J	RATLC0047984	Rose J 1.5 Framework	
	Rose Web Publisher	RATLC00963241 / PK21657	Rose Web Publish output expand "+" is not viewable in model explorer.	
Licensing
No licensing changes are required when installing this iFix.
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_RoseEnterprise_Baltic_iFix1_03.20.2006.bat” file before proceeding with the next steps:
@set HF_INSTALLDIR="C:\Progra~1\Rational\Rose"
@set HF_INSTALLDIR_ANSI="C:\Progra~1\Rational\Rose\ansi c++"
To Complete Installation:
1.	Rose V2003.06.15 must be installed prior to installing this iFix.
2.	Backup your existing release.
3.	Place the following files in a temporary directory: 
o	install_Rose*_2003r5_iFix1_03.30.2006.bat
o	Rose_2003r5_iFix1_03.30.2006.exe
Run  install_Rose*_2003r5_iFix1_03.30.2006.bat

The following preliminary information will display – press Enter to continue:
=======================================================
Rose 2003.06.15 iFix 1
                  Product:  Rose Enterprise
Installs and Registers
Rose 2003.06.15 iFix 1
%TEMP%\Rose_2003r5_iFix1_ERRORLOG.log will include a listing
of any errors encountered while installing this iFix. 
Contact Rational Technical Support if you encounter any Installation Errors.
=======================================================
Press any key to continue . . .
Rose 2003.06.15 iFix 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 a messages as each Add-In included in this iFix is registered:
Registering Rose ANSI C++ Add-In...
Registering Rose ClearCase Add-In...
Registering CORBA Add-In...
Registering Deployment Add-In
Registering Rose J Add-In…
Registering Rose Java2rei Add-In…
Registering Web Publisher Add-In...
Registering Visual C++ Add-In…
Registering Version Control Add-In…
Registering VS Add-In…
Press any key to continue… (Press Enter)
Registering Rose Data Modeler Add-In...
Microsoft (R) .NET Framework Assembly Registration Utility 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002.  All rights reserved.
Types registered successfully
                        Press any key to continue…  (Press Enter)
•	You will then see a message in the Command Prompt Window indicating that the iFix was successfully installed:
=======================================================
Rose 2003.06.15 iFix 1
    Successfully Installed
=======================================================
Press any key to continue . . .
If you encounter any errors during the installation of this iFix, refer to the error log:  
%TEMP%\ Rose_2003r5_iFix1_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 iFix.
With Rational Products
This iFix does not introduce any compatibility issues with other IBM Rational products.
With Third-Party Products
This iFix does not introduce any known compatibility issues with third-party products.
Enhancements & Defect Fixes
Core Rose Enhancements
•	New REI function GetRealizeRelations() available which will return the collection of realize relationships for a Use Case
•	Enhanced handling of text labels
Rose J Add-in Enhancement
•	Limited support for JDK 1.5
Rose Data Modeler Enhancements
•	Maintaining pretty print formatting 
•	Ability to forward engineer entire database instead of one schema at a time
Rose VC++ Add-In Enhancement
•	Limited .NET Integration support extended to VS .NET 2005 (Available as Test Fix to this iFix). 
Note:  Download this feature by accessing www.ibm.com for Rational Rose and selecting All Rational Rose Enterprise downloads. Select from list of available downloads.

Core Rose Enhancements
New REI function GetRealizeRelations( ) available which will return the collection of realize relationships for a Use Case
A new method has been added to the Use Case class. This method retrieves the collection of realize relations belonging to a Use Case. It returns a RealizeRelationCollection. The syntax for using this method is
Set theRealizeRelsColl = theUseCase.GetRealizeRelations ( ) 
where
theRealizeRelsColl As RealizeRelationCollection > Returns the collection of realize relations belonging to the UseCase
theUseCase As UseCase > Usecase from which the collection is being retrieved
Enhanced handling of text labels
Label names attached to dependency, generalization, realize relationships and label names of DecisionBox, Start and End states and for vertical and horizontal synchronizations may now be moved and re-sized.
Rose J Add-In Enhancement
Limited support for Sun JDK 1.5
•	The following Java 1.5 constructs are preserved during round trip engineering: 
o	Enumerations 
o	For-Each Loop 
o	AutoBoxing / UnBoxing

•	The following Java 1.5 constructs are supported during reverse engineering, however, only the bodies of the following constructs will be preserved during forward engineering: 
o	Static Import 
o	Generics 
o	Variable Arguments (VarArgs)
Note:  The Java 1.5 construct, Annotations, is currently not supported during forward or reverse engineering.
Enumerations
Enumerations in Rose are provided with modeling, forward engineering and reverse engineering capabilities. An Enumeration Specification is provided for Enumerations in parallel to Class Specification for a Class.
The Enumeration Specification can be opened by
•	Double clicking an enumeration; or 
•	electing an Enumeration > right click > Open Specifications.
Creation of an Enumeration in Rose:
An enumeration in Rose is a Class with stereotype set to Enum.
Creation of Enumeration literals:
The Enumeration Specification includes a page called Enumeration Code. This page is used to create Enumeration literals / constants. 
•	The Enumeration literal list box in the specification is used to add, rename, and delete enumeration literals. 
•	Every enum literal can have an optional enum body. The Enumeration Constant Body <Read Only> shows the optional enum body. This cannot be edited. 
•	Selection of an enum constant in the list box shows it's optional enum body in the edit box of Enumeration Constant Body <Read Only>. 
•	The Preview button shows the complete list of enum constants with their enum body in the Preview <Read Only> edit box.
Forward Engineering and Reverse Engineering of Enumerations:
The code for the modeled enumeration can be generated using the Rose J code generator. It generates the complete, syntactically correct code. In addition, existing code containing enumerations can be reverse engineered to a rose model.
Code Sample:
public enum Month { 
January(31), 
February(28), 
March(31), 
April(30), 
May(31), 
June(30), 
July(31), 
August(31), 
September(30), 
October(31), 
November(30), 
December(31); 
private final int days;
Month(int days) { 
this.days = days; 
} 
public static void main(String[] args) { 

for(Month month : Month.values( )) 
{ 
System.out.println(month+":"+month.days); 
} 
}} 
For-Each Loop 
For each loop can be used in the method body and enum body.
Code Sample:
for(Month month : Month.values( )) 
{ 
System.out.println(month+":"+month.days); 
}
Static Import
Static imports will be recognized during reverse engineering. 
Note:  These imports will not be preserved in the rose model for further usage.
Code Sample:
import static java.lang.Math.*; 
import static java.lang.Math.PI;
AutoBoxing / UnBoxing
Autoboxing and Unboxing code statements can occur inside the method body and enum body.
Code Sample:
int i = 10; 
Integer val = i; //Autoboxing 
i=val+i; //Unboxing
Generics
Generics are supported during reverse engineering in Rose.
Code Sample:
import java.util.*; 
class GenericsExample<T> 
{ 
<T> GenericsExample( T argIn ) 
public<E> void genericMethod( E argIn0, T argIn1 ) {} 
public List<T> getList() 
{ 
return new ArrayList<T>(); 
} 
}
T and E are type parameters. When reverse engineering, a nested class of stereotype is created, entitled Generics. Type arguments in type are ignored i.e., List<String> is considered as List.
Variable Arguments 
Variable Arguments or VarArgs will be recognized during reverse engineering. The VarArgs are stored in the reverse engineered Rose Model as single dimensional arrays.
For Example the method specification for the VarArgs method:
static void trial(int y,int x) 
{ 
System.out.println("documentation for varargs in java 1.5"); 
}
In this method specification the variable argument int x will be converted to the single dimensional array int[] x in the model.
Rose Data Modeler Enhancements
Maintaining pretty print formatting
If SQL source text for a view is changed (blanks are removed and any pretty printing formatting is removed) after making changes.
Enhancement enabled to save pretty print format, during automatic Create View statement generation, if the value of the following registry key is set to Yes:
HKEY_CURRENT_USER\Software\Rational Software\Rose\AddIns\Data Modeler\Custom Settings\SaveViewPrettyPrintFormat
Ability to forward engineer entire database instead of one schema at a time
A new forward engineering option is available in the Forward Engineering Wizard > Choose Options dialog Generate > Constraints from other schema. If this is checked, and if the schema is forward engineered, the alter table statement for the foreign key will be generated. 
Note:  If a database is forward engineered, this option is ignored.
This is for models with relationships spanning two different schemas. Previously, you would be unable to generate the alter table statements for the foreign keys corresponding to these relationships when forward engineering a schema. Only if the database was forward engineered would these statements be seen in the DDL.

Rose iFix 1 Defects Fixed
Rose iFix 1 includes the following Defect Fixes.

    Rose iFix 1 Defect Fixes

Component	RATLC ID	Description	
Rose Ada	RATLC00040756	Unable to code generate an Ada83 or Ada95 Read-Only model.	
Rose Ada	RATLC00538900 / IC47505	Handle statement(s) created incorrectly when generating Ada95 code. 

When creating a relationship By Value containment, the Handle statement is created, and in this case should not be created.	
Rose Ada	RATLC00538902 / PK12768	Rose Ada may generate code that will not compile due to colon notation and white-space issues.	
Rose Ada	RATLC01099728 / PK12568	The FileNameFormat property does not allow you to alter the directory name when generating code utilizing Rose Ada. Ada requires that filenames and package names are the same. The "FileNameFormat" will format the directory name, not the file. 
To change the value of "FileNameFormat" 
1.	Tools > Options 
2.	Goto Ada95 tab 
3.	In the Type: drop down list take Project 
4.	The FileNameFormat is shown in Model Properties list below. The default value is 128vx_b.
See Online Help for more information.	
Rose ANSI C++	RATLC00050238	Documentation could be lost during round trip engineering of template class parameter.	
Rose ANSI C++	RATLC00961652	Generating Rose ANSI C++ code may make changes to the associated *.h file(s) incorrectly. 

After applying Pattern, generating code, applying documentation change and regenerating code the .h files show changes in the Log. In this case, the *.h files should not change.	
Rose ANSI C++	RATLC00962827	Rose may crash and/or may not exit correctly when attempting to reverse engineer code.	
Rose ANSI C++	RATLC01077555 / PK01533	Rose ANSI C++ may incorrectly delete a constructor body during code generation.	
Rose ANSI C++	RATLC01079317 / PK02217	Rose ANSI C++ unable to generate correct code which initializes attribute in header file. 
The required code generation to initialize attributes in header file will occur only when the value of the following registry key is set to 1:
HKEY_CURRENT_USER\Software\Rational Software\Rose\AddIns\ANSI C++\Custom Settings\User Preferences\InitializeStaticConstMembersInHFile	
Rose ANSI C++	RATLC01097605 / PK04355	Rose ANSI C++ cannot reverse engineer C style comments, i.e. /** ... **/. 

This issue would occur if no space after and before the comment tags.	
Rose ANSIC C++	RATLC01099414 / PK12144	Rose ANSI C++ does not generate #INCLUDE statements when the stereotype of the other class is "<<ENUM>>".
 
As ENUM's are handled differently from class, it is necessary to verify dependencies resolved correctly - a new child list added to resolve this issue.	
Rose ANSI C++	RATLC01103069 / IC47806	Return type parameters are removed during reverse engineering by the Rose ANSI C++ Add-In. 

Reverse engineering the code for a class which has a non empty operation return type, removes the operation return type from the model when the code is reverse engineered twice.	
Rose C++	RATLC00960439 / IC44660	Rose C++ may not handle "\r\n" sequence correctly for nested classes implementation type.	
Rose C++	RATLC00962157	Rose C++ generates incorrect code for copy constructors of a class with attributes set as const int that have an initial value.	
Rose C++	RATLC01075507 / IC43923	Error may occur when attempting to generate code for a C++ class which includes a package specification and package body. In addition, whenever the property inlinecopyconstructor was set to true for a class, the code would contain errors. 
A variable generatecopyconstinit was not getting initialized properly. This fix ensures that the variable is initialized properly for inline constructors and the initializers are generated properly for the copyconstructor.	
Rose C++	RATLC01075508 / IC43924	Rose ANSI C++ generates code which will not compile as it is missing the copy constructor.

The generation of copy constructor initializers were extended to include roles of Associations.	
Rose C++	RATLC01087097 / IC46425	Unexpected package name in parameter types in method signature.

Now, the package name is only added when the package is specified as a namespace.	
Rose C++	RATLC001090058 / PK08674	Rose C++ may generate incorrect code for unsigned attributes. 

They may appear as long unsigned, char unsigned instead of the correct format: unsigned long, unsigned char. Code will generate, but format incorrect.	
Rose C++	RATLC01090059 / PK08673	Rose C++ will generate incorrect code for an operation with a templated type. 

The incorrectly generated code may appear as: 

//## Other Operations (implementation) 
long >< unsigned UserSetting & 
YY::getXXX () 
{ 
//## begin 
YY::getXXX%3A64584600D8.body 
preserve=yes 
//## end 
YY::getXXX%3A64584600D8.body 
} 
The correct code should be: 

//## Other Operations (implementation) 
UserSetting <unsigned long> & 
YY::getXXX () 
{ 
//## begin 
YY::getXXX%3A64584600D8.body 
preserve=yes 
//## end 
YY::getXXX%3A64584600D8.body 
}	
Rose C++	RATLC01090080 / IC46773	Rose C++ may add package name as namespace causing failure to generate code. 

When attempting to generate C++ code for classes within packages, if the attribute type is set as a complex type (i.e. enum, class, typedef, etc.) - Rose C++ will treat the package names as namespaces even though it is not a namespace or a class, incorrectly appending the package name in the generated code.	
Rose C++	RATLC01090107 / IC46781	Rose C++ will not generate implementation code for abstract destructor. 
A new property GenerateAbstractDestructorBody is added for each class. This Property needs to be set to TRUE for the body of the Abstract Destructor to be generated. For models created prior to this release, the properties in the model need to be updated by going to Tools >Model Properties >Update and specifying the rosecpp.pty file in the C++ directory under the rose installation folder.	
Rose C++	RATLC01096968 / IC47150	Rose C++ incorrectly generates fully qualified names for return types.	
Rose C++	RATLC01103081 / IC47807	Rose C++ V2003.06.15 generates code with more spaces than in previous versions of Rose, which causes problems if code under source control. 

The code generated with this fix ensures that additional spaces are not generated before parameter, return or attribute types.	
Rose C++	RATLC01103882 / PK15642	Rose C++ code generation may cause a memory leak.
 
While generating code using Rose C++ Add-In, a significant amount of memory may be consumed due to a memory leak.	
Rose CORBA	RATLC00140522 / IC43121	Associations to structures in CORBAModules do not always generate fully qualified attribute type.	
Rose CORBA	RATLC00249194	Forward declaration may be included rather than include. 
Now, instead of generating the Forward references for interfaces, which are defined in another IDL file, that IDL file gets included.	
Rose CORBA	RATLC00962075	Rose CORBA *.ini needs to be updated to correctly show highlighted keywords in editor.	
Rose CORBA	RATLC01099444 / IC47396	Rose CORBA generates code with class type as CORBAStruct, which cannot be reverse engineered. 

This issue was due to the fact that forward declarations generated with a module for the CORBA elements were not correct. For struct stereotype interface forward declarations were generated. 

Now, the forward declarations are generated within a module only for the CORBA elements such as interfaces and value types.	
Rose Core	RATLC00143414	Elongated lines may incorrectly appear below or above classes as they are placed on the diagram.	
Rose Core	RATLC00210460	When an object in sequence diagram is moved down, all messages (having a message number greater than the object moving down) would also move down. 
Now, only those messages which are dependent on the message (selected to be moved) in the timeline will move down.	
Rose Core	RATLC00248949 / IC42574	Objects become stretched out when changing the Stereotype display of the objects in a Sequence Diagram. 
The following steps may incorrectly change the size of an object: 
1.	Create a package with a class 
2.	Create a new sequence diagram in the logical view 
3.	Drag and drop the class, and then select it and change the stereotype
Note:
As seen in Rose V2003.06.14, the fully qualified name will not be displayed for objects in the sequence diagram when the package is unloaded.	
Rose Core	RATLC00249074 / IC42762	Unable to delete controlled unit on a package overview diagram.	
Rose Core	RATLC00382746	Selected Association Lines in Diagrams appear in Blue. 
Selected Association lines no longer appear in blue, by default. A registry setting is available to enable this new behavior if desired. 
To enable/disable highlighting feature, the registry key EnableHighlight is added: 
HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose\Rose HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\Rose
When the value of this key is set to Yes, the highlighting feature is enabled. Default value of this registry key is No, disabling the highlighting feature i.e., no highlighting of selected relations will occur.	
Rose Core	RATLC00382803	Rose may crash when removing class with fully annotated associations from diagram.	
Rose Core	RATLC00440535	Enhancement: New REI function GetRealizeRelations() available which will return the collection of realize relationships for a Use Case.	
Rose Core	RATLC00450568	Renaming a long transition name in the State Diagram may cause corruption to the name (string).	
Rose Core	RATLC00960948	Enhancement: Enhanced handling of text labels.	
Rose Core	RATLC00961734 / IC46728	Rose diagram distorted when loading workspace 

In a class diagram, straighten some of the unidirectional associations and aggregation relationships and save the model. 

Now reload the model. All the associations are as they were saved. 

But when loading the Model Workspace, some of the associations and aggregation relationships are not shown properly. The lines are not drawn properly: the arrows are half missing and are diagonal instead of straight. 

Clicking and slightly moving a class causes the arrow to "jump" into the correct position, however, even after correcting the diagram and saving the changes before closing Rose, the problem reappears, when the .wsp file is loaded again.	
Rose Core	RATLC0961880 / PK10165	Attempting to compare and sync between Rose model and DDL script can produce the following error: 

"Object reference not set to an instance of an object."	
Rose Core	RATLC01079575, RATLC00961647 / IC46596, PK02403	The text in a note may exceed the note boundaries when using the Fit To Page option under Print Preview in activity diagrams. 
A New Registry Key ScaleFitToPageForNoteActivityState is added under: 

HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose\Rose HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\Rose 

This Key needs to be set to Yes in order to activate this fix.
This fix modifies the formatting of the text in the note view. The formatting is done taking into account the font size and the size of the box and then mapped onto the print preview device context.	
Rose Core	RATLC01089729 / IC46711	Sequence diagrams and associated collaboration diagrams may get out of sync.
 
The fix for this issue ensures that the supplier of the object relationship or object link in the collaboration diagram is set correctly, taking into account the direction of the message.	
Rose Core	RATLC01096281, RATLC01088544 / IC47087, PK07614	Performing a copy and paste of elements in sequence diagram changes text color to Blue. 

In this case, every time a copy and paste is done, the font color is set to the highlight color. 

Now, while copying and pasting, the original font color is saved and retrieved so that no changes to the color will occur while copying and pasting.	
Rose Core	RATLC01098823 / PK11952	Upon opening a model created from a previous version of Rose, you may encounter the following type of warnings: 

The consumer of MessageView object_name does not match the model in the diagram diagram_name. 

The fix for this issue ensures that the supplier of the object relationship or object link in the collaboration diagram is set correctly taking into account the direction of the message and therefore no warning messages appear while model loading. The messages will appear correctly under the link specification.	
Rose Core	RATLC01099106 / IC47364	Rose may crash when dragging a role label toward the bottom right hand corner (for large distance) in Class Diagram.	
Rose Core	RATLC01101978 / PK13772	Custom Stereotype for state could not be added to statechart diagram toolbar. 

Note:  The stereotype was being able be added to activity diagram toolbar.	
Rose Data Modeler	RATLC00244134 / IC37753	Object Model / Data Model transformation of association 1:0..1 depends upon the order of creation instead of multiplicity. 

A new registry key has been added which will need to be enabled to activate this fix: 

[HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\AddIns\Data Modeler\Custom Settings] FKGenerationBasedOnCardinality 

By default the value of this registry entry will be No and this fix will not be activated. 

Upon changing the value of FKGenerationBasedOnCardinality to Yes: 

When an object model is transformed to its corresponding data model, the foreign keys generated will be based upon the cardinalities of the associations and not on the direction in which they are drawn. For example, if an association has cardinalities defined as "0..1" to "1", this causes one of the participating classes optional. In this case the foreign key will always be placed in the class that is optional. 

If this fix is not activated, the default behavior would depend upon the direction of drawing and would decide which table has the foreign key.	
Rose Data Modeler	RATLC00248409	Ability to utilize forward engineering wizard without specifying a DDL filename. 
Now, if no name for a file is entered a dialog box will request the following:
Please enter a name at least one character in length	
Rose Data Modeler	RATLC00248849	Unhandled exception could occur when reverse engineering (DB2) from a database when the schema already exists in Rose. 
Steps to reproduce: 
1.	DB2 database includes a schema called DB2ADMIN. 
2.	In Rose create a database of type IBM DB2 7.x. 
3.	Create a schema of name "DB2ADMIN" and associate it with the database created in step #2. 
4.	Reverse engineer from database selecting database with schema DB2ADMIN.
Unhandled Exception occurs.	
Rose Data Modeler	RATLC00249042	Parser error occurs when reverse engineering alter statement for add column.	
Rose Data Modeler	RATLC00455887 / IC40328	Enhancement: Maintaining pretty print formatting.	
Rose Data Modeler	RATLC00462810 / IC43285	When reverse engineering an OS 390 database, Rose Data Modeler will only reverse engineer the tables you created. 

To reverse engineer all the tables in the database (DB2 OS390) set the following new registry value: 

HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\AddIns\Data Modeler\Custom Settings\RECompleteDB to Yes. The default value is No. 

Note: You will still only be able to reverse engineer the tables that you have permission to access.	
Rose Data Modeler	RATLC00961851 / IC46986	Enhancement: Ability to forward engineer entire database instead of one schema at a time.	
Rose Data Modeler	RATLC00961880 / PK10165	Attempting to compare and sync between Rose model and DDL script can produce the following error: 

"Object reference not set to an instance of an object."	
Rose Data Modeler	RATLC00961913	Compare and Sync may fail (produce incorrect values) with reserved key words. 

The keyword Group was not recognized as an identifier. This was added, so now Group can be utilized as an IDENTIFIER. This means columns, tables, indices etc. can have a name Group. 

Also, while forward engineering these keywords will not be, by default, put inside quotes. 

Workaround: Generate quoted identifiers by selecting this option in the compare and sync wizard.	
Rose Data Modeler	RATLC00961920	Parser error may occur while comparing model and it's generated DDL due to comments and due to GO in procedure body. 
While forward engineering a model with target database of Microsoft SQL server the comments were not generated properly. This caused the parse error in reverse engineering the DDL. It was necessary to write comments with in '/* */' for multiline comments and '--' for single line comments.
Also, appropriate rules added to the grammar to support GO in procedure body.	
Rose Data Modeler	RATLC00962052	Foreign Key generation may not occur correctly based on the setting for FKGenerationBasedOnCardinality.	
Rose Data Modeler	RATLC00962064	Reverse Engineering DDL in SQL Server may produce the following error: 

"Object reference not set to an instance of an object"	
Rose Data Modeler	RATLC00962190	After performing Compare and Sync, relationship type may be incorrect.	
Rose Data Modeler	RATLC01083180 / PK04712	Rose Data Modeler displays Java.Lang.NullPointer exception when attempting to compare and synchronize specific DDL scripts.	
Rose Data Modeler	RATLC01088236 / PK07422	An unhandled exception "Index was out of Range" error may occur when performing a compare and sync with a DDL.	
Rose Data Modeler	RATLC01088513 / IC46569	Rose Data Modeler will display a parser error if attempting to reverse engineer a database, DDL or *.sql file with view definition that uses aliases with "[ ]" notation.	
Rose Data Modeler	RATLC01090054 / IC46771	Rose Data Modeler does not recognize schemabinding keyword when reverse engineering database or DDL.	
Rose J	RATLC00143032, RATLC00248717	Enhancement: Limited support for JDK 1.5.	
Rose J	RATLC00244806	Reverse engineering *.war file could cause Rose to crash.
 
In this case Rose would hang due to trying to delete an object that was not created.	
Rose J	RATLC00459726	If Java code is reverse engineered into Rose and then forward engineered, import statements may be lost. 
A check has been created to determine whether import statements that refer to the classes in the same package are generated. If they are generated and present in the component list of the particular component in question, the import statement for classes in the same package is generated.	
Rose SCC	RATLC00140930 / IC43283	Improved performance - Version Control functions (i.e. Check-in, Check-out, Get Latest, and Add to Version Control). 	
Rose Model Integrator	RATLC00538901 / PK12767	Rose Model Integrator may crash when merging Data Model files created with a Rose version previous to V2003.06.12. 
Rose Data Models created by versions of Rose prior to V2003.06.12 must be updated to be utilized correctly in newer versions of Rose. If the update is not performed, unexpected behavior (including crashes) may occur when performing merge operations. The following describes the one time update that must be performed.
1.	Set the following registry key to Yes: 
HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose\Rose\ForceSave
2.	Start Rose and ensure that the DataModeler Add-In is enabled. 
3.	Open the Rose model and save. While the model is saved the Data Modeler units will be updated in the model. 
Note:
If the Data Modeler units are contained in .cat file(s) then the .cat file(s) must be loaded upon opening the model for the necessary updates to the .cat file to take place. You must select Yes when seeing the prompt, for all subunits that contain Data Modeler units. These units should not be loaded using the Units > Load Schemas option. 
If the .mdl or .cat files containing the Data Modeler units are under Rational ClearCasecontrol, the base version of these files in the integration stream also need to be updated and the updated file must be reset to the base version.
For further information regarding this issue, please contact IBM Rational Technical Support.
4.	Once all models (including subunits) have been updated, reset the following registry key to No: 
HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose\Rose\ForceSave
5.	Uncheck the option Tools >Options >General >Force Save on next load. 
6.	Once all the models have been updated, as described above, they may be merged using the Rose Model Integrator. 
Changes after Applying this Release
a.	The model file will be slightly larger after saving with this Release. 
b.	When performing a text compare between the old and the new model files, you will notice there is new information added for constraint operation objects in .mdl and .cat files. 
c.	3. Dependency Relation Objects are added in the constraint operation object to store the referenced key columns as supplier of the dependency relation, instead of using a KeyList property to store the referenced key columns in constraint object.
Rose Model Integrator Limitation
The Rose Model Integrator may perform incorrect merges if a model element is referenced by another model element by a quidu reference. This may cause model corruption in the automatically-merged Data Modeler model if the dependency relationship object is not picked with the corresponding attribute that is referenced in the relationships quidu. 

Manual follow-up is required to ensure the merged data modeler model is valid. In this case you need to ensure that the quidu of the supplier of the dependency relationship in the model file refers to the corresponding attribute (as specified by the supplier of the dependency relationship) for all the modified keys that are being merged.
Contact IBM Rational Technical Support for more information (instructions) in relation to merging Data Modeler models.	
Rose VC++	RATLC00961650	The association between two classes may not exist in the class diagram after reverse engineering from VC++ project.	
Rose VC++	RATLC01088940 / IC46609	Rose VC++ generates two #include statements when using the External Map	

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.