Rational Rose Service Release 2003.06.01 Release Notes

August 2003

Any reproduction or distribution of this work is expressly prohibited without the prior written consent of Rational.

Legal Notices Information

Scope

This Service Release fixes problems reported with the v2003.06.00 release of Rational Rose.

Hardware/Software Information

Hardware / Software requirements for this service release are the same as those described in the installation Guide for Suites 2003.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 Service Release for Rose:

Core Rose Enhancements

• Rose 2003.06.01 creates models in a new petal version due to changes required in relation to the new Rose J Model Closure Autoload Feature.

Rose J Add-in Enhancements

• Rose J Model Closure Autoload Feature
  
• Enhanced Rose J Fundamental Type Support
  

Rose VC++ Add-In Enhancements

• Automatic Source File Updates in the IDE

Rose Data Modeler Enhancements

• Data Model-Object Model Comparison Wizard
  
• Transformation Synchronization Options (Synchronization between Data Model and Object Model during Transformation)
  
• Enhanced DDL Elements Generation Order
  
• Limited DDL Round-Trip Engineering Support for IBM DB2 OS390 version 7
  
• Enhanced Constraint Generation in DDL for IBM DB2 OS390
  

Installation Information

Prerequisite

Licensing

No licensing changes are required when installing this Service Release.

Installation Issues

Rose 2003.06.00 must be installed prior to installing this Service Release.

After you install a Rational product, you must restart your system before applying this service release. Do not apply this service release until you have restarted your system after installing a Rational product. See RATLC 516372, below.

RATLC00516372 - If the Rational Setup Wizard does not appear when you apply this service release, use Windows Task Manager to end one of the msiexec.exe processes. The Rational Setup Wizard window should appear. If it still does not appear, cancel the next msiexec.exe. As a result, installation of this service release should be successful. Workaround: Restart you system before applying this Service Release.

IMPORTANT NOTICE!! Rational Installer Incompatible with Windows "Change Journal" Feature

Rational has determined that under certain circumstances file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has the windows "Change Journal" (log) enabled on it. Rational is actively working with Microsoft to better understand and identify a fix for the problem.

Before installing any Rational Version 2003 product onto a computer running Windows 2000, please read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434 for the latest information. Alternatively, you can search the Rational Solutions Knowledge Base at http://solutions.rational.com/solutions for the text "Change Journal".

Product Documentation

Documentation for Rational Rose is available on-line at http://www.rational.com/support/products/rose.jsp

Compatibility Issues

This section describes any compatibility issues that could arise from use of this service release.

With Rational Products

This service release does not introduce any compatibility issues with other Rational products.

With Third-Party Products

This service release does not introduce any known compatibility issues with third-party products.

Restrictions and Guidelines on Using Rose 2003.06.01

This Service Release creates and maintains Rose models in a new petal version.  It is important for all users, sharing a model, to upgrade to this version of the Service Release at the same time in order to avoid compatibility issues that may arise when working on the same model while utilizing different versions of Rose.

Defects and Changes

Rose Data Modeler Add-In

Data Model-Object Model Comparison Wizard

Rose Data Modeler now supports comparison between the Data Model and its Transformed Object Model. The following differences between the object model and transformed data model will be displayed in the comparison report:

1. Foreign Key changes in data model. [i.e. the parent / child of an transformed identifying / non-identifying relationship has been changed.]
2. Primary Key changes in Data Model [i.e. The addition / deletion of Primary Key Column(s)]
3. Objects that have been deleted from object model but still exist in data model.
4. Attributes in object model which are not in data model.
5. Attribute data type changes in object model which are not in the corresponding column data type in data model.

The Data Model-Object Model Comparison Wizard allows you to save the differences (report) to a text file for future reference.

To Utilize the Data Model-Object Model Comparison Wizard

1. Right-click on the schema
2. Select Data Modeler->Compare to Object Model
3. Follow the online instructions to compare the selected data model with the transformed object model.

