IBM Rational Rose
Release Notes

Rose Windows Version 7.0.0.1 iFix004
Rose Linux Version 7.0.0.0 iFix004
Before using this information, be sure to read the general information under Appendix. Notices.
Contents 
About this document
Who should read this document
Related information
About Rose iFix004
Installing this iFix on Windows
Installing this iFix on Linux 
Announcements, Changes and Known Issues
Restrictions and guidelines
Status of change requests
Problems Fixed in iFix004
Problems Fixed in iFix003
Problems Fixed in iFix002
Problems Fixed in iFix001
Additional Rose Linux Fixes from v7.0.0.1
Files Changed or Added by this iFix
Contacting IBM Customer Support for Rational software products
Appendix. Notices
About this document
This iFix004 Release Note is in addition to the Release Note for Rose Windows v7.0.0.1, v7.0.0.1 iFix001, v7.0.0.1 iFix002, v7.0.0.1 iFix003 and Rose Linux v7.0.0.0, Rose Linux v7.0.0.1 iFix003.
Copyright International Business Machines Corporation 1995, 20078 All rights reserved. US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM(R) Corp.
This document provides information about installing and using IBM Rational Rose, including system and software requirements; new features and enhancements; current known issues and defects fixed.
Who should read this document
This document provides information intended for these users:
•	System administrators who install and configure Rational Rose 
•	Project managers who use Rational Rose models and documents 
•	Advanced users who implement integrations of Rational Rose with other products, work on international systems and localized versions of the product, or encounter problems that are undocumented in the product documentation 
Related information
Documentation for IBM Rational is available on-line at http://www.ibm.com/software/rational/support/documentation/.
About Rose iFix004
This section describes new features and other changes introduced in Rational Rose iFix004.
*Note: iFix004 includes iFix001, iFix002 and iFix003 fixes.
*Note: For Linux this iFix004 should be installed in Rational Rose Linux v7.0 or iFix002 or iFx003 directly. It will include all applicable fixes from v7.0.0.1, iFix001, iFix002 and iFix003.
Installing iFix004 - Rose Windows
The following instructions describe how to install Rational Rose v7.0.0.1 iFix004 in Rose Windows.

Verify Rational Rose v7.0.0.1 is installed, by running Start > Programs > IBM Rational > Rational Software Installed Product Information

You should see IBM Rational Rose * Build ID 7.0.0.1.
o	Download the iFix specific to your v7.0.0.1 Release, as indicated in the table below.

Note:  Download the language version you require, i.e.:

**_** = en_US – English
**_** = ja_JP - Japanese
Rose v7.0.0.1 Release Name	Rose v7.0.0.1 iFix004 to Download	
Rational Rose Professional Ada	7.0.0.1-RATL-RRADA-WIN-**_**-IFIX04.msp	
Rational Rose Professional C++	7.0.0.1-RATL-RRCPP-WIN-**_**-IFIX04.msp	
Rational Rose Enterprise	RATL-RRENT-WIN-**_**-IFIX04.msp	
Rational Rose Professional J	7.0.0.1-RATL-RRJAVA-WIN-**_**-IFIX04.msp	
Rational Rose Modeler	7.0.0.1-RATL-RRM-WIN-**_**-IFIX04.msp	
Rational Rose Data Modeler	7.0.0.1-RATL-RRMPRO-WIN-**_**-IFIX04.msp	
Rational Rose Professional VisualBasic	7.0.0.1-RATL-RRVB-WIN-**_**-IFIX04.msp	
o	Once downloaded, double-click on the iFix *msp file to begin the installation.
Verify Rational Rose v7.0.0.1 iFix004 is installed by running Start > Programs > IBM Rational > Rational Software Installed Product Information.
Installing iFix004 – Linux
Note:  iFix004 may be installed in either Rose Linux v7.0.0.0, Rose Linux v7.0.0.1 iFix002 or iFix003.
•	Download iFix004 - 600804111-8.tar.gz and extract it to a temporary folder. 

•	Extract the iFix:

gunzip <  600804111-8.tar.gz | tar xpf -

•	cd to the 600804111-8 directory and run the install script as indicated below:
./install_i386_linux2_ 600804111-8
•	The installation script will prompt for the Rational Rose release location (i.e. /Rational/releases/rose.7.0.0.0), specify the correct location and press enter:
Enter $ROSE directory: /Rational/releases/rose.7.0.0.0
•	The install script will proceed to backup existing files and copy the new files:
Creating backup if necessary...
Backup: addins/ada83/i386_linux2/libada83addin.so
Backup: addins/ada83/i386_linux2/ada83addin.rsb
Backup: addins/ada95/i386_linux2/libada95addin.so
...
Installing files out of i386_linux2.patch.600804111-8.tar.Z...
   addins/ada83/i386_linux2/libada83addin.so
   addins/ada83/i386_linux2/ada83addin.rsb
   addins/ada95/i386_linux2/libada95addin.so
   …
•	The following question will be displayed.  You may choose to keep or delete the patch file(s).

The i386_linux2.patch.600804111-8.tar.Z file is no longer needed.
Remove i386_linux2.patch.600804111-8.tar.Z?  [yes]

If you would like to keep the file(s), enter “no”.

•	The final installation messages will be displayed:

Inventory file copied to $ROSE/install/patches.
Install script copied to $ROSE/install/patches.
PATCH: 600804111-8  Installed by user_id on Dec 14, 2007 at 09:28
You can run this install script to restore Rose  7.0.0.0 to its state prior
to installing patch 600804111-8:
$ROSE/install/patches/install_i386_linux2_600804111-8 -restore
You can run this install script to commit patch 600804111-8.
 If you do this, you cannot restore later.
$ROSE/install/patches/install_i386_linux2_600804111-8 -commit
Committing a patch will save disk space by removing the backup files.
•	Verify iFix004 is installed correctly by starting Rose Linux and selecting Help > About Rational Rose

