IBM Rational Rose RealTime
Release Notes
 
Version 7.0.0.1 iFix006 
 
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 IBM Rational Rose RealTime v7.0.0.1 iFix006
Installing Rose RealTime v7.0.0.1 iFix006
Installing on Windows
Installing on Solaris
Installing on Linux
Compatibility Issues
Rose RealTime / Rational Product Integrations
With Third-Party Products
Rose RealTime Petal Format or Code Generation
Rose RealTime TargetRTS Changes
Announcements, Changes and Known Issues
Status of change requests
Problems fixed in v7.0.0.1 iFix006
Problems fixed in v7.0.0.1 iFix005
Files Changed or Added by this iFix
Files Common to all Platforms (Windows, Solaris & Linux)
Windows
Solaris
Linux
Contacting IBM Customer Support for Rational software products
Appendix. Notices
 
About this document
This iFix006 Release Note is in addition to the Release Note for Rose RealTime v7.0.0.1.
Copyright International Business Machines Corporation 1999, 2009. 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 RealTime, 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 RealTime
§         Project managers who use Rational Rose RealTime models and documents
§         Advanced users who implement integrations of Rational Rose RealTime 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 IBM Rational Rose RealTime v7.0.0.1 iFix006
This chapter describes updates to the documentation that pertain to installing Rational Rose RealTime v7.0.0.1 iFix006.
System and software requirements
This iFix supports the following Operating Systems:
§         Microsoft Windows 2000 Professional SP4; XP Professional with SP2, Vista Business SP1
§         Red Hat Linux v8.0, 9.0, Enterprise 3 & 4
§         SUN Solaris 8, 9 & 10
Post installation steps 
Toolset 
Run the toolset and ensure that the version number is correct. In Rational Rose RealTime, click Help > About Rational Rose RealTime and verify that the version number for Rational Rose RealTime is 6.6.3609.0 (Solaris & Linux and Windows)
CodeGen
If you wish to take advantage of the problems fixed in the code generators, you need to rebuild and re-link your models.
RQA-RT 
No additional steps are required.
RTJava Models
No additional steps are required.
C TargetRTS
If you wish to take advantage of the problems fixed in the C TargetRTS, you need to rebuild your Target RTS libraries and re-link your models.
C++ TargetRTS 
If you wish to take advantage of the problems fixed in the C++ TargetRTS, you need to rebuild your Target RTS libraries and re-link your models.
Connexis(TM)
If you wish to take advantage of the problems fixed in the DCS, you need to rebuild and re-link your models. It will also be necessary to rebuild the DCS library if your target is not one of the pre-built DCS libraries supplied in this Release.
Installing Rose RealTime v7.0.0.1 iFix006
This section describes installing Rational Rose RealTime Version 7.0.0.1 iFix006.
Note:  Rose RealTime v7.0.0.1 iFix004 must be installed before installing Rose RealTime iFix006.
Rose RealTime v7.0.0.1 iFix006 Windows Installation Instructions
•	Verify Rational Rose RealTime v7.0.0.1_iFix004 is installed by running Start > Programs > IBM Rational > Rational Software Installed Product Information.
o	If Rose RealTime v7.0.0.1 iFix004 is installed you will see IBM Rational Rose RealTime * Build ID 7.0.0.1- IFIX04.
•	Download the iFix specific to your v7.0.0.1_iFix006 Release.
•	Once downloaded double-click on the iFix *msp file to begin the installation.
•	Press Update
•	Press Next
•	Press Install
•	Installation Complete
•	Verify Rational Rose RealTime v7.0.0.1 iFix006 is installed by running Start > Programs > IBM Rational > Rational Software Installed Product Information.
o	The build-id for Rose RealTime should be 7.0.0.1-IFIX06
Rose RealTime v7.0.0.1 iFix006 Solaris Installation Instructions
§         setenv $ROSERT_HOME <rational_dir>/releases/RoseRT.7.0.0.0 if you are using C Shell. On Bourne, K and/or Bash Shell enter:

export ROSERT_HOME=<rational_dir>/releases/RoseRT.7.0.0.0
•	copy RoseRT.v7.0.0.1.iFix006.sun5.tar.gz to temporary directory
•	Verify Rational Rose RealTime v7.0.0.1_iFix004 is installed, if not installed, upgrade to Rational Rose RealTime v7.0.0.1_iFix004 prior to the installation of Rational Rose RealTime v7.0.0.1_iFix006.
§         Once it has been determined iFix004 is installed, run the following command to unzip the patch