Note: A valid comparison can only be performed only if the Data Model has a Transformed Object Model.

Transformation Synchronization Options

Rose Data Modeler now supports synchronization between Data Model and Object Model during Transformation. Any extra elements will be deleted if the "Delete Extra Element In Destination" option is selected during transformation. The "Delete Extra Element In Destination" option is provided in both "Transform Data Model to Object Model" specification and the "Transform Object Model to Data Model" specification.

Enhanced DDL Elements Generation Order

Rose Data Modeler now generates DDL commands organized by table instead of by command types. Description below lists original (previous) order and new enhanced DDL Elements Generation Order.

Original Generation Order

1. Drop statements
2. CREATE DATABASE statement
3. Create TABLESPACE statements
4. CREATE DISTINCT TYPE statements
5. CREATE TABLE
6. Indexes
7. Alter Table add Foreign Key
8. CREATE VIEW
9. CREATE Stored Procedure
10. CREATE Trigger
11. Comment

Enhanced DDL Elements Generation Order

1. Drop statements
2. CREATE DATABASE statement
3. Create TABLESPACE statements
4. CREATE DISTINCT TYPE statements
5. Repeat until all normal tables are processed:
   1. CREATE TABLE
   2. Indexes for the table
   3. Alter Table add Constraints
6. Repeat until all aux tables and like tables are processed:
   1. CREATE AUX TABLE if aux table / CREATE TABLE …LIKE … if it's a LIKE table
   2. Alter Table add column (For LIKE table, if column definitions are present)
   3. Indexes for the table
   4. Alter Table add Constraints (For LIKE table, if PK constraint or Unique constraints are present)
7. Alter Table add Foreign Key
8. CREATE VIEW
9. CREATE Stored Procedure
10. CREATE Trigger
11. Comment

DDL Round-Trip Engineering

Rose Data Modeler now supports DDL Round-Trip Engineering for Database Type IBM DB2 OS390 version 7 on the following DDL statements:

1. CREATE DATABASE statement (newly added)
2. CREATE AUXILIARY TABLE statement (newly added)
3. User-defined column data type definition in ALTER TABLE ADD <column definition> statement.
4. ROWID data type
5. The following keywords in CREATE TABLE statement:
   1. AUDIT
   2. DATA CAPTURE
   3. CCSID
   4. WITH DEFAULT
   5. DEFAULT
   6. GENERATED ALWAYS
   7. GENERATED BY DEFAULT
   8. As-identity clause
   9. LIKE <table name>
      1. Only <table name> is supported
      2. Column definition for LIKE table is generated as ALTER TABLE ADD <column definition> statement instead of being generated together with the CREATE TABLE statement.
6. The following keywords in CREATE INDEX statement:
   1. BUFFERPOOL
   2. PIECESIZE
   3. CLOSE
   4. COPY
   5. Using-block
   6. Free-block
   7. Gbpcache-block
   8. CLUSTER PART partition information
   9. ASC
   10. DESC
7. The following keywords/constructs in CREATE TABLESPACE statement:
   1. LOB
   2. DSSIZE
   3. SEGSIZE
   4. BUFFERPOOL
   5. LOCKSIZE
   6. LOCKMAX
   7. CLOSE
   8. COMPRESS
   9. CCSID
   10. LOCKPART
   11. MAXROWS
   12. NUMPARTS
   13. MEMBER CLUSTER
   14. Using-block
   15. Free-block
   16. Gbpcache-block
   17. Trackmod-block
   18. PART Partition information

Enhanced Constraint Generation in DDL for IBM DB2 OS390 Database Type

Unique constraints and Primary Key constraint are now generated as ALTER TABLE statements immediately after the CREATE INDEX statement rather than being generated together with CREATE TABLE statement. The ALTER TABLE statement construct will appear as:

ALTER TABLE <table name> ADD <constraint definition>

Rose J Add-In

Rose J Model Closure Autoload Feature