Release Version should display as:  7.0.0.1-IFIX04 
Announcements, Changes and Known Issues
This section describes important Announcement, Changes and Known Issues for Rose Linux v7.0/ Rose Windows v7.0.0.1 iFixes.
Note:  This iFix includes updates from previous iFixes.
Note:  Rational Rose is supported on Windows Server 2003
Rational Federal Desktop Core Configuration (FDCC) product support statement:
http://www.ibm.com/support/docview.wss?rs=999&context=SSSHEM&context=SSCSP7T&context=SSSTY3&context=SSCSNZN&context=SSSTWP&q1=FDCC&uid=swg21298277&loc=en_US&cs=utf-8&lang=en
Changes and Known Issues – iFix001 (Windows, only)
The following support has been added in this release:
•	Support on Microsoft Vista. (This does not apply for UNIX/Linux.)
Known Issues when running Rose on Vista
•	Must install Microsoft winhelp32.exe to view Rose Help – see RATLC01187965 for further information.
•	RATLC01188293 – It may be possible to select Rose VB or Rose Apex Add-In’s in the Add-In Manager even though neither Visual Studio nor Rational Apex installed.
•	Rose Add-In information for Vista:

o	Rose Apex Add-In is not supported on Vista, as Rational Apex is not available for Vista.
o	Rose Data Modeler:  Oracle 9i is not supported on Vista and Rose does not formally support Oracle 10g. 

Workaround:  To work with Oracle database, install Oracle 10g client on Vista machine and Oracle 9i server on any other Windows XP machine.  You may then forward and reverse engineer using the Oracle database.

o	Rose Data Modeler:  Unable to install DB2 7.0 on Vista, therefore Rose Data Modeler does not support DB2 7.0 on Vista.
General Known Issues
•	RATLC01189099 – Linux Only – Class Specification dialog for class will not open from browser if class name long and not completely visible.
If a class name is long and it is not completely visible in the browser window, then double-clicking on it will not launch the class specification dialog. To launch the specification dialog from the browser, either scroll the browser window so that the class name is fully visible or make the browser window wide enough to show the class name fully.

This is only an issue in the browser and does not occur in the diagram.
•	RATLC01352111 – Linux Only – Rose may crash upon start-up if Rose Licenses about to expire

Upon starting Rose, you will see a License Manager message box indicating that the License will expire after a specific number of days.  Nothing happens (i.e. Rose does not start) upon selecting the “OK” button.

Contact Rational Technical Support for a License extension, to work-around this problem.
•	RATLC01352232 – Linux Only – Ambiguous error message when performing Ada95 code generation

To reproduce:

- Set Rose Ada95 as language
- Create a new class in Logical View
- Create a component in Component View
- Generate code for Component

It should show an error message in log window, indicating “A Component is not supported.”

Actual Error Message:  SYSTEM ERROR:  line 4860, pc 14941:  Cannot find property set “default_Module-Spec” for property “class” on Module “NewComponent”.
•	IC48750;  RATLC00542317 - Enumerations are available in all JDK frameworks

Rational Rose provides limited support for JDK 1.5. In relation to JDK 1.5 enumerations, Rose allows classes to be stereotyped with the “Enum” stereotype.  Then, during code generation the class is generated as a Java enumeration. Although this stereotype is applicable only for Java 1.5 classes, it may be applied to any other class contained in any of the Framework models

•	IC48425; RATLC00385579 – Attempting to delete EJB name will append additional characters.

To reproduce:
Select Tools > Java/J2EE > New EJB
Choose all defaults, name it ‘TestEJB’ and click OK.
In the tree browser, right click the EJB > Java/J2EE > Open EJB Specification
In the Bean Name field, put the cursor between J and B in ‘TestEJB’, and click Delete (keyboard) several times
The name will grow:  ‘TestEJJBJBJBJBJBJBEJB"
Rational Rose is designed to append a suffix ("EJB" by default) to bean name.
If the bean is named "foo", then Rose appends the suffix string "EJB" causing the full name to appear as "fooEJB".
Whenever Rose finds that the default suffix does not exist, it appends it.
If the bean name is named "fooEJB", and you place the cursor between E and J and press the Delete key, J will be deleted causing the name to be fooEB.  As the suffix ("EJB") no longer exists, “EJB” is appended to create the full name “fooEBEJB”.
•	PK20590; RATLC00483486 - Rose REI Diagram.GetSelectedItems Method returns Items vs ItemViews
Workaround:  Iterate through each RoseItemView on the diagram to check if it is selected.  This may not be scalable in large diagram.
•	The following fixes are not available in Rose Japanese release. 
Note:  A Test Fix for these issues will available, shortly.  Please, contact Rational Technical Support if you have any questions.
1.	PK32143; RATLC00548563 – Japanese OS Only - Unable to reverse engineer CORBA IDL files with comments.
2.	PK32093; RATLC00999288 - Reverse engineering comments in Rose CORBA, following ‘raises’ keyword may fail
3.	PK37594; RATLC01009614 - Reverse engineered CORBA IDL files may have unresolved references
Restrictions and guidelines (Rose Windows, only)
This section describes noteworthy restrictions and guidelines that affect the use of IBM Rational Rose. These are not considered defects because the behavior is not expected to change in a future release.
IMPORTANT NOTICE!! Microsoft Windows 2000 NTFS "Change Journal" defect can cause file system corruption during installation of Rational products
Under certain circumstances, file system corruption can result from installing Rational Version 2003 and 7 products on Windows 2000 to an NTFS partition that has enabled the Windows "Change Journal" (log). This corruption is caused by a defect in Windows 2000. Before you install any Rational Version 2003 or 7 product on a computer that is running Windows 2000:
1.	Disable all virus detection software 
2.	Read IBM Support Technote 1135295. Go to http://www-1.ibm.com/support/us/search/index.html and search for "Rational Installer Change Journal." 
3.	Read Microsoft Knowledge Base article 820888 at http://support.microsoft.com/default.aspx?scid=kb;[LN];820888. This article includes information about an update from Microsoft that fixes the defect. 
Microsoft .NET Framework (v.1.1 or higher) Required to Install Rational Rose Data Modeler and Rational Rose Web Modeler Add-Ins
The Microsoft .NET Framework (v.1.1 or higher) is required to install the Rose Data Modeler and Rose Web Modeler Add-Ins. If you do not have the required .NET Framework version installed and choose to continue the installation, these Add-Ins will not be installed and previously installed versions of these Add-Ins will be disabled. You can install these Add-Ins at any time after you install the .NET Framework by using the Change option of your Rose installation in the Add/Remove Programs in the Control Panel.
For additional information in relation to installing Microsoft .NET Framework, please refer to:
http://msdn.microsoft.com/netframework/technologyinfo/howtoget/default.aspx.
The following describes Rational Rose Enterprise Installation behavior in relation to the Rose Data Modeler and Rose Web Modeler Add-Ins.
 Rational Rose Enterprise Installation behavior in relation to the Rose Data Modeler & Rose Web Modeler Add-Ins	