gunzip < RoseRT.v7.0.0.1.iFix006.sun5.tar.gz | tar xpf -
The directory "700906221-1" will be created.
§         cd 700906221-1
§         run "./install_sol_700906221_1"
This command will back-up the pertinent files in your Release and install the iFix.  You will then have the following options:
You can later run this install script to restore Rose RealTime 7.0 to its state prior to installing patch:
 
$ROSERT_HOME/install/patches/install_sol_700906221_1 -restore
 
You can later run this install script to commit patch 700906221-1.  If you do this, you cannot restore later.
$ROSERT_HOME/install/patches/install_sol_700906221_1 -commit
 
Committing a patch will save disk space by removing the backup files.
 
Rose RealTime v7.0.0.1 iFix006 Linux Installation Instructions
§         setenv  ROSERT_HOME <rational_dir>/releases/RoseRT.7.0.0.0 if you are using C Shell. On Bourne, K and/or Bash Shell enter:
export ROSERT_HOME=<rational_dir>/releases/RoseRT.7.0.0.0
•	copy RoseRT.v7.0.0.1.iFix006.linux.tar.gz to temporary directory
•	Verify Rational Rose RealTime v7.0.0.1_iFix004 is installed, If not installed, upgrade to Rational Rose RealTime v7.0.0.1_iFix004 prior to the installation of Rational Rose RealTime v7.0.0.1_iFix006.
§         run the following command to unzip the patch

gunzip < RoseRT.v7.0.0.1.iFix006.linux.tar.gz | tar xpf -
                  The directory "700906221-8" will be created.
§         cd 700906221-8
§         run "./install_i386_linux2_700906221_8"
This command will back-up the pertinent files in your Release and install the iFix.  You will then have the following options:

      You can later run this install script to restore Rose RealTime 7.0 to its state prior to installing patch:
 
$ROSERT_HOME/install/patches/install_i386_linux2_700906221_8 -restore
 
You can later run this install script to commit patch 700906221-8.  If you do this, you cannot restore later.
$ROSERT_HOME/install/patches/install_i386_linux2_700906221_8 -commit
 
Committing a patch will save disk space by removing the backup files.
Compatibility Issues
This section describes any compatibility issues that could arise from use of this iFix.
Rose RealTime / Rational Product Integrations
Rose RealTime can be integrated with the following Rational products
•	Rational ClearCase v7.1
•	SoDA v7.0.2
•	ReqPro v7.1
•	Purify / Quantify 7.0.0.0 (Solaris)/7.0.0.0 (Windows)
With Third-Party Products
This iFix does not introduce any known compatibility issues with third-party products.
Rose RealTime Petal Format or Code Generation Impacts
This iFix does not impact or include changes to existing Petal Format.
There are some Code Generation changes included, but none of the changes would cause compatibility issues.  The Code Generation changes are listed below.
Component	Problem ID	Description	
Rose RealTime C	IC50696;  RATLC00146713	Excluding a port can corrupt the bindings for the application. 
This could lead to messages arriving on the wrong port and/or causing the application to crash.	
Rose RealTime C	PK00107; RATLC00141383	The rtcgen option –crlf not working correctly.	
Rose RealTime C++	RATLC00564939	Code generated for Insertion and Extraction operators for nested class may not have proper scope resolution for arguments’ data types. This may result in compiler not being able to recognize the correct classes resulting in build failure	
Rose RealTime C++	PK30894;  RATLC00146430 	Removed unnecessary parameters ImplementationPreface and ImplementationEnding for attributes under C++ tab.	
Rose RealTime C++	PK32845; RATLC00498101	Corrected the code generation behavior to correctly scope the nested diagrams	
Rose RealTime TargetRTS Impacts
This iFix includes a fix to copy data to a non-critical section efficiently allowing the mutex to be available for any higher priority thread much more quickly.  
Refer to the document entitled “Rose_RealTime_v7.0.0.1_iFix003_TargetRTS_Changes.htm” for a complete description of the changes.
 
After applying this iFix you will need to re-build your custom TargetRTS libraries.
 
1.	Re-build Connexis using the latest "TargetRTS” libraries. 
2.	Re-build your application using latest "TargetRTS" libraries. 
 
Announcements, Changes and Known Issues
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
 
VxWorks 6.0 Integration
The Rose RealTime / VxWorks 6.0 Integration includes:
 
-         Kernel Mode Integration
-         RTP Mode Integration
 
Vxworks 6.0 Kernel Mode Integration:
 
Includes modified TargetRTS (including C/C++) sources compatible with VxWorks 6.0.
Integration supported on target board with PPC603 CPU and VxWorks 6.0 image.
 
You may deploy any Rose RealTime model on a supported board and run as usual.  (Entry point for Rose RealTime model remains as “rtsMain” method.)
 
IMPORTANT:  In order to run existing models on VxWorks 6.0, it will be necessary to rebuild and link with the libraries supplied with this iFix.  It will be necessary to choose one of the new targets installed with this iFix.
 
The new targets are a combination of:
 
SIMNT (VxWorks 6.0 Simulator)
PPC603 Board (i.e. any target board with MPC8260 or compatible processor)
Diab & GNU Compilers
 
Vxworks 6.0 Real Time Process Mode Integration:
 
Rose Real Time now provides limited support for the Vxworks RealTime Process (RTP) feature. Rose Real Time supports specific Target-RTS configurations in relation to the VxWorks 6.x RTP feature. Please refer to the document README_RoseRT_iFix03_VxWorks_6x_RTP_Integration.rtf for complete details.
 
Known Issues
The Rose RealTime v7.0.0.1 iFix006 installation on Unix/Linux platforms will create two additional files -RTDcsTarget.h and RTTarget.h in $ROSERT_HOME\C++\TargetRTS\target\VxWorks64RTPT\ .
However, users can view the similar files rtdcstarget.h & rttarget.h.

IC37352:  RATLC00516264 - During code generation, the following error message is issued and the code generation stopped:
Error: INTERNAL ERROR: File I/O error while trying to open <path tomodel file>/ScratchPad.rtlogpkg
You may ignore the missing scratchpad files by un-checking the option provided in Tools > Option > File tab >Load
 
IC14929:  RATLC00145010 - It is not possible to Revert an auto merge in Model Integrator.
The Selection Edit > Undo, and Merge > Revert is grayed out.
In the Model Integrator merge mode, expand the hierarchy in the model browser and select myCap > State Machine > Initial > {transition arrow}.
Select body from the property view. Click inside the text view window. Now, the default selection of contributors can be changed
 
PK30274: RATLC00146301: Rose RealTime: Crash E-Mail may include truncated information
Rose RealTime crash reports may become truncated. This problem occurs when the user enters a line with more than 250 characters using wrap-around feature of the shell. The solution is to press <ENTER> between each line without using the wrap-around feature of the terminal.

IC40191:RATLC00520562: Rose RealTime documentation implies that reply() only can be used with synchronous communication
 
reply() can also be used in asynchronous communication. The Receiver doesn't need to know the type of communication. The desired behavior of the Receiver in relation to the reply() message is defined in "C++ Reference -> C++ Services Library -> Communication Services -> Asynchronous and Synchronous Communication".

RATLC01470396: IntegratingData example  model a C++ model is not working in Solaris10

This particular example needs an external library compiled in that particular environment. Recompiling the external library would fix this problem

Status of Change Requests
Problems fixed in v7.0.0.1 iFix006
Component	Problem ID	Description	
Rose RealTime C++	PK32845; RATLC00498101	Corrected the code generation behaviour to correctly scope the nested diagrams	
Rose RealTime Model Integrator	RATLC00571271	Added a new filter in model integrator to enable/disable comparison between quidu(quid references)	
Rose RealTime Toolset	IC43327; RATLC00530357	Corrected the Fit in window operation to ignore blank labels. This was causing the diagram to shrink very low resolution even though the diagram occupies only a fraction of canvas	
Rose RealTime Toolset	IC48469; RATLC00513266	Enabled mouse wheel functionality in the model browser	
Rose RealTime Toolset	IC51392; RATLC01007305	Increased the size of diagrams so that the diagrams would be able to grow beyond 28k pixels	
Rose RealTime Toolset	IC58752; RATLC00570321	Fixed a crash N: :__1cPshPropClipboardSMwGetClipboardInfo6MpnQtagWINDOWSTATION__i_	
Rose RealTime Toolset	PK64770; RATLC00565156	Fixed a defect in retrieving background information from ClearCase when automatic refresh is done on an element. This was causing toolset to ignore the subsequent elements from clearcase refresh	
Rose RealTime Toolset	PK76595; RATLC01369961	Fixed a crash in Rational Rose RealTime while changing text font.	
Rose RealTime Toolset	PK77480; RATLC01243495	Fixed the problem of Going back to top state when the state is empty without providing an error message	
Rose RealTime Toolset	PK77489; RATLC00571315	Fixed a toolset crash when used with Gnome desktop on Unix	
Rose RealTime Toolset	PK78002; RATLC01370614	While checking in RoseRT shows warnings twice for lack of comment	
Rose RealTime Toolset	PK78885; RATLC00571752	Fixed the toolset crash CObject::IsKindOf	
Rose RealTime Toolset	PK79340; RATLC01469331	Fixed sequence diagram Corruption problem in the toolset after a delete and undo operation	
Rose RealTime Toolset	PK80599; RATLC01470027	Fixed a crash in inline editing of signals of a protocol. Toolset used crash after proceeding with “Check out the files and continue with the Edit”.	
Rose RealTime Toolset	PK82400; RATLC00573139	Disallow model-relative pathnames for packages is not working	
Rose RealTime Toolset	PK83104; RATLC00573421	Fixed the RRTEI function AddInstantiateRel() such that it creates Instantiate Relationships	
Rose RealTime Toolset	PK87966; RATLC00574760	When two or more components are selected and right click is pressed for pop-up menu. This operation was resulting in a crash. The problem has been fixed	
Rose RealTime Web Publisher	PK75220; RATLC01241079	Enabled scroll bar in the category frames of the Web Publisher generated HTML files.	
Problems fixed in v7.0.0.1 iFix005
Component	Problem ID	Description	
Rose RealTime C++	PK30894; RATLC00146430 	Removed unnecessary parameters ImplementationPreface and ImplementationEnding for attributes under C++ tab.	
Rose RealTime / ReqPro Integration	IC46782; RATLC00750558 	Erroneous error message regarding ReqPro / Rose RealTime permission issues has been removed.	
Rose RealTime Example	RATLC01365186	Included thread synchronization in CallBack Example Model to run correctly on Windows.	
Rose RealTime TargetRTS	PK19042; RATLC00144221 	Linker script available with Target RTS (rtlink.pl) has been modified to provide correct warnings in relation to compiler return status.	
Rose RealTime Toolset	IC37296; RATLC00510047 	Associations between capsules are not refreshed in the browser after they are deleted from class diagrams.

This type of deletion is now refreshed in the browser.	
Rose RealTime Toolset	IC41600; RATLC00525328 	The link order in the component diagram is not considered in generating the makefiles.

Now, The order in the makefile will be generated based on the model dependencies.	
Rose RealTime Toolset	IC43617; RATLC00530989 	Rendering of ports in structure diagrams have been improved.

When two ports are placed near to each other in the structure diagram, they could incorrectly be drawn as overlapping  ports.

Please refer Additional Information for more information on new functionality.	
Rose RealTime Toolset	IC51066; RATLC00550725 	Rose RealTime C & C++ overriding of derived class cardinality may generate incorrect number of bindings.

If an application contains more than one capsules that share a superclass and differently override cardinality on either end of an inherited connector, Rose RealTime generates the correct number of bindings for the first capsules and stores it in the superclass.  Subsequently, for any other derived capsule the same cardinality will incorrectly be returned.

Number of bindings will now be generated to match the bindings provided in the inheritance hierarchy.	
Rose RealTime Toolset	PK11653; RATLC00143479 	RRTEI add capsule role API will now work correctly and will no longer cause potential model corruption.	
Rose RealTime Toolset	PK16722; RATLC00144038 	RRTEI API implementation has been corrected to activate activity diagram.	
Rose RealTime Toolset	PK74120; RATLC01368232 	Performance improvement when loading Rose RealTime model stored in ClearCase.	
 
Additional Information

§	Overlapping of port Roles (IC43617:RATLC00530989)

New functionality which recalculates the co-ordinates of PortRoles when the diagram is displayed, to avoid overlapping.is enabled only if new the registry entry is set:

"AutoAdjustOverlapPortRoles" – ‘YES'

 To set to “Yes’, Go to Registry Path 

"HKEY_CURRENT_USER\Software\Rational Software\Rose RealTime\6.5"

and set the Registry Entry value "AutoAdjustOverlapPortRoles" to 'YES'.
The original behavior can be restored by setting the above mentioned registry value to 'NO'

•	Rose RealTime does not show warnings/blue deltas correctly(PK19137:RATLC00144232)

The above functionality can be activated by selecting the check box against “Show Blue Delta during Load” under File tab in Tools->Options…

§         AddLogicalPackageDependency RRTEI function call (PK40362 / RATLC00148207)

The prototype of the function AddLogicalPackageDependency is:
 
AddLogicalPackageDependency (theName : String, theSupplierLogicalPackageName : String) : LogicalPackageDependency.

The second argument, theSupplierLogicalPackageName is the name of the supplier package in the dependency relationship. This should be the fully qualified name of the package in the model. You may either specify fully qualified name explicitly or use the RRTEI function GetQualifiedName(). If the supplier package is not found in the model, a script error dialog is presented.
 
The error dialog will be displayed, in the following scenarios:
1)       The supplier package is not in the model under Logical View.
2)       Logical View::supplier_package is not a fully qualified name.
 
In this case, you may correct the script or the model accordingly.
 
§         Improved Data copy During Send Operation and Improved RTDictionary::Find operation (PK32722 / RATLC00993513)
Refer to the document entitled “Rose_RealTime_v7.0.0.1_iFix003_TargetRTS_Changes.htm” for a complete description of the changes.
 
To incorporate these TargetRTS changes
 
1.       After applying the TargetRTS source code changes, build the TargetRTS libraries.
2.       It is necessary to rebuild Connexis using the latest "TargetRTS” libraries.
3.       The application also needs to be rebuilt using latest "TargetRTS" libraries.
 
Note: All Rose RealTime TargetRTS Tornado libraries are provided.  Please, extract only the desired set of libraries ( libObjecTime.a, libObjecTimeTypes.a and main.o ).
 
§         Added Facility to share Path Maps between Rose RealTime instances (PK60016: RATLC01353838)
Create environment variable RRT_PATHMAP pointing to a text file (called pathmap file below) containing key value pairs of path maps. This file will be used for creating path maps for the session.
Format of the pathmap file
The format of the pathmap file would be <key>=<value> in each line (no spaces).
For example:
TARGET_SCRIPTS=/opt/Rational7.0Sol/releases/RoseRT.7.0.0.0/bin/tc/sun5
STEREOTYPES=/opt/Rational7.0Sol/releases/RoseRT.7.0.0.0/stereotypes
Each line in this file will specify one path map entry. 
Details of the changes
A new method to create path maps has been implemented. This is  triggered by RRT_PATHMAP variable. The details are defined in the Method 1. Method 2 explains the existing behavior
1.       Method 1:
a.       If the RRT_PATHMAP variable is present, Rose RealTime will read the path maps from the file and will import these into the Rose RealTime session. 
b.      ROSERT_HOME path map variable will be picked up from the environment variable ROSERT_HOME.(ROSERT_HOME and ROSERT_HOST are required to start toolset) 
c.       The following path maps will be created with default values if they are not defined in the pathmap file, default value is provided in the parentheses.
-         CNX_SCRIPT_PATH ($ROSERT_HOME/Connexis/bin/$ROSERT_HOST)
-         CONNEXIS_HOME ($ROSERT_HOME/Connexis)
-         FRAMEWORK_PATH ($ROSERT_HOME/framework)
-         ROSERT_RTS_HOME ($ROSERT_HOME)
-         SCRIPT_PATH ($ROSERT_HOME/bin/$ROSERT_HOST)
-         STEREOTYPES ($ROSERT_HOME/stereotypes)
-         TARGET_SCRIPTS ($ROSERT_HOME/bin/tc/$ROSERT_HOST)
-         TARGETRTS ($ROSERT_HOME/C++)
d.      Editing path maps should be done by editing the pathmap file, only. The Edit Path Map menu item will be disabled, when using this method. It is possible to add path maps using the RRTEI but it is recommended to move all the path maps created by RRTEI to the pathmap file, so that all the users have access to exactly the same pathmaps.
2.       Method 2: use the existing behavior
a.       If the RRT_PATHMAP variable is not defined in the environment, the path maps will be read from the registry. 
b.      Editing of path maps through Rose RealTime will be allowed, in this case.

Files Changed or Added by this iFix
Files Common to all Platforms (Windows, Solaris & Linux)
$ROSERT_HOME\C++\TargetRTS\codegen\rtcomp.pl
$ROSERT_HOME\Examples\Models\C++\Callbacks\Callbacks.rtmdl
Windows
$ROSERT_HOME\bin\win32\RoseRT.exe
$ROSERT_HOME\bin\win32\RrtRes.dll
$ROSERT_HOME\bin\win32\TraceToolRT.dll
$ROSERT_HOME\bin\win32\rtcppgen.exe
$ROSERT_HOME\bin\win32\rtcgen.exe
$ROSERT_HOME\bin\win32\rtcgen.dll
$ROSERT_HOME\bin\win32\rtcppgen.dll
$ROSERT_HOME\bin\win32\rtjavaui.dll
$ROSERT_HOME\bin\win32\rtrun
$ROSERT_HOME\WebPublisher\win32\rosertwebpub.rsb
$ROSERT_HOME\WebPublisher\win32\librosertwebpub.so 
Solaris
$ROSERT_HOME/bin/RoseRT
$ROSERT_HOME/bin/sun5/RoseRT
$ROSERT_HOME/bin/sun5/RoseRT.rsb
$ROSERT_HOME/bin/sun5/rtcppgen
$ROSERT_HOME/bin/sun5/rtcgen
$ROSERT_HOME/bin/sun5/rtcgen.rsb
$ROSERT_HOME/bin/sun5/rtcppgen.rsb
$ROSERT_HOME/bin/sun5/rtcgen.dll
$ROSERT_HOME/bin/sun5/rtcppgen.dll
$ROSERT_HOME/bin/sun5/rtrun
$ROSERT_HOME/bin/sun5/rtjavaui.rsb
$ROSERT_HOME/bin/sun5/rtjavaui.dll
$ROSERT_HOME/WebPublisher/sun5/rosertwebpub.rsb
$ROSERT_HOME/WebPublisher/sun5/librosertwebpub.so
Linux
$ROSERT_HOME/bin/RoseRT
$ROSERT_HOME/bin/linux/RoseRT
$ROSERT_HOME/bin/linux/RoseRT.rsb
$ROSERT_HOME/bin/linux/rtcppgen
$ROSERT_HOME/bin/linux/rtcgen
$ROSERT_HOME/bin/linux/rtcgen.rsb
$ROSERT_HOME/bin/linux/rtcppgen.rsb
$ROSERT_HOME/bin/linux/rtcgen.dll
$ROSERT_HOME/bin/linux/rtcppgen.dll
$ROSERT_HOME/bin/linux/rtrun
$ROSERT_HOME/bin/linux/rtjavaui.rsb
$ROSERT_HOME/bin/linux/rtjavaui.dll
$ROSERT_HOME/WebPublisher/linux/rosertwebpub.rsb
$ROSERT_HOME/WebPublisher/linux/librosertwebpub.so
$ROSERT_HOME/Help/rose.hlp
$ROSERT_HOME/Help/rose.cnt
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwperl         
$ROSERT_HOME/bin/mw_504/bin-i86_linux/PrintProcInfo  
$ROSERT_HOME/bin/mw_504/bin-i86_linux/gethome        
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwcpp          
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwdeploy       
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwmakedepend   
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwtar          
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwmake         
$ROSERT_HOME/bin/mw_504/bin-i86_linux/mwddd          
$ROSERT_HOME/bin/linux/summit/summittl.rsb           
$ROSERT_HOME/bin/linux/summit/libsummittl.so         
$ROSERT_HOME/bin/linux/summit/pb.rsb                 
$ROSERT_HOME/bin/linux/summit/libpb.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(R), DB2 Universal Database(TM), DDTS(R), Domino(R), IBM, Lotus(R) Notes, MVS(TM), Notes, OS/390(R), Passport Advantage(R), ProjectConsole(TM) Purify(R), Rational, Rational Rose, Rational RoseRealTime, Rational Suite, Rational Unified Process(R), RequisitePro, RUP(R), S/390(R), SoDA, 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.