Previously, when attempting to perform code generation or reverse engineering while any controlled unit was unloaded, a dialog would be displayed, informing you that some units are unloaded and incorrect code might be generated.  In Rose 2003.06.00 and earlier, it was not easily possible to determine which units required loading, in order to successfully perform code generation or reverse engineering

The Rose J Model Closure Autoload Feature automatically helps you determine the correct model closure necessary for successful forward and reverse engineering.  Utilizing this feature, Rose will ensure the necessary units are loaded.

The following describes the steps necessary to utilize Rose J Model Closure Autoload.

1. How to Enable the Autoloading feature in a Newly Created Rose 2003.06.01 Model

Enable the “Maintain Model for Autoloading” flag in the model, as described below.

1. Load model file in Rose 2003.06.01.
2. Right-click on the Model Item in the browser.  (The root of the browser tree).
3. Select Open Specification
4. Select "Maintain Model for Autoloading" on the General Tab.
5. Save the Model.

The model is now enabled for Model Closure Autoloading.

2. How to Enable Autoloading  in a Rose model created prior to Rose 2003.06.01

Enable the “Maintain Model for Autoloading” flag in the model and force-save the model.

1. Set the registry key \HKCU\Software\Rational Software\rose\Rose\ForceSave to "Yes"
2. Open the entire model and all subunits in Rose 2003.06.01.
3. Select Maintain Model for Autoloading as described in “How to Utilize the Autoloading feature in Newly Created Rose 2003.06.01 Model”.
4. Save the model. It will ask to save all subunits.  Click "Yes" to save them all.
5. The registry key value is reset.  If you need to force-save another model, repeat Steps 1-4.

• If the Model has not been Enabled for Autoloading (see above) a “Controlled Units Not Loaded” dialog will appear (if the necessary controlled units are not loaded) along with a warning and the option “Continue with no Autoload”.  The warning will provide the instructions shown above to enable the model for Autoloading. It will be important to follow these steps to enable the Model for the Autoloading feature.
• If the Model has been Enabled for Autoloading (see above) a “Controlled Units Not Loaded” dialog will be displayed upon code generation or reverse engineering if all the necessary controlled units are not loaded.  A “Closure Auto Load” radio group box will present the following options:

1. Auto Load this time only
2. Auto Load always
3. Continue with no Auto Load

• Selection of the Auto Load features will result in the loading of necessary controlled units, to complete successful code generation or reverse engineering.
• The “Auto Load always” setting may be reset using the “Closure Auto Load” group box on the Java / J2EE > Project Specification > Code Generation tab.
• An “Auto Load – Files Not Found” dialog will display a list of all files that could not be found, when using the Autoload feature.  In this case the Rose log window will also display a warning indicating which file(s) could not be loaded.  The warning will also include the fully qualified name of the referencing model element and type of reference.  At this point, continuing with code generation could result in incorrect code.  With the information provided, you may provide the file(s) necessary and choose to “Continue” or to “Cancel” this action.
• Model Closure Autoloading maintains the same behavior when Autosync is enabled.
• Reverse Engineering Autoload is controlled by the same “Closure Auto Load” radio buttons on the Project Specification dialog that are used by Code Generation.
• When reverse engineering a class that references classes that are in the code but not in the model, you may select “Continue with no load” when prompted by the “Controlled Units Not Loaded” dialog.  In this case, Rose J will resolve these references by adding empty class(es) to the model while creating the appropriate logical view package(s) for the referenced empty classes.  Reverse Engineering will then complete successfully.
• Perfomance impact exists when utilizing the Model Closure Autoload Feature to perform code generation and reverse engineering, due to file processing.

Enhanced Rose J Fundamental Type Support

You have been able to manage fundamental types with the Rose J Project Specification dialog by adding and removing types displayed on the Fundamental Types tab.  To add a type, you would click on the new entry button and add an entry in java fully qualified name format..  To remove a type, you would select the type from the list and click the delete button.  The resulting list of fundamental types would be stored in the registry of the your local machine.  Some of the major limitations of this current Rose J Fundamental Type Support, include:

1. Fundamental types were not shareable across teams or organization, i.e. there was no way to standardize/unify them.
2. The user interface for adding and removing fundamental types could be enhanced.

In order to resolve the limitations listed above, the following enhancements have been added to improve Rose J Fundamental Type Support:

• The fundamental type list is now saved with the model so that you can share the list across teams or organization by distributing the model.
• Rose J context menus have been added for both class diagram and browser to allow for quick addition to the Java Fundamental Type list.

To Add / Remove a Fundamental Type

1. Click on the target class either in the class diagram or in the browser
2. Select the Java/J2EE->Fundamental type toggle. 

To View Fundamental Type List

1. Select the target class either in the class diagram or in the browser
2. Select Java/J2EE->View fundamental type

Rose VC++ Add-In

Rose VC++ Automatic Source File Updates in the IDE

In earlier versions of Rose VC++, round-trip engineering would write directly to the file system to update code files. If those files were open in the IDE at the time, you would see a dialog box indicating "This file has been modified outside of the source editor. Do you want to reload it?", asking you if you would like to reload the file into the IDE.

In Rose 2003.06.01, if this feature is enabled (see below) files that are already open in the IDE will be modified directly in the IDE, thus avoiding the reload dialogs.

In the case of ClearCase managed files, there was also a problem in the interaction between the Visual C++ IDE and the ClearCase files that reside in the ClearCase link directories. Visual C++ never receives file change notification events from link directories. In this case you would not see the message, indicating the file would need to be reloaded.

In Rose 2003.06.01, if this feature is enabled (see below) the files open in the IDE will automatically be updated during round-trip engineering.

To Enable Rose VC++ Automatic Source File Updates in the IDE: Set the following registry key to "1".

To disable this feature, set the registry key to "0". By default, the value is "0".

HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\Addins\VC++\Custom Settings\Language Properties\ReloadFilesInIDE

Defects fixed in this release

Rose Ada Add-In
RATLC00234488- The following error message could occur, upon generation Ada95 code (which, includes many operations):  "Error:  Internal Error:  The error type is unknown, an old type error id is used."

ANSI C++ Add-In
RATLC00229454, 238717 - ANSI C++ converter crash on test model containing template instantiations.
RATLC00371709 - ANSI C++ Converter may cause Rose to crash on Windows NT4.

Rose C++ Add-In
RATLC00236173 - Header file is not included in the body file when the package body and package spec components are not in the same package.
RATLC00240069 - Generating code on nested classes may cause the following error:  SYSTEM ERROR: line xx, pc 7397: Invalid list index(2) is not in range 0 to 1.
RATLC00449753 - Generating C++ code may cause the following error:  SYSTEM ERROR: line xx, pc 7243: Null handle in request for property "itemKind".

Core Rose
RATLC00018239 - Diagram may incorrectly grow larger when attempting to resize an activity by making it smaller.
RATLC00040908 - Fit to page print option does not work correctly, as truncation occurs in the printed output at the bottom of the diagram.
RATLC00055169 - Unable to scroll down in list box using keyboard arrow keys.
RATLC00213283 - Copying and pasting attributes can cause Rose to lose property values.
RATLC00227852 - Requirement to disable the documentation window whenever an association collection is selected on the browse-tree.  Prior to this change package documentation would be deleted incorrectly when deleting associations collection documentation.
RATLC00229028 - Stereotypes in Activity Diagrams may not be completely visible.
RATLC00239356 - Unresolved transitions may occur by copying and pasting Activity Diagrams containing decisions.
RATLC00239358 - Unresolved object flows may occur by copying and pasting Activity Diagrams containing objects and object flows.
RATLC00239813 - Rose may crash upon copying and pasting a class diagram.
RATLC00240047 - Transition labels may be positioned incorrectly upon editing, moving and showing actions on states.
RATLC00240613 - Rose 2003.06.00 introduced a new Rose log error message, due to corruption that could occur in Sequence Diagrams (RATLC 227839, rose68141). The new error messages would appear as indicated below - alerting you there are discrepancies in the model:

Error: The consumer of the MessageView object ""object1_name"" does not match the model, in the diagram ""diagram1_name"".
Error: The consumer of the MessageView object ""object2_name"" does not match the model, in the diagram ""diagram2_name"".
Error: The supplier of the MessageView object ""object3_name"" does not match the model, in the diagram ""diagram3_name"". etc.

Rose 2003.06.01 includes a further enhancement to automatically fix the messageviews that do not match the message model. When Rose 2003.06.01 detects these problems in a model, it will automatically 'fix' the problem and provide the message above along with the new message below, in the Rose log:  "The discrepancy has been resolved
automatically. Please save and check the model for correctness."

RATLC00241787 - Activity Diagrams can become corrupt upon saving and reopening the Model.
RATLC00368099 - Selecting 'No" to a reload model dialog  request while Rose is minimized will have no effect.
RATLC00371864 - Tools > Model Properties > Update is not updating property values correctly.
RATLC00435516 - Controlling parent package of control unit may cause pathmap error.
RATLC00440533 - Automatic resizing cannot be disabled for Activity and Statechart Diagrams.
RATLC00516372 - If the Rational Setup Wizard does not appear when you apply this service release, use Windows Task Manager to end one of the msiexec.exe processes. The Rational Setup Wizard window should appear. If it still does not appear, cancel the next msiexec.exe. As a result, installation of this service release should be successful. Workaround: Restart you system before applying this Service Release.

Rose Data Modeler Add-In
RATLC00237973 - Unreferenced memory crash when performing reverse engineering on model from DB2 UDB to Rose.

This appears to be due to a database configuration issue when many long table names exist in the Database. This can cause a query overflow on the server. The workaround is to increase the heap sizes on the DB2 server to process more simultaneous requests. To increase the heap size:

Open the IBM DB2 Control Center
Expand the Instances folder
Right click the DB2 instance and click Configure
Click the Performance tab
Scroll to Query heap size,…,query_heap_sz
Increment the existing heap size by increments of 1024 (Do not increase heap size to unreasonable value)

RATLC00371353 - Incorrect column sequence can occur when reverse engineering DB2 database and generating DDL.
RATLC00449524 - Association Tables may not be created correctly during the conversion from Object Model to Data Model.  This will occur, for example upon making the transformation to an existing schema.

Rose Framework Wizard
RATLC00053045 - Framework does not correctly launch, after upgrading Rose.

Rose J Add-In
RATLC00026990 - Rose may generate invalid EJB HOME Interface code.
RATLC00027472 - Parser error occurs when reverse engineering string without a space.
RATLC00028953 - Parser incorrectly occurs on file not selected for reverse engineering.
RATLC00053974 - Business methods in remote interface missing throws RemoteException.
RATLC00212990 - Parser error occurs when reverse engineering Java code as there is no space between "}" and "else".
RATLC00213818 - Allow Rose to detect installation of JBuilder 7.0.
RATLC00239392 - Autosync may stop functioning after deep-deleting a class. Workaround: Use Ctrl+G to manually perform code generation to restart Autosync.
RATLC00239503 - Do not apply Patterns under Use Case View. When attempting to appliy GOF and Java Patterns under Use Case View Rose will hang.
RATLC00239811 - The JBuilder 7.0 IDE Link may not appear to be working correctly, after installation of Rose 2001A.04.11. In this case, trouble shooting and manual integration steps might be necessary.
RATLC00242057 - Code is not generated for any associations drawn from a stateful session bean to any other classes.
RATLC00241564 - Utilizing the Rose J Specification dialog box will override the 'Property Type' property (i.e. BeanProperty) incorrectly to "(1)", causing the error "Enumerated value 'Write Only' does not exist".

Rose VC++ Add-In
RATLC00053232 - VC++ Add-In may not generate code or reverse engineer after upgrading from Rose 2000e.
RATLC00212957 - Rose V++ unassigns interface from component in the model when including midl code.
RATLC00235393 - Rose incorrectly deletes implementation code for abstract destructors.
RATLC00238846 - Entire "Options" groupbox should be enabled or disabled upon "Generate Documentation" check box change
RATLC00241064 - Error occurs when opening Model Assistant on typedefs that are stored in read-only *.cat file. After error occurs, user must kill and restart Rose.
RATLC00242029 - Rose VC++ online Help files may appear to be missing, producing the warning 'topic does not exist'.

Rose Web Publisher Add-In
RATLC00239488 - Types not differentiated from Rose Web Publisher and XMI Add-In.
RATLC00365408 - Enhancement required to sort the contents tree browser identically to how Rose sorts the Rose browser display (sorts elements by type, and alphabetically without regard to case).
RATLC00443632 - Rose Web Publisher Add-In will not create links for diagrams under an operation.

Files changed by this release

Core Rose
[Release_Location]\rose\rose.exe
[Release_Location]\rose\roseres.dll

Rose Ada
[Release_Location]\rose\ada95\roseada95.pty

Rose ANSI C++
[Release_Location]\rose\ansi c++\cppcvtk2.dll
[Release_Location]\rose\ansi c++\cppcvtk2res.dll
[Release_Location]\rose\ansi c++\cppdll.dll
[Release_Location]\rose\ansi c++\cppevent.dll
[Release_Location]\rose\ansi c++\cppres.dll
[Release_Location]\rose\ansi c++\resources.dll

Rose C++
[Release_Location]\rose\c++\rosecpp.cx

Rose CORBA
[Release_Location]\rose\corba\corba_addin.dll
[Release_Location]\rose\corba\corba_addinres.dll

Rose Data Modeler
[Release_Location]\rose\datamodeler\rosedatamodeler.dll
[Release_Location]\rose\datamodeler\rosedatamodelerresources.dll

Rose J
[Release_Location]\rose\java\rjava_addin.dll
[Release_Location]\rose\java\rjava_addinres.dll

Rose Model Integrator
[Release_Location]\rose\modelint.exe
[Release_Location]\rose\modelintres.dll

Rose VC++
[Release_Location]\rose\vc\dlls\rvc.dll
[Release_Location]\rose\vc\dlls\rvccodeview.dll
[Release_Location]\rose\vc\dlls\rvclangprops.dll
[Release_Location]\rose\vc\dlls\rvcmodelassist.dll
[Release_Location]\rose\vc\dlls\rvcres.dll

Rose VS
[Release_Location]\rose\vs\dlls\rvscut.dll
[Release_Location]\rose\vs\dlls\rvsexplorercontrol.ocx
[Release_Location]\rose\vs\dlls\rvsres.dll
[Release_Location]\rose\vs\dlls\rvsrtecontrols.ocx

Rose Web Modeler
[Release_Location]\rose\web modeler\wm-xml.dll

Rose Web Publisher
[Release_Location]\rose\rosewp\rosewebpub.dll
[Release_Location]\rose\rosewp\rosewebpubres.dll

Rose XML
[Release_Location]\rose\xml_dtd\dtd_addin.dll
[Release_Location]\rose\xml_dtd\dtd_addinres.dll

Note:  [Release_Location] is the Rational Products installation directory.  This is typically "C:\Program Files\Rational".

Additional Information

Contacting Rational Customer Support

If you have questions about installing, using, or maintaining this product, contact Rational Customer Support as follows:

When you contact Rational Customer Support, please be prepared to supply the following information:

• Your name, company name, telephone number, and e-mail address
• Your operating system, version number, and any service packs or patches you have applied
• Product name and release number
• Your case ID number (if you are following up on a previously reported problem)