Microsoft .NET Framework Availability	Installation Results	User Action Required	
New Installation	
.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13 or higher.	Rose Data Modeler & Rose Web Modeler install correctly.	None	
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13 or higher.	General Install continues, however, the Rose Data Modeler & Rose Web Modeler Add-In's will not be installed.	These Add-Ins may be installed at any time after you install the .NET Framework by accessing them from the Control Panel > Add or Remove Programs > Change button. (Also see RATLC00247844, below)	
Upgrade Current Installation	
.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13 or higher.	New v2003.06.13 or higher Rose Data Modeler & Rose Web Modeler Add-Ins install correctly and the previous versions of these Add-Ins will no longer be available.	None	
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13 or higher.	New v2003.06.13 or higher Rose Data Modeler & Rose Web Modeler Add-Ins do not get installed. Previous version of these Add-In's are also deactivated.	These Add-Ins may be installed at any time after you install the .NET Framework by accessing them from the Control Panel > Add or Remove Programs > Change button. (Also, see RATLC00247844, below)	
RATLC00247844: Installing Rational Rose products on machine that does not have .NET Framework version 1.1 or higher installed, warns that the Rose Data Modeler and Rose Web Modeler Add-Ins will not be installed although the installation incorrectly attempts to proceed with installing these Add-Ins. These Add-Ins will be listed in the Add-In Manager, however, you will be unable to activate them. These Add-Ins should be reinstalled (as described above in "User Action Required") after installing .NET Framework 1.1 or higher.
Rose Data Modeler Installation behavior in relation to the Rose Data Modeler & Rose Web Modeler Add-In's	
Microsoft .NET Framework Availability	Installation Results	User Action Required	
New Installation	
.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13 or higher.	Rose Data Modeler & Rose Web Modeler install correctly.	None	
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13 or higher.	Product Installation exits with error.	Rose Data Modeler Edition may be installed at any time, after installing Microsoft .NET Framework version 1.1 or higher.	
Upgrade Installation 	
.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13 or higher.	New v2003.06.13 or higher Rose Data Modeler version is installed correctly and the previous version will no longer be available.	None	
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13 or higher.	Product installation exits with error.	Rose Data Modeler Edition may be installed at any time, after installing Microsoft .NET Framework version 1.1 or higher.	
"MEM_BAD_POINTER" Error May Occur When Installing Rose on Windows XP SP2
This error may occur under the following conditions (#1 & #2 - English OS and #2 - Japanese OS):
1.	One or both of the boxes on the Languages tab of the Control Panel > Regional and Language Options is checked (supporting East Asian and complex script / right-to-left languages). 
2.	Windows XP SP2 is installed. 
When this problem exists, Rose will also display a MEM_BAD_POINTER error when exiting Rose.
The error may be ignored. The Installation and Rose session will run successfully.
Note:  Microsoft has provided a Hot Fix for this issue - Microsoft KB number :KB910466. It may be downloaded from: http://support.microsoft.com/?kbid=910466.
There are separate fixes for the language of the Operating System. Request the fix that applies in your case (i.e. English or Japanese).
Status of change requests
Problems fixed in iFix004
Note: Rose Data Modeler, VC++, and VSS defect fixes are not relevant for Rose Linux.
Component	Problem ID	Description	
Rose ANSI C++	RATLC01206046	Enhanced commenting style, allowing custom comments to be preserved
A new registry setting (HKEY_CURRENT_USER\Software\Rational Software\Rose\AddIns\ANSI C++\Custom Settings\User Preferences\PreserveCommentStyle) has been added to preserve comment style. Set it to “1” (“0” is default value) to preserve comment style (now called CS). 
With this entry set to “1”, Rose will exhibit the same Rose 2003.06.13 behavior of forward and reverse engineering of comments. The Comment Styles options in the ANSI C++ Component Specification dialog will be disabled if this option is selected.
Note:  You must open an ANSI C++ Components Specification dialog at least once after installing this iFix004 to create the registry entry “PreserveCommentStyle” with a default value ‘0”.	
Rose C++	PK32754;
RATLC01000629	Certain settings for the C++ Model Properties may cause Rose C++ code generation to fail, with the following type of error:
SYSTEM ERROR: line 2451, pc 10339: Reference to undefined value: "currentOperGenType"	
Rose C++	PK46976; RATLC01204725	Cyclic dependency may occur error when generating C++ code	
Rose C++	PK55030; RATLC01214688	Namespace symbol may be generated instead of package name	
Rose CORBA	PK32093; RATLC00999288	Reverse engineering comments in Rose CORBA, following ‘raises’ keyword may fail	
Rose CORBA	PK37594; RATLC01009614	Reverse engineered CORBA IDL files may include unresolved references
See description under Additional Information.	
Rose CORBA	PK60162; RATLC01221594	Rose Linux may crash when creating a unidirectional relationship from a use case to an interface	
Rose Core	PK30556; RATLC00494603	Unable to resize a focus of control	
Rose Core	PK35690; RATLC00551378	The ‘Fit in Window’ option may incorrectly re-size (reduce) element’s size
If a collaboration diagram contains object associated to classes that have a stereotype such as entity or boundary, the ‘Fit in Window’ option may reduce the element’s size too much creating blank lines at the bottom of the page or at the rightmost part of the diagram.	
Rose Core	IC47891;
RATLC01103626	Changing the IEditor font may revert to the default upon re-opening the IEditor.	
Rose Core	PK48399; RATLC01206370	Rose may crash when using Ctrl-A to select all text in the documentation view, while diagram is not open
Note: “Select All” using Ctrl+A shortcut key is not supported for the documentation window.

Workaround:   Right click “Select All” for selecting all the text.	
Rose Core	IC49037;
RATLC00485632	The message "Show Access Violations" does not appear, when a class in a package has an association to a class in another package, if the two packages have the same name.	
Rose Core	PK56011; RATLC01216072	Stereotype added class name may appear outside of the class after reopening the diagram	
Rose Core	PK58316; RATLC01352492	COM Exception may occur when setting the TYPE property on Rose Attribute Class
This issue occurs when creating an attribute without creating a class (through a Rose script).	
Rose Core	PK61945; RATLC01355157	Rose may cause display to hang when using the scroll mouse.	
Rose Core	PK63155; RATLC01225982	Word wrapped class name does not appear correctly in SoDA	
Rose Core	RATLC01352819	Rose may crash when setting Stereotype property on attribute	
Rose Core	RATLC01353897	Code comment color may not appear correctly
The Rose IEditor may incorrectly color the comments which follow the Comment Definition #2 style (in the Editor Style tab of Editor Options). To correct this modify the Comment Definition #2 Start to “//” in the Editor options.
Note: If you are starting Rose for the first time, the Comment Definitions will be created correctly.	
Rose Core	RATLC00212753	Default diagram should appear first beneath the package in browser
A registry value key " HKEY_CURRENT_USER\Software\Rational Software\Rose\Rose\DefaultDiagramFirst" has been added and is by default set to "No".   Changing this value to "Yes", the default diagram under the package will appear first among the other diagrams under the package.
Use the right mouse button to select the “Set as Default main diagram” for a Package in the browser window.	
Rose Data Modeler	IC38456; 
RATLC00452970	Attempting to transform Object model to Data model or vice versa would not work correctly, upon changing the name of the attribute or column
A new registry value named “UpdateColumnAttributeNameAtRetransformation” has been added under:
 “HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\AddIns\Data Modeler\Custom Settings”
This value must be set to “Yes” to enable correct changing of name in Object Model to Data Model and vice-versa at re-transformation. By default this is set to “No”. 	
Rose Data Modeler	PK35514; RATLC01005507	Rose may hang momentarily when adding text to a column
Editing the comment field of a column using the documentation window, may have caused Rose to hang for a few seconds.	
Rose Help	PK19116;
RATLC01137517	The following error would occur upon selecting “Compiling Your Script” in Rose online Help:
Cannot find the SCRIPTO.hlp file	
Rose VC++	PK60559; RATLC01354175	Return types that contain an operator such as “&” will not be included correctly in generated code.	
Rose VSS	PK44312; RATLC01144575	The following error could occur when using the Rose Version Control Add-In for Perfoce Version Control, when performing a check-in:
 "Error performing operation"
Rose now supports Perforce Version control system using Microsoft’s Source Code Control (SCC) API.
Note: While checking-in files from Rose, Perforce will show its Submit Changelist dialog to confirm the files to be checked-in.  Do not modify the selection of files in this dialog. Doing so may result in an in-consistent source-control status of files in Rose	

Problems fixed in iFix003
Note: Rose Data Modeler, VC++, and Version Control defect fixes are not relevant for Rose Linux.
Component	Problem ID	Description	
Rose ANSI C++	PK49216; RATLC01189798	Code Synchronization error occurs for operation Return type
If the operation of a class includes a nested class as Return type, forward-engineering displays that the file has been modified, even though there has been no change. Similarly, during reverse-engineering the class containing the operation indicates it was modified, even though no code change was made.	
Rose ANSI C++	PK56680; RATLC01350562	Code Synchronization error occurs for operation when white-space included between exceptions
If the operation of a class includes white-spaces between the exceptions specification in the code, forward-engineering will display that the file has been modified, even though no change has been made in the model or code.	
Rose ANSI C++	RATLC01255784	In-correct code may be generated for operations whose return type is a user-defined class	
Rose C++	PK22207; RATLC00144679	Japanese comment is omitted when generating C++ code
When entering specific sentence in Japanese to Documentation in model elements’ specification (e.g. Class specification, Operation specification, or Attribute specification) and generating code, the specific sentence written in Japanese will be omitted in the code.	
Rose Core	PK31782; RATLC00496582	Rose may crash when performing copy/paste operation between Activity diagrams
A crash could occur if copy/paste operations performed between two activity diagrams.	
Rose Core	PK33243; RATLC00498721	Copying and pasting can cause message links in Collaboration diagrams to become reordered
While pasting messages across collaboration diagrams the messages could be pasted in the order of object links and not the original sequence.	
Rose Core	PK39281; RATLC01194912	The DiagramCollection object may create corrupted icon
Corrupted images could occur for diagrams rendered using REI on Windows 2003 and Vista.	
Rose Core	PK53021; RATLC01212159	Rose may crash when moving an association end from a relationship including an element contained in an unloaded subunit.	
Rose Core	PK53260; RATLC01253726	Rose type UID is removed from the definition if the class that defines the type is in an unloaded unit
The type UID would be removed for parameter/attribute, if the class defining that type was not loaded (from a controlled unit).	
Rose Core	PK53446; RATLC01212810	Unable to save subunit when .mdl root is read-only	
Rose Data Modeler	IC38456; 
RATLC00452970	Attempting to transform Object model to Data model or vice versa would not work correctly, upon changing the name of the attribute or column
A new registry value named “UpdateColumnAttributeNameAtRetransformation” has been added under:
 “HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose\AddIns\Data Modeler\Custom Settings”
This value must be set to “Yes” to enable correct changing of name in Object Model to Data Model and vice-versa at re-transformation. By default this is set to “No”. 	
Rose Data Modeler	PK44355; RATLC01201861	Unhandled exception occurs when opening the specification of the stored procedure parameter by double-clicking on it	
Rose Data Modeler	PK49028; RATLC00149436	The Transformation wizard does not transform the object model initial value to the data model default value	
Rose Data Modeler	RATLC01349387	Unhandled exception may occur upon opening the specification of the Tablespace Specification	
Rose Java	PK25760; RATLC00989235	Disabling the checkbox "Generate Fully Qualified Type" removes argument's documentation text	
Rose Java	PK47138; RATLC00149156	Java method containing long[] type argument may cause it’s content to be deleted during code generation	
Rose Java	IC48826; 
RATLC00963107	Incorrect Default Constructor and Warning Message for read-only *.cat files	
Rose Model Integrator	PK46201; RATLC01188811	Checking Options > Filtering... > "Ignore All" checkbox in Model Integrator causes Model Integrator to incorrectly ignore all differences	
Rose VC	IC49068; 
RATLC00144793	Incorrect code may be generated for nested classes
If an operation in a nested class has a return type as another nested class, then that return type is not fully qualified correctly after code generation.	
Problems fixed in iFix002
Component	Problem ID	Description	
Rose Ada95	 
IC47173; 
RATLC01097073	Rose Ada95 code generator utilizes the class name for the package name rather than correctly using the CodeName property.	
Rose ANSI C++	PK26937;  RATLC00490565	Unable to enter more than 255 bytes in initial value field of attribute in specification.
Rose would not store initial value for an attribute if its size is more than 255 characters.	
Rose ANSI C++	RATLC01185668	Documentation may be lost upon round trip engineering a template class parameter.	
Rose Corba	PK28797;
RATLC00492503	Fundamental CORBA type incorrectly automatically maps to Logical View class.

While resolving type names, Rose will now first try to resolve to a fundamental type (of the assigned language), if that fails then it will resolve against any other available type in the model.	
Rose Core	IC48859;  
RATLC00484415	Loss of model information could occur upon reloading the Collaboration diagram after upgrading from Rose 2003.06.12 to 2003.06.15.	
Rose Core	IC51544;  
RATLC00552019	Upon doing a "Browse Selection..." for a message on a sequence diagram, referring to an overloaded child method, the operation's specifications for the parent method will appear.	
Rose Core	PK24747;  RATLC00487761	Rose may crash upon changing the navigability of an association in a class diagram.
An undefined association in the class diagram was causing Rose to crash when the navigation action was taking place.	
Rose Core	PK37968;  RATLC00508505	Help > About does not correctly display information about iFix or the updated version of Add-In’s installed.
Rose will now display the correct version information in Help > About.	
Rose Core	PK38364;  RATLC00508931	Label for End State in Activity diagram does not appear after drag and drop from the browser.
Core Rose was not creating the labels for the “Start State” and “End State”.  Therefore, the label was not visible in the activity diagram. 	
Rose Core	PK39541;  RATLC01195313	Class name with parenthesis as return type may corrupt operation signature.

Specially formatted class names such as class names for signal opening and ending braces (for example, class name   “A (B)” ) were not being recognized by the Rose.  Rose has been modified to recognize such specially formatted class names.	
Rose Core	PK40084;  RATLC01196122	Rose diagrams may become corrupt if class names are greater than 16 characters and the classes are in different controlled units.
The corruption is a result of cross-referencing among *.cat files if class names greater than 15 characters.	
Rose Core	PK42081;  RATLC01017125	Help > About does not show the correct Rose version.	
Rose Core	PK42191;  
PQ98918 
RATLC01017310, RATLC00737273	Start and End States with long name will display as "..." on activity diagrams.

A registry setting "DisableLabelTruncationForStartEndStates" is available in "HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose\Rose". 
•	Set to 'Yes' if you do not want the labels to be truncated. 
•	By default, this is set to "No", and the labels will be truncated.	
Rose Core	RATLC00244196	Rose may crash when closing Transition Specification.	
Rose Data Modeler	PK18636;  RATLC00481131	The following error message may occur upon trying to open a specification dialog for a class in a class diagram and then clicking on tabs in the specification dialog:
An unhandled exception has occurred in a component in your application. Click continue and application will ignore this error and attempt to continue. Object reference not set to an instance of an object.	
Rose Data Modeler	PK34172;  RATLC00500286	Unable to reverse engineer DDL with limited registry access
Rose was trying to open a registry key under HKEY_LOCAL_MACHINE with read/write access, when only read access was required. Since typical users don't have write access on HKEY_LOCAL_MACHINE, there was an error during reverse engineering.	
Rose Data Modeler	RATLC00249113	Forward engineering of a view into a Sybase database fails if 'where' clause in the view statement ends with a quoted identifier.	
Rose Documentation	IC48750;
RATLC00542317	Enumerations are available in all JDK frameworks.	
Rose Java	PK28940;
RATLC00492641	Casting of generics may produce a parser error when reverse engineering.	
Rose Version Control	PK03942;
RATLC01082326	Unable to add external documents that are attached to a component or to a component diagram, to version control.
The same behavior happens if you try to add a document to a component diagram. This only happens under the Component View and not under the Logical View or Use Case View.	
Rose Web Publisher	PK19183;
RATLC00481657	Using a remote connection may prevent a Rose model from web publishing correctly.
Open Clipboard Failed error messages may occur.

Running Windows Clipboard Viewer (clipbrd.exe) while Rose is in the process of web publishing can also cause Rose to report clipboard errors. Therefore, Windows Clipboard Viewer should not be run while Rose is web publishing.	
Problems fixed in iFix001
Component	Problem ID	Description	
Rose Add-Ins	RATLC01186777	Unable to select the following Add-In’s after installing Rose on Vista:
o        Rose C++, Rose VC++, Rose Ada83, Rose Ada95, Rose VB	
Rose Add-Ins	RATLC01188007	Unable to generate code for the following Rose Add-In’s on Vista:
•	Rose C++
•	Rose Ada83
•	Rose Ada95
By default, code was generated in <install_dir>\rose\addin_name\source where <install_dir> is usually "C:\Program Files\Rational".
Since Vista does not allow writing to the "Program Files" directory, source code generation would fail.
Code is now generated in user directory. User directory is defined by the environment variable "USERPROFILE".	
Rose ANSI C++	IC50743;  
RATLC01186025	"Warning: Unresolved relation..." Error may occur.
This unnecessary warning, could occur because of model corruption - due to parsing error. The parser was not able to recognize global namespace(s) inside a template.	
Rose ANSI C++	IC51343;  
RATLC01006367	ANSI C++ synchronization issues could occur.
The Resource strings for 'Class modification(s)' and 'No model updates have been performed'  were missing.
Also, a check on comment style was performed for both forward and reverse engineering which resulted in wrong setting for the file change flag.	
Rose C++	PK39011;  
RATLC01187403	A system error could occur when generating Rose C++ code.
While generating code, the "FullyQualifiedInclusionProtectionSymbol" feature was added to include fully qualified name for the “InclusionProtectionSymbol" property in the header file.
Note:  A check is added to allow code generation only for appropriate modules.	
Rose Data Modeler	RATLC01188008	The Rose Data Modeler may hang when attempting to forward engineer to database.
Rose Data Modeler attempted to generate log file directly in C: drive.	
Rose Framework	RATLC01188160	Permission error when attempting to save Rose Model after loading Framework.
This was due to Frameworks being read-write vs. read-only.	
Rose Help	RATLC01187965	The Windows Help program (WinHlp32.exe) is not available in Vista.
However, it is available for download from Microsoft at:. 
http://www.microsoft.com/downloads/details.aspx?familyid=6ebcfad9-d3f5-4365-8070-334cd175d4bb&displaylang=en

Download this and install as a pre-requisite to run Rose Help	
Rose Registry Entries	RATLC01188075	All registry entries now made through HKEY_CURRENT_USER.
Also, changed corresponding reads to HKEY_CURRENT_USER and if not found in HKEY_CURRENT_USER, to read from HKEY_LOCAL_MACHINE.	
Rose VB	RATLC01187966	Unable to activate Rose VB Add-In on Vista.	
Rose VC++	RATLC01187964	Unable to forward and reverse engineer using Rose VC++ Add-In when Rose installed on Vista.	
Rose VC++	PK41407;  RATLC00554424, RATLC00144994	Allow Rose to recognize both .NET 2002/2003 and .NET 2005 installations.
 Previously, a separate Test Fix would have to be applied to integrate with either .NET 2002/2003 or .NET 2005.  The Test Fix is no longer necessary.	
Additional Rose Linux Fixes from v7.0.0.1
Rose Ada	PK21659; 
RATLC00963242	Rose Ada95 protected objects are declared as 'is separate'.	
Rose Ada	PK23728; 
RATLC00986011	Rose Ada may generate invalid syntax for Ada95 attributes. 
Rose may not maintain the parentheses in the attribute specification.	
Rose Ada	RATLC01185354	Ability to generate constructors, destructors and copy constructors as "separate". 
To make the Default Constructor separate for all classes, set the newly added property 'SeparateDefaultConstructor' to True (Default : False). To set the value of "SeparateDefaultConstructor":
1.	Select Tools > Options 
2.	Select "Ada95" tab 
3.	Select "Class" from the "Type:" drop down list 
4.	Select "SeparateDefaultConstructor" under Model Properties. The default value is False. Set to True.
To make the Default Copy Constructor separate for all classes, set the newly added property 'SeparateCopyConstructor' to True (Default : False). To set the value of "SeparateCopyConstructor":
1.	Select Tools > Options 
2.	Select "Ada95" tab 
3.	Select "Class" from the "Type:" drop down list 
4.	Select "SeparateCopyConstructor" under Model Properties. The default value is False. Set to True.
To make the Default Destructor separate for all classes, set the newly added property 'SeparateDestructor' to True (Default : False). To set the value of "SeparateDestructor":
1.	Select Tools > Options 
2.	Select "Ada95" tab 
3.	Select "Class" from the "Type:" drop down list 
4.	Select "SeparateDestructor" under Model Properties. The default value is False. Set to True.	
Rose ANSI C++	IC48533; 
RATLC00144253	ImplementationType value may only generated during reverse engineering, every other time.	
Rose ANSI C++	IC50242; 
RATLC00994863	Adding an exception that is not in the model to an operation may block Rose ANSI C++ forward engineering. 
Workaround: Choose an exception using the "Select Exception Class" window available by clicking on the "..." button in the Exception tab of the Operation Specification window.	
Rose ANSI C++	PK20821; 
RATLC00144479	Zombie rose.exe process could remain upon exiting Rose after generating code for a class that had an attribute whose type was another class. 
This issue occurred as not all COM references were freed.	
Rose ANSI C++	PK23574; 
RATLC00486572	Multiline comments may be deleted from the header file after reverse engineering and then performing a code generation. 
The start point to replace/modify the class comment was not correct if the header comment was a block comment. The header comment was ignored only if it was a line comment.
Now, the header comment will be ignored even if it is a block comment.	
Rose ANSI C++	RATLC01184832	Rose may exit when attempting to reverse engineer ANSI C++ code.

This could occur due to buffer overflow because of a syntax error in parsing a non-inline destructor definition including template arguments.	
Rose C++	IC49062; 
RATLC00144786	When the InclusionProtectionSymbol is set to AUTOGENERATE, the code that is generated in the header files in the #ifndef & #define statements is incorrect. 
Request for fully qualified name for the "InclusionProtectionSymbol" property in Rose C++. The property contains only one attritbue name "AUTO GENERATE".
Now, one more boolean value property has been added. The new property name is "FullyQualifiedInclusionProtectionSymbol". The default value of this property is "False". If it's value is changed to "True" then the InclusionProtectionSymbol value in the header file will contain the fully qualified name of the header file.
For example:
For a class "NewClass" inside a package "NewPackage"
if FullyQualifiedInclusionProtectionSymbol = "True" then generated code would be:
# ifndef NewPackage_NewClass_h 1
#define NewPackage_NewClass
and
if FullyQualifiedInclusionProtectionSymbol = "False" then
# ifndef NewClass_h 1
#define NewClass	
Rose C++	PK26617; 
RATLC490201	Rose may hang when double byte character comments and statements are added in the preserved region. 

In this case, the status of generating code "Generating code..." does not end. [Cancel] in the "Code generating status" windows does not work. Rose must be closed from [File] > [Close] menu option or terminated from Task Manager.	
Rose C++	PK32265; 
RATLC00497276	C++ templates used as function parameters may be generated twice during Rose C++ code generation.	
Rose C++	RATLC0042340	The DataMemberVisability Property may not update properly upon opening an older Rose model.	
Rose CORBA	PK32143; 
RATLC00548563	Unable to reverse engineer CORBA IDL files with comments. 

Rose CORBA would stop reverse engineering if a comment was encountered between the parentheses at the beginning of the operation and the first operand or if comments were encountered after the operand, if the operation return type was "factory".

Note:  This is still an issue in Rose iFix002 (Japanese OS).	
Rose CORBA	PK33098; 
RATLC00498528	When generating CORBA code in Rose, it generates the "typedef" definition in the wrong place. 

By declaring the definition in the wrong place, the stub code cannot be created from the IDL file. In addition, when using the "typedef" variable it uses the fully qualified name which is not necessary if it is declared correctly.	
Rose Core	PK21071; 
RATLC00484060	Activities lose their reference if containing package is not loaded. 

If there are two controlled packages with the same activity name and one of the packages has a reference to the activity of the other package in it's activity diagram, if only this package is loaded, then Rose tries to resolve the reference by name and not by ID and therefore refers to the local activity thereby loosing the original reference. 
Now, activities do not lose their reference if the containing package is not loaded	
Rose Core	PK22219; 
RATLC00144685	Problems when creating/modifying DECIMAL(x,y) 

The type of an attribute when set to DECIMAL(4,5) is getting set as (4,5),which is not expected. This fix ensures that the type is correctly set to to DECIMAL(4,5)	
Rose Core	PK31142; 
RATLC00495540	Rose v7.0 may hang when opening a model saved with a previous version of Rose. 
This problem is caused by coordinate and pctDist values that are set too high. 
Rose will now check for an abnormal coordinate value, before positioning the label in the view. If a coordinate value has exceeded it's bound, it will be recalculated with reference to the associated segment, with pctDist set to 0.5 and height set to 60 (Default values). A warning will be displayed in the Rose log regarding this issue and you will need to explicitly Save, in order to preserve these changes.	
Rose Core	RATLC00482465	Duplicate ID message should not be repeated in the Rose log and should indicate specifically related *.cat file(s). 
Rose will now output a warning to the log whenever a Duplicate ID is found. The warning will contain the fully qualified name and model/cat file names of the clashing objects.	
Rose Core	RATLC01100355	Rose may delete all objects with the same name when deleting an object with that name.

It also formats the object so that if the object has no name Rose names all the objects with no name the same.	
Rose Core	RATLC01184530	Performance enhancement when loading large models in Rose. 
Model Loading performance enhanced by ~15% - ~40%.	
Rose Model Integrator	PK27045; 
RATLC00145571	Rose Model Integrator may generate corrupt model files when attempting to merge two Sequence Diagrams if two mechanisms have the same name.	
Rose Web Publisher	PK21657; 
RATLC00963241	Rose Web Publisher output using expand "+" is not always viewable in model explorer. 	
Rose Web Publisher	RATLC01186705	HTML models published using Rose Web Publisher in previous Rose versions (Rose 7.0 and earlier) may not display correctly when viewed in Internet Explorer 7 on Windows XP SP2. For example, significant flickering can occur. 

To view these models correctly the following files need to be copied to the HTML model's directory: 
1.	Copy install_dir\rosewp\files\root.html and install_dir\rosewp\files\frames.html to published model directory. 
2.	Copy and rename install_dir\rosewp\files\root.html as published model root file to published model directory. install_dir represents the directory where Rose 7.0.0.1 has been installed. HTML models published with Rose 7.0.0.1 do not need this workaround and should display correctly.	
Rose Web Publisher	RATLC00145382	Links to elements that exist under an operation from a diagram in another package are not correct.	
Additional Information
PK37594; RATLC01009614 - Reverse engineered CORBA IDL files may have unresolved references
Please use the following step to reverse engineer CORBA IDL files, which may include dependencies between themselves and may also cause “Check Model” errors if they are not reverse engineered correctly.
1.	Set registry option HKEY_CURRENT_USER\Software\Rational Software\Rose\AddIns\CORBA\MultiPassRE to “Yes” and start Rose.  If this value is not present then please start and exit Rose once with CORBA Add-In is enabled, this will create the option (with the default value “No”).
2.	In the CORBA Reverse Engineering dialog, select all the IDL files to be reverse engineered (using Add/Add All/ Add Recursive buttons). The order of adding the files is not important.
3.	Click “Select All” to select all the IDL files for reverse engineering.  All the files in the list box should now be selected.
4.	Click “Reverse” to start reverse engineering of all the selected files.
5.	Rose CORBA will then reverse engineer each of the files, de-selecting each file as it is completed.
6.	If Rose encounters a file which includes elements that refer to missing target elements, it will issue a log entry (“Error: The file <<idl file name>> contains unresolved elements”), and it will keep that file selected in the list-box. Note that all other elements in this file (which do not have missing targets) will still be created in the model. Only those elements which have missing target elements will not be created.
7.	After all the files are processed, only the file which had missing targets for their elements will remain in the list.
8.	Click “Reverse” again and Rose will reverse engineer the remaining selected files (from step 6).
9.	The missing elements will now be created with the correct relationships (assuming that the targets elements were created later on during the reverse engineering process in steps 5/6).
10.	If there are no missing targets, all files will appear un-selected. This indicates success and Check Model will no longer report any problems, in this regard.

Files Changed or Added by this iFix
Rose Windows Files Changed
Location relative to $ROSE_HOME (typically, C:\Program Files\Rational\Rose on Windows)
.\ada83\ada83addin.dll
.\ada83\ada83res.dll
.\ada95\ada95addin.dll
.\ada95\ada95res.dll
.\ada95\rose_ada95.cx
.\ansi c++\cppcvtk2.dll
.\ansi c++\cppcvtk2res.dll
.\ansi c++\cppdll.dll
.\ansi c++\cppevent.dll
.\ansi c++\cppres.dll
.\ansi c++\resources.dll
.\c++\cppaddin.dll
.\c++\cppaddinres.dll
.\corba\corba_addin.dll
.\corba\corba_addinres.dll
.\datamodeler\DMNET.dll
.\datamodeler\Resource.dll
.\help\scripto.hlp
.\java\rjava_addin.dll
.\java\rjava_addinres.dll
.\modelint.exe
.\modelintres.dll
.\rose.exe
.\roseres.dll
.\vc\dlls\rvc.dll
.\vc\dlls\rvcapplicationstarter.dll
.\vc\dlls\rvccompprops.dll
.\vc\dlls\rvcvs7addin.dll
.\version control\dlls\rsssourcectl.dll
.\webpub\rosewebpub.dll
.\webpub\rosewebpubres.dll
.\xml_dtd\dtd_addin.dll
.\xml_dtd\dtd_addinres.dll

Rose Linux Files Changed
Location relative to $ROSE_HOME (rational_dir/releases/rose.7.0.0.0)
./addins/ada83/i386_linux2/libada83addin.so
./addins/ada83/i386_linux2/ada83addin.rsb
./addins/ada95/i386_linux2/libada95addin.so
./addins/ada95/i386_linux2/ada95addin.rsb
./addins/ansic++/i386_linux2/libcppdll.so
./addins/ansic++/i386_linux2/cppdll.rsb
./addins/c++/i386_linux2/libcppaddin.so
./addins/c++/i386_linux2/cppaddin.rsb
./addins/clearcase/i386_linux2/libclearcase_addin.so
./addins/clearcase/i386_linux2/clearcase_addin.rsb
./addins/corba/i386_linux2/libcorba_addin.so
./addins/corba/i386_linux2/corba_addin.rsb
./addins/cppcvt/i386_linux2/libcppcvtk2.so
./addins/cppcvt/i386_linux2/cppcvtk2.rsb
./addins/cppevent/i386_linux2/libcppevent.so
./addins/cppevent/i386_linux2/cppevent.rsb
./addins/dtd/i386_linux2/libdtd_addin.so
./addins/dtd/i386_linux2/dtd_addin.rsb
./addins/java/i386_linux2/librjava_addin.so
./addins/java/i386_linux2/rjava_addin.rsb
./addins/java/java2rei/i386_linux2/libjava2rei.so
./addins/java/java2rei/i386_linux2/java2rei.rsb
./addins/mdlint/i386_linux2/compare.rsb
./addins/mdlint/i386_linux2/merge.rsb
./addins/mdlint/i386_linux2/modelint
./addins/mdlint/i386_linux2/modelint.rsb
./addins/mdlint/i386_linux2/xcompare.rsb
./addins/mdlint/i386_linux2/xmerge.rsb
./addins/rosewp/i386_linux2/librwebutil.so
./addins/rosewp/i386_linux2/rwebutil.rsb
./help/scripto.hlp
./i386_linux2/bin/rjavarelay
./i386_linux2/bin/rjavarelay.rsb
./i386_linux2/bin/rose_exe
./i386_linux2/bin/rose_exe.rsb
./i386_linux2/bin/Rose_Message_Server
./i386_linux2/bin/rosemsg
./i386_linux2/lib/libRForteReceiver.so
./i386_linux2/lib/libRJBuilderReceiver.so
./i386_linux2/lib/RForteReceiver.rsb
./i386_linux2/lib/RJBuilderReceiver.rsb
./addins/ada95/rose_ada95.cx
./addins/ada95/ada95.reg
./addins/ada95/roseada95.pty
./addins/ada83/ada83.reg
./addins/ansic++/ansic++.reg
./addins/ansic++/cpp.pty
./addins/cppcvt/cppcvt.reg
./addins/cppevent/cppevent.reg
./addins/corba/corba.reg
./addins/java/java.reg
./addins/c++/rosecpp.cx
./addins/c++/rosecpp.pty
./addins/c++/c++.reg
./addins/mdlint/mdlint.reg
./addins/rosewp/rosewp.reg
./addins/rosewp/files/frames.html
./addins/rosewp/files/root.html
./addins/rosewp/files/browser.jar
./addins/dtd/dtd.reg
../mw/lib-linux_optimized/gdiuser32.rsb
../mw/lib-linux_optimized/kernel32.rsb
../mw/lib-linux_optimized/libgdiuser32.so
../mw/lib-linux_optimized/libkernel32.so
../mw/lib-linux_optimized/libpslib.so
Contacting IBM Customer Support for Rational software products 
If you have questions about installing, using, or maintaining this product, contact IBM Customer Support as follows:
The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support Home page for Rational products can be found at http://www.ibm.com/software/rational/support/.
Voice Support is available to all current contract holders by dialing a telephone number in your country (where available). For specific country phone numbers, go to http://www.ibm.com/planetwide/.
Note:
 
When you contact IBM Customer Support, please be prepared to supply the following information: 
•	Your name, company name, ICN number, 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 PMR number (if you are following up on a previously reported problem)
Appendix. Notices
This information was developed for products and services offered in various countries throughout the world. IBM may not offer the products, services, or features discussed in this document in every country. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: 
IBM Director of Licensing
IBM Corporation North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: 
IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
Department BCFB
20 Maguire Road
Lexington, MA 02421
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
USE OF SAMPLES CONTAINED IN THIS INFORMATION:
This information may contain sample application programs in source language, which illustrates programming techniques on various operating platforms.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
(c) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (c) Copyright IBM Corp. _enter the year or years_. All rights reserved.
ADDITIONAL NOTICES:
Additional legal notices may be included with the license agreement accompanying the licensed program described in this document.
TRADEMARKS:
AIX, ClearCase(R), ClearCase Attache(R), ClearCase MultiSite(R), ClearDDTS(R), ClearGuide(R), ClearQuest(R), DB2, DB2 Universal Database, DDTS(R), Domino(R), IBM, Lotus(R) Notes, MVS(TM), Notes, OS/390(R), Passport Advantage(R), ProjectConsole(TM) Purify(R), Rational, Rational Rose(R), Rational Suite(R), Rational Unified Process(R), RequisitePro(R), RUP, S/390(R), SoDA(R), SP1, SP2, Team Unifying Platform(TM), WebSphere(R), XDE(TM), and z/OS(R) are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX(R) is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product or service names may be trademarks or service marks of others.