IBM Rational Rose RealTime
Release Notes
 
Version 7.0.0.1 iFix009
 
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 iFix009
Installing Rose RealTime v7.0.0.1 iFix009
Rose RealTime v7.0.0.1 iFix009 Windows Installation Instructions
Rose RealTime v7.0.0.1 iFix009 Solaris Installation Instructions
Rose RealTime v7.0.0.1 iFix009 Linux Installation Instructions
Compatibility Issues
Rose RealTime / Rational Product Integrations
Rational License Server
With Third-Party Products
Rose RealTime Petal Format or Code Generation Impacts
Rose RealTime TargetRTS Impacts
Announcements, Changes and Known Issues
Rational Federal Desktop Core Configuration (FDCC)/USGCB product support statement:
VxWorks 6.0 Integration
Vxworks 6.0 Kernel Mode Integration:
Vxworks 6.0 Real Time Process Mode Integration:
Support for Windows 7
Support for 64-bit Connexis
Connexis application has been ported to 64-bit and libraries for 64-bit Solaris and Linux are available with this release
Visual Studio 2008 debugger Integration
Known Issues
IC37352:  RATLC00516264 - During code generation, the following error message is issued and the code generation stopped:
IC14929:  RATLC00145010 - It is not possible to Revert an auto merge in Model Integrator.
PK30274: RATLC00146301: Rose RealTime: Crash E-Mail may include truncated information
IC40191:RATLC00520562: Rose RealTime documentation implies that reply() only can be used with synchronous communication
RATLC01470396: IntegratingData example  model a C++ model is not working in Solaris10
RATLC01474788:RoseRT model fail to Run with Purecov (Target Configuration 'SOLARIS10SPARC64T.sparc64-gnu-3.4.6')
Status of Change Requests
Problems fixed in v7.0.0.1 iFix009
Problems fixed in v7.0.0.1 iFix008
Additional Information
Format of the pathmap file
Details of the changes
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 iFix009 Release Note is in addition to the Release Note for Rose RealTime v7.0.0.1 and Release Note for Rose RealTime v7.0.0.1_iFix007
Copyright International Business Machines Corporation 1999, 2011. 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 iFix009
This chapter describes updates to the documentation that pertain to installing Rational Rose RealTime v7.0.0.1 iFix009.
System and software requirements
This iFix supports the following Operating Systems:
•	Microsoft Windows 2000 Professional SP4; XP Professional with SP3, Vista Enterprise SP1, Windows 7 Professional, Enterprise and Ultimate
•	Red Hat Linux v8.0, 9.0, Enterprise Linux 3 & 4, Suse Linux Enterprise Desktop v10(32 bit and 64 bit)
•	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.3915.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 iFix009
This section describes installing Rational Rose RealTime Version 7.0.0.1 iFix009.
Note 1: Rose RealTime v7.0.0.1 iFix007 must be installed before installing Rose RealTime iFix009.It can be downloaded from http://www-01.ibm.com/support/docview.wss?uid=swg24024803
Note 2: Before installing the Rose RealTime v7.0.0.1 iFix009 on Windows/Unix/Linux, 2 directories need to be renamed as below
1. $ROSERT_HOMEC++\TargetRTS\src\target\VxWorks64RTP\RTInet to $ROSERT_HOMEC++\TargetRTS\src\target\VxWorks64RTP\RTinet
2. $ROSERT_HOMEC++\TargetRTS\src\target\VxWorks64RTP\RTTimeSpec to $ROSERT_HOMEC++\TargetRTS\src\target\VxWorks64RTP\RTTimespec

Rose RealTime v7.0.0.1 iFix009 Windows Installation Instructions
•	Verify Rational Rose RealTime v7.0.0.1_iFix007 is installed by running Start > Programs > IBM Rational > Rational Software Installed Product Information.
o	If Rose RealTime v7.0.0.1 iFix007 is installed you will see IBM Rational Rose RealTime Version Build ID 7.0.0.1- IFIX07.
•	Download the iFix009 Release specific to your  language(i.e. OS 7.0.0.1-RATL-RRRT-WIN-en-US-IFIX09.msp or 7.0.0.1-RATL-RRRT-WIN-ja-JP-IFIX09.msp)
•	Once downloaded double-click on the 7.0.0.1-RATL-RRRT-WIN-en-US-IFIX09.msp or 7.0.0.1-RATL-RRRT-WIN-ja-JP-IFIX09.msp file to begin the installation.
•	Press Update
•	Press Next
•	Press Install
•	Installation Complete
•	Verify Rational Rose RealTime v7.0.0.1 iFix009 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-IFIX09
Rose RealTime v7.0.0.1 iFix009 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.iFix009.sun5.tar.gz to temporary directory
•	Verify Rational Rose RealTime v7.0.0.1_iFix007 is installed, if not installed, upgrade to Rational Rose RealTime v7.0.0.1_iFix007 prior to the installation of Rational Rose RealTime v7.0.0.1_iFix009.
•	Once it has been determined iFix007 is installed, run the following command to unzip the patch

    gunzip < RoseRT.v7.0.0.1.iFix009.sun5.tar.gz | tar xpf -
          The directory "701102041-1" will be created.
•	cd 701102041-1
•	run "./install_sol_701102041_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_701102041_1 -restore
 
You can later run this install script to commit patch 701102041-1.  If you do this, you cannot restore later.
$ROSERT_HOME/install/patches/install_sol_701102041_1 -commit
 
Committing a patch will save disk space by removing the backup files.
 
Rose RealTime v7.0.0.1 iFix009 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.iFix009.linux.tar.gz to temporary directory
•	Verify Rational Rose RealTime v7.0.0.1_iFix007 is installed, If not installed, upgrade to Rational Rose RealTime v7.0.0.1_iFix007 prior to the installation of Rational Rose RealTime v7.0.0.1_iFix009.
•	Once it has been determined iFix007 is installed, run the following command to unzip the patch

          gunzip < RoseRT.v7.0.0.1.iFix009.linux.tar.gz | tar xpf -
                The directory "701102042-8" will be created.
•	cd 701102042-8
•	run "./install_i386_linux2_701102042_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_701102042_8 -restore
 
You can later run this install script to commit patch 701102042-8.  If you do this, you cannot restore later.
$ROSERT_HOME/install/patches/install_i386_linux2_701102042_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.2
•	SoDA v7.0.4
•	ReqPro v7.1.2
•	Purify / Quantify 7.0.0.0 (Solaris)/7.0.0.0 (Windows)
Rational License Server
The licensing components built into the Toolset have been upgraded to resolve the RATLC00572518. FlexLM license servers older than version 10.8 may not be compatible. Please upgrade to FlexLM version 10.8 or above 
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++	PK32845; RATLC00498101	Corrected the code generation behavior to correctly scope the nested diagrams	
Rose RealTime Codegen	PM25329	Extended APAR PK60016 to Codegen also. This enables sharing of pathmaps using a file between users.
For more details please go to Additional Information section	
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)/The United States Government Configuration Baseline (USGCB) 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.

Support for Windows 7
Rose RealTime now provides support for Microsoft Windows 7 for the following in 32-bit and 64-bit variants (Note: Rose RealTime application is not ported to 64 bit)
•	Microsoft Windows 7 Professional
•	Microsoft Windows 7 Enterprise
•	Microsoft Windows 7 Ultimate
Support for 64-bit Connexis
Connexis application has been ported to 64-bit and libraries for 64-bit Solaris and Linux are available with this release
Visual Studio 2008 debugger Integration
RoseRT-iFix008 will be supporting Microsoft Visual Studio 2008. Users can debug RoseRT Model and also TargetRTS in Visual Studio 2008 using Debugger-VS2008 in operation mode. User has to reconfigure component, target settings and editing the TargetRTS settings to debug the models in VS2008. 

To debug the model in VS2008, the following settings need to be done for Model Component and Target
Component specification settings for VS2008 debug
Under the C++ Compilation tab
CompileArguments:    /ZI
Under C++ Executable Tab
LinkArguments: /DEBUG
Processor Component Instance Specification settings under Detail tab
	1. Operation mode: Debugger-VS_2008

Editing TargetRTS settings for VS2008 debug
Set the Extra Compiler Flags (LIBSETCCEXTRA) to /ZI by editing the duplicated Target. 
Find the information for duplicating Editing Target in RoseRT online help (Add-Ins, Tools, and Wizards-> Rational Rose RealTime Wizards-> TargetRTS Wizard)

Known Issues
The Rose RealTime v7.0.0.1 iFix008 installation on Unix/Linux platforms will create the following additional files RTDebuggerInput\nextChar.cc, RTMain\installHandlers.cc, RTMain\installOneHandler.cc, RTMain\targetStartup.cc, RTstdio.h, RTtcp.h in $ROSERT_HOMEC++\TargetRTS\src\target\VxWorks64RTP\
However, users can view the similar files RTDebuggerInput\nextchar.cc, RTMain\installhandlers.cc, RTMain\installonehandler.cc, RTMain\targetstartup.cc, RTStdio.h RTTcp.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 to model 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
RATLC01474788:RoseRT model fail to Run with Purecov (Target Configuration 'SOLARIS10SPARC64T.sparc64-gnu-3.4.6')

Status of Change Requests
Problems fixed in v7.0.0.1 iFix009
Component	Problem ID	Description	
Rose_RT_Codegen	PM25329	Extended APAR PK60016 to Codegen also. This enables sharing of pathmaps using a file between users.
For more details please go to Additional Information section	
Rose_RT_Connexis	PM28524	Resolved a defect in Connexis where a Mutex is getting referenced after it has been deleted	
Rose_RT_Connexis	RATLC01371571	Added 64 bit support for Connexis on Linux	
Rose_RT_Connexis	RATLC01533671	Added 64 bit support for Connexis on Solaris	
Rose_RT_CORBA	PM02561	Modified the CORBA sequence generation for multiplicity 0..1	
Rose_RT_TargetRTS	RATLC00576546	Added a new Target for mingw-3.4.5 tool chain	
Rose_RT_Toolset	RATLC00523466	Users are unable to identify the filenames of External Docs from the browser if the there are very long paths. 
To resolve this we implemented a feature to display only the file without the complete path. This can be enabled by selecting Tools -> Options -> Browser Tab. select Show Short names for External Docs	
Rose_RT_Toolset	RATLC00523797	Corrected the error message while running the check_rose_req script	
Rose_RT_Toolset	RATLC00577647	Added support for Window 7	
 
Problems fixed in v7.0.0.1 iFix008
Component	Problem ID	Description	
Rose_RT_Connexis	PK97930	Call to the function RTProtocol::deregisterSPP() for deregistering the service, is causes the  DCS thread to hang.	
Rose_RT_Toolset	PK93978	Provided the fix for reducing the crashes from RoseRT	
Rose_RT_Toolset	PK97617	Added substring search feature. Provided a check box option for user to select substring search	
Rose_RT_Toolset	PK99173	Provided the fix so that Rose RealTime will have right context while opening the specification dialogue box for signals and ports.	
Rose_RT_Toolset	PM06977	Provided the fix to create and use the activity which is supplied by the user during the checkout.	
 
Additional Information	
•	Overlapping of port Roles (IC43617)

New functionality which recalculates the co-ordinates of PortRoles when the diagram is displayed, to avoid overlapping, this feature 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)

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)

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)
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)
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/config/NT40MinGwT.x86-MinGw-gnu-3.4.5/config.mk
$ROSERT_HOME/C/TargetRTS/config/NT40MinGwT.x86-MinGw-gnu-3.4.5/setup.pl
$ROSERT_HOME/C/TargetRTS/lib/NT40MinGwT.x86-MinGw-gnu-3.4.5/libObjecTimeC.a
$ROSERT_HOME/C/TargetRTS/lib/NT40MinGwT.x86-MinGw-gnu-3.4.5/libObjecTimeCTransport.a
$ROSERT_HOME/C/TargetRTS/lib/NT40MinGwT.x86-MinGw-gnu-3.4.5/main.o
$ROSERT_HOME/C/TargetRTS/libset/x86-MinGw-gnu-3.4.5/libset.mk
$ROSERT_HOME/C/TargetRTS/src/target/NT40MinGw/MAIN/main.cc
$ROSERT_HOME/C/TargetRTS/target/NT40MinGwT/RTTarget.h
$ROSERT_HOME/C/TargetRTS/target/NT40MinGwT/target.mk
$ROSERT_HOME/C++/TargetRTS/config/NT40MinGwT.x86-MinGw-gnu-3.4.5/config.mk
$ROSERT_HOME/C++/TargetRTS/config/NT40MinGwT.x86-MinGw-gnu-3.4.5/setup.pl
$ROSERT_HOME/C++/TargetRTS/include/RTTimespec.inl
$ROSERT_HOME/C++/TargetRTS/lib/CHORUS40T.ppc603-egcs-2.91.66/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/CHORUS40T.ppc603-egcs-2.91.66/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/CHORUS40T.ppc603-egcs-2.91.66/main.o
$ROSERT_HOME/C++/TargetRTS/lib/LYNX30T.ppc-cygnus-2.7-97r1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/LYNX30T.ppc-cygnus-2.7-97r1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/LYNX30T.ppc-cygnus-2.7-97r1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/LYNX30T.x86-cygnus-2.7-97r1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/LYNX30T.x86-cygnus-2.7-97r1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/LYNX30T.x86-cygnus-2.7-97r1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/LYNX31T.ppc-gnupro-2.9-98r2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/LYNX31T.ppc-gnupro-2.9-98r2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/LYNX31T.ppc-gnupro-2.9-98r2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/lib/NT40CygwinT.x86-cygwin-gnu-3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/NT40CygwinT.x86-cygwin-gnu-3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/NT40CygwinT.x86-cygwin-gnu-3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/NT40CygwinT.x86-cygwin-gnu-3.4.4-3/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/NT40CygwinT.x86-cygwin-gnu-3.4.4-3/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/NT40CygwinT.x86-cygwin-gnu-3.4.4-3/main.o
$ROSERT_HOME/C++/TargetRTS/lib/NT40MinGwT.x86-MinGw-gnu-3.4.5/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/NT40MinGwT.x86-MinGw-gnu-3.4.5/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/NT40MinGwT.x86-MinGw-gnu-3.4.5/main.o
$ROSERT_HOME/C++/TargetRTS/lib/NT40MT.x86-VisualC++-6.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NT40MT.x86-VisualC++-6.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NT40MT.x86-VisualC++-6.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/lib/NT40T.x86-VisualC++-6.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NT40T.x86-VisualC++-6.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NT40T.x86-VisualC++-6.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/lib/NT40T.x86-VisualC++-7.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NT40T.x86-VisualC++-7.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NT40T.x86-VisualC++-7.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/lib/NUCLEUS11T.x86-VisualC++-6.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NUCLEUS11T.x86-VisualC++-6.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/NUCLEUS11T.x86-VisualC++-6.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/main.o
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73MT.x86-gnu-3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73MT.x86-gnu-3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73MT.x86-gnu-3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73MT.x86-gnu-3.2/ObjecTime.lib
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73MT.x86-gnu-3.2/ObjecTimeTypes.lib
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73T.x86-gnu-3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73T.x86-gnu-3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73T.x86-gnu-3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT80MT.x86-gnu-3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT80MT.x86-gnu-3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT80MT.x86-gnu-3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SLED10T.x86-gnu-4.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SLED10T.x86-gnu-4.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SLED10T.x86-gnu-4.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SLED10x64T.x64-gnu-4.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SLED10x64T.x64-gnu-4.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SLED10x64T.x64-gnu-4.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SOLARIS10T.sparc-gnu-3.4.6/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SOLARIS10T.sparc-gnu-3.4.6/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SOLARIS10T.sparc-gnu-3.4.6/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SUN5MT.sparc-SunC++-5.0/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5MT.sparc-SunC++-5.0/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5MT.sparc-SunC++-5.0/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.95.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.95.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.95.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-3.0.4/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-3.0.4/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-gnu-3.0.4/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.0/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.0/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.0/main.o
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.3/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.3/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.3/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.simpc-egcs-2.90.29/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.simpc-egcs-2.90.29/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.simpc-egcs-2.90.29/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.simso-cygnus-2.7.2-960126/main.o
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.ppc603-Diab-5.2.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.ppc603-Diab-5.2.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.ppc603-Diab-5.2.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.ppc603-gnu-3.3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.ppc603-gnu-3.3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.ppc603-gnu-3.3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.simnt-Diab-5.2.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.simnt-Diab-5.2.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.simnt-Diab-5.2.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.simnt-gnu-3.3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.simnt-gnu-3.3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.simnt-gnu-3.3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.ppc603-Diab-5.5.0-RTP/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.ppc603-Diab-5.5.0-RTP/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.ppc603-Diab-5.5.0-RTP/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.ppc603-gnu-3.4.4-RTP/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.ppc603-gnu-3.4.4-RTP/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.ppc603-gnu-3.4.4-RTP/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.simnt-Diab-5.5.0-RTP/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.simnt-Diab-5.5.0-RTP/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.simnt-Diab-5.5.0-RTP/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.simnt-gnu-3.4.4-RTP/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.simnt-gnu-3.4.4-RTP/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks64RTPT.simnt-gnu-3.4.4-RTP/main.o
$ROSERT_HOME/C++/TargetRTS/lib/WINCE300T.sh3-eMVisualC++-3.0/libObjecTime.LIB
$ROSERT_HOME/C++/TargetRTS/lib/WINCE300T.sh3-eMVisualC++-3.0/libObjecTimeTypes.LIB
$ROSERT_HOME/C++/TargetRTS/lib/WINCE300T.sh3-eMVisualC++-3.0/main.OBJ
$ROSERT_HOME/C++/TargetRTS/libset/x86-MinGw-gnu-3.4.5/libset.mk
$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/deregisterSAP.cc
$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/deregisterSPP.cc
$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/registerSAP.cc
$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/registerSPP.cc
$ROSERT_HOME/C++/TargetRTS/src/target/NT40MinGw/MAIN/main.cc
$ROSERT_HOME/C++/TargetRTS/src/target/VxWorks64RTP/RTDebuggerInput/nextChar.cc
$ROSERT_HOME/C++/TargetRTS/src/target/VxWorks64RTP/RTMain/installHandlers.cc
$ROSERT_HOME/C++/TargetRTS/src/target/VxWorks64RTP/RTMain/installOneHandler.cc
$ROSERT_HOME/C++/TargetRTS/src/target/VxWorks64RTP/RTMain/targetStartup.cc
$ROSERT_HOME/C++/TargetRTS/src/target/VxWorks64RTP/RTstdio.h
$ROSERT_HOME/C++/TargetRTS/src/target/VxWorks64RTP/RTtcp.h
$ROSERT_HOME/C++/TargetRTS/target/NT40MinGwT/RTTarget.h
$ROSERT_HOME/C++/TargetRTS/target/NT40MinGwT/target.mk
$ROSERT_HOME/Connexis/C++/lib/LYNX30T.ppc-cygnus-2.7-97r1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/LYNX30T.x86-cygnus-2.7-97r1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/OSE411T.sparc-gnu-2.95.1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/REDHAT73MT.x86-gnu-3.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/REDHAT73T.x86-gnu-3.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/REDHAT80T.x86-gnu-3.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SLED10T.x86-gnu-4.1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SLED10x64T.x64-gnu-4.1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SOLARIS10SPARC64T.sparc64-gnu-3.4.6/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SOLARIS10T.sparc-gnu-3.4.6/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SUN5MT.sparc-SunC++-5.0/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SUN5T.sparc-gnu-2.8.1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SUN5T.sparc-gnu-2.95.1/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/SUN5T.sparc-SunC++-5.0/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VXWorks60T.ppc603-Diab-5.2.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VxWorks60T.ppc603-gnu-3.3.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VXWorks60T.simnt-Diab-5.2.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VxWorks60T.simnt-gnu-3.3.2/libDCS.a
$ROSERT_HOME/Connexis/Model/DCS.rtmdl
$ROSERT_HOME/Examples/Models/C++/ExternalAPI/externalCPPUsingGlobalandThread.rtmdl
$ROSERT_HOME/RTJava/classes.jar
$ROSERT_HOME/RTJava/TargetRTS/ComponentView/rosert/classes.rtcmp
$ROSERT_HOME/RTJava/TargetRTS/ComponentView/rosert/normal.rtcmp
$ROSERT_HOME/RTJava/TargetRTS/ComponentView/rosert/special.rtcmp
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert.rtlogpkg
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Capsule.rtclass
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Controller.rtclass
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Diagrams.rtlogpkg
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/ProtocolRole.rtclass
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Special.rtlogpkg
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Special/Capsule.rtclass
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Special/Frame.rtclass
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Special/Log.rtclass
$ROSERT_HOME/RTJava/TargetRTS/LogicalView/com/rational/rosert/Special/Timing.rtclass
Windows
$ROSERT_HOME/bin/win32/libVS_2008.dll
$ROSERT_HOME/bin/win32/RoseRT.exe
$ROSERT_HOME/bin/win32/RrtRes.dll
$ROSERT_HOME/bin/win32/rtcbld.dll
$ROSERT_HOME/bin/win32/rtcgen.exe
$ROSERT_HOME/bin/win32/rtcppbld.dll
$ROSERT_HOME/bin/win32/rtcppgen.exe
$ROSERT_HOME/bin/win32/rtjavagen.exe
$ROSERT_HOME/bin/win32/rtjavaui.dll
$ROSERT_HOME/bin/win32/rtrun.exe
$ROSERT_HOME/Connexis/bin/win32/Connexis.dll
$ROSERT_HOME/Connexis/bin/win32/ConnexisRES.dll
$ROSERT_HOME/Connexis/bin/win32/ConnexisViewer.exe
$ROSERT_HOME/Connexis/bin/win32/ConnexisViewerRES.dll
$ROSERT_HOME/Connexis/bin/win32/TraceData.dll
$ROSERT_HOME/CORBA/corbart_addin.dll
$ROSERT_HOME/CORBA/corbart_addinres.dll
$ROSERT_HOME/WebPublisher/win32/rosertwebpub.dll
$ROSERT_HOME/WebPublisher/win32/rosertwebpubres.dll
$ROSERT_HOME/bin/win32/cmscripts/cc/cm_getcaps
$ROSERT_HOME/Connexis/C++/lib/NT40T.x86-VisualC++-6.0/DCS.LIB
$ROSERT_HOME/Connexis/C++/lib/TORNADO2T.simpc-egcs-2.90.29/libDCS.a
Solaris
$ROSERT_HOME/bin/mw_504/bin-sunos5_optimized/mwcleanup
$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_getcaps
$ROSERT_HOME/bin/sun5/RoseRT
$ROSERT_HOME/bin/sun5/RoseRT.rsb
$ROSERT_HOME/bin/sun5/rtcbld.dll
$ROSERT_HOME/bin/sun5/rtcbld.rsb
$ROSERT_HOME/bin/sun5/rtcgen
$ROSERT_HOME/bin/sun5/rtcppbld.dll
$ROSERT_HOME/bin/sun5/rtcppbld.rsb
$ROSERT_HOME/bin/sun5/rtcppgen
$ROSERT_HOME/bin/sun5/rtjavagen
$ROSERT_HOME/bin/sun5/rtjavaui.dll
$ROSERT_HOME/bin/sun5/rtjavaui.rsb
$ROSERT_HOME/bin/sun5/rtrun
$ROSERT_HOME/CORBA/sun5/corbart_addin.rsb
$ROSERT_HOME/CORBA/sun5/libcorbart_addin.so
$ROSERT_HOME/WebPublisher/sun5/librosertwebpub.so
$ROSERT_HOME/WebPublisher/sun5/rosertwebpub.rsb
$ROSERT_HOME/Connexis/bin/sun5/connexis.rsb
$ROSERT_HOME/Connexis/bin/sun5/ConnexisViewer
$ROSERT_HOME/Connexis/bin/sun5/ConnexisViewer.rsb
$ROSERT_HOME/Connexis/bin/sun5/libconnexis.so
$ROSERT_HOME/Connexis/bin/sun5/libTraceData.so
$ROSERT_HOME/bin/check_rose_reqs
$ROSERT_HOME/bin/registry/c.reg
$ROSERT_HOME/bin/registry/connexis.reg
$ROSERT_HOME/bin/registry/corba.reg
$ROSERT_HOME/bin/registry/cpp.reg
$ROSERT_HOME/bin/registry/EclipseIntegration.reg
$ROSERT_HOME/bin/registry/RTJava.reg
$ROSERT_HOME/bin/registry/webpub.reg
$ROSERT_HOME/bin/RoseRT
$ROSERT_HOME/C++/TargetRTS/include/RTVersion.h
Linux
$ROSERT_HOME/bin/mw_504/bin-linux_optimized/mwcleanup
$ROSERT_HOME/bin/linux/cmscripts/cc/cm_getcaps
$ROSERT_HOME/bin/linux/RoseRT
$ROSERT_HOME/bin/linux/RoseRT.rsb
$ROSERT_HOME/bin/linux/rtcbld.dll
$ROSERT_HOME/bin/linux/rtcbld.rsb
$ROSERT_HOME/bin/linux/rtcgen
$ROSERT_HOME/bin/linux/rtcppbld.dll
$ROSERT_HOME/bin/linux/rtcppbld.rsb
$ROSERT_HOME/bin/linux/rtcppgen
$ROSERT_HOME/bin/linux/rtjavagen
$ROSERT_HOME/bin/linux/rtjavaui.dll
$ROSERT_HOME/bin/linux/rtjavaui.rsb
$ROSERT_HOME/bin/linux/rtrun
$ROSERT_HOME/CORBA/linux/corbart_addin.rsb
$ROSERT_HOME/CORBA/linux/libcorbart_addin.so
$ROSERT_HOME/WebPublisher/linux/librosertwebpub.so
$ROSERT_HOME/WebPublisher/linux/rosertwebpub.rsb
$ROSERT_HOME/Connexis/bin/linux/connexis.rsb
$ROSERT_HOME/Connexis/bin/linux/ConnexisViewer
$ROSERT_HOME/Connexis/bin/linux/ConnexisViewer.rsb
$ROSERT_HOME/Connexis/bin/linux/libconnexis.so
$ROSERT_HOME/Connexis/bin/linux/libTraceData.so
$ROSERT_HOME/bin/check_rose_reqs
$ROSERT_HOME/bin/registry/c.reg
$ROSERT_HOME/bin/registry/connexis.reg
$ROSERT_HOME/bin/registry/corba.reg
$ROSERT_HOME/bin/registry/cpp.reg
$ROSERT_HOME/bin/registry/EclipseIntegration.reg
$ROSERT_HOME/bin/registry/RTJava.reg
$ROSERT_HOME/bin/registry/webpub.reg
$ROSERT_HOME/bin/RoseRT
$ROSERT_HOME/C++/TargetRTS/include/RTVersion.h

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.