Version 2003.06.13
Release Date: September 2004
Last Updated: 09/24/2004
© Copyright IBM Corporation. 1999, 2004. All Rights Reserved.
Any reproduction or distribution of this work is expressly prohibited without the prior written consent of IBM Corporation.
This patch is for Solaris configurations only, and it includes Enhancements, Changes and Fixes for Defects (see Defects Fixed in This Release).
The Patch Release Notes includes:
Verify that there is a valid version of Rational Rose RealTime v2003.06.00 installed and ensure that file and directory permissions allow writing to the files listed in Files Included in this Patch. If you encounter problems during the unzip process regarding read-only files, change the permissions on the file system for all files under <ROSERT_HOME>C/TargetRTS and <ROSERT_HOME>C++/TargetRTS.
If you installed Rational Rose RealTime using a Network or Administrative installation, the patch applies to the server computer only. Contact your administrator to install this patch.
Note: Some Windows virus checking software will warn you about gzip type files (with a .gz extension). This warning can be safely ignored. There should be no viruses reported during the extraction of the patch files when using WinZip.
You do not need to install the GA-01, GA-02, GA-03 or GA-04 patch before installing this patch.
To install the Rational Rose RealTime 2003.06.13 (aka GA-05) patch:
Ensure there is no running instance of Rational Rose RealTime on the computer you want to update. Copy the appropriate compressed files for your platform to your <ROSERT_HOME> directory. For Solaris: Copy SR3.sun5.827.tar.gz, then run the following commands:
cd $ROSERT_HOME gunzip < SR3.sun5.827.tar.gz | tar xpf -
For Linux: Copy SR3.sun5.827.tar.gz, then run the following commands:
cd $ROSERT_HOME gunzip < SR3.sun5.827.tar.gz| tar xpf -
Note: By default, the extraction path is C:\Program Files\Rational\Rose RealTime. If your <ROSERT_HOME> location is different from the default path, prior to extraction, change the path specified in the Unzip to folder path box appropriately.
The accompanying .gz files from the Service Release are no longer required. However, if you want to retain these files if a re-installation is required, you can move the tar files to <ROSERT_HOME>/specials.
For additional information on issues with Rational Rose RealTime (prior to v2003.06.13), see the chapter, "General Issues" in the Addendum, Rational Rose RealTime located in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf.
For help on the new and modified information included in this Service Release, see the Rose RealTime Release Notes, located in <ROSERT_HOME>/rosert_readme.html.
Run the toolset and ensure that the build 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.5.827.0. If the build number is not the same, this Service Release was not applied correctly.
Note: If you wish to take advantage of the problems fixed in the code generators, you need to rebuild and re-link your models.
Note: If you wish to take advantage of the problems fixed in RQA-RT, you need to rebuild your RQA-RT Test Runs.
Note: If you wish to take advantage of the problems fixed in the RTJava Models, you need to rebuild your Java models.
No additional steps are required.
Note: 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.
Note: If you wish to take advantage of the problems fixed in the code generators, you need to rebuild and re-link your models.
Note: If you wish to take advantage of the problems fixed in the DCS, you need to rebuild and re-link your models.
It will be necessary for you to rebuild any of the following Targets you require from this Patch. If the Target you require is not shown in the list below, it has already been rebuilt and included in the Patch.
C++ Targets | C Targets | Connexis Targets (Released in 2003.06.12) |
NUCLEUS11T.ppc860-Diab-4.2b | OSE411T.ppc603-Green-1.8.9 | OSE411T.ppc603-Green-1.8.9.SUN5 |
OSE411T.ppc603-Green-1.8.9 | OSE411T.ppc603-Green-2.0 | TORNADO2T.ppc603-GreenVX-1.8.9.SUN5 |
OSE411T.ppc603-Green-2.0 | TORNADO2T.ppc603-GreenVX-2.0.SUN5 | |
PSOS25T.ppc603-Diab-4.2b | PSOS25T.ppc603-Diab-4.2b.SUN5 | |
PSOS25T.ppc860-Diab-4.2b | PSOS25T.ppc860-Diab-4.2b.SUN5 | |
QNX4S.x86-WC++-10.6 | UNIXWARE701T.x86-SDK-3.0.UXW7 | |
SUN5T.sparc-gnu-3.0.4 | ||
TORNADO2T.ppc603-GreenVX-1.8.9 | ||
TORNADO2T.ppc603-GreenVX-2.0 |
For additional information on licensing, see You Must Install License Keys to Run this Product.
For additional information on compatibility issues, see the Product Support section of the Rational Rose RealTime web site at:
http://www.ibm.com/software/rational/support/
For the most recent documentation updates, visit the Product Support section of the Rational Rose RealTime web site at:
http://www.ibm.com/software/rational/support/
Where printed documentation exists, always refer to the online Help or PDF versions of the book for the latest updates.
RATLC00246172 / IC41967 | Analysis RRTEI Collection classes will not work correctly with out-of-proc calls. |
RATLC00515540 / IC39587 | Attempting to select "Zoom > Fit In Window" from the diagram window or selecting "Fit to page" in Print dialog and then selecting "Print Preview" for a activity chart (i.e. 8 DIN A4 pages), may cause Rose RealTime to crash. |
RATLC00515542 / IC37530 | Rose RealTime Web Publisher may not publish Activity Diagrams correctly. |
RATLC00516159 / IC41774 | The
RRTEI functions componet.AddInclusionPath and component.AddUserLibrary
do not function as expected. Both functions return true which
indicates that the inclusion / userlibrary has been created although it
has not been. Workaround: Locate the property in the RRTEI associated with the data to be updated (i.e. "inclusion path") and override the value. |
RATLC00516276 / IC37365 | Upon adding a new Port to a CapsuleStructure there are no warnings or errors shown when a Port with the same name already exists. When this occurs the model will become inconsistent. In addition, when loading a model with this issue warnings are shown indicating that duplicate Ports need to be renamed. However, the StructureDiagram shows multiple PortViews per Port. |
RATLC00517294 / IC38263 | All RRTEI Relocate Methods should return Boolean values, as indicated in Online Help. Some of the methods that currently do not return Boolean values are "RelocateClass", "RelocateLogicalPackage" and "RelocateClassDiagram". The methods "RelocateCapsule", "RelocateProtocol" and "RelocateCollaboration" currently do return Boolean values correctly. |
RATLC00517805 / IC38611 | Incorrect components are offered as a choice when attempting to Browser Header / Browse Brody. You must verify which class the component is associated with to determine which component to select. If you select the wrong component, you will encounter an error. |
RATLC00518863 / IC39179 | Rose
RealTime Model Integrator will not generate QUID for junction point views
upon merging in models created with Rose RealTime 2002. The
following steps, illustrate this behavior:
Rose RealTime 2002 does not generate QUID for junction point views after the first save. |
RATLC00520561 / IC40188 | Unable to rename a package using some Chinese characters when running Rose RealTime on Simplified Chinese or on English Windows with the system default locale set to Simplified Chinese. |
RATLC00521864 / IC40612 | The
following error message can occur when attempting to open a Rose RealTime
model through a workspace using a ClearCase Snapshot view:
Error: Could not run script to get source control capabilities: The shell command ""C:\Progra~1\Rational\RoseRe~1\bin\win32\rtperl" -w "C:\Program Files\Rational\Rose RealTime\bin\win32\cmscripts\cc\cm_getcaps"" did not terminate in the specified timeout.. Workaround: Open the *.rtmdl file and turn on SourceControl after the model is loaded. |
RATLC00522023 / IC40673 | The
Rose RealTime C TargetRTS Build flat option does not include header
files from $ROSERT_HOME/C/TargetRTS/build-<your config>.
Workaround: Add the following line to your config.mk file: TARGETCCFLAGS = $(INCLUDE_TAG)"$(RTS_HOME)/build-$(TARGET).$(LIBRARY_SET) " |
RATLC00522046 / IC40673 | Rose
RealTime C TargetRTS build flat option does not copy RSL.h and
UMLRT.h to the build-<your config>/RTPubl directory.
When building the Rose RealTime C TargetRTS flat, Rose RealTime regenerates the TargetRTS header files in the directory $ROSERT_HOME/C/TargetRTS/build-<your config>. All the #include <...> have been changed to #include "...". Unfortunately, two header files in $ROSERT_HOME/C/TargetRTS/include/RTPubl are not regenerated (RSL.h and UMLRT.h). Workarounds: Modifying RSL.h and UMLRT.h and placing them in libset/<your_libset>/RTPubl or changing the two files in include/RTPubl to use #include "...". |
RATLC00522099 / IC41974 | Rose RealTime C TargetRTS RTPubl/CapClass.h: struct _RTCapsule_class should be rearranged to remove padding inserted for alignment. |
RATLC00523150 / IC41231 | In Rose RealTime CPP, making a change to a large source file and subsequently requesting a codesync may cause Rose RealTime to hang. |
RATLC00524571 / IC41470 | Connexis
enabled application may cause exception when deregistering SPPs on
shutdown.
Workaround:
|
RATLC00525237 / IC41575 | Using Rose RealTime C, Timer_data_union doesn't compile when RTMESSAGE_PAYLOAD_SIZE=0. |
RATLC00525328 / IC41600 | Rose
RealTime link errors may occur due to the fact that the link order is
determined by the order that the dependencies were added to the packages.
Prior to Rose RealTime 2003, the order was based on the order of the
dependencies added. Those added first were linked first. In
Rose RealTime 2003 the reverse order is applied, which may cause link
failures.
|
RATLC00526499 / IC42118 | Connexis
CRM connection not re-established in certain situations.
|
Documentation for IBM Rational is available on-line at http://www.ibm.com/software/rational/support/documentation/.
Additional information about this release is available in the Addendum, Rational Rose RealTime, located in <ROSERT_HOME>/Help/rosert_addendum_2003.pdf.
Note: It is only necessary to utilize this enhancement if you are encountering slow performance when attempting to display the Sequence Diagram Role List.
A new option has been included in the Rose RealTime Tools > Options dialog, which can significantly enhance performance when attempting to display a large role list. A new check-box option "Sequence diagram role list size" is added to the "Picklists" section of the Options dialog. By default, the check-box is unchecked and there is no limit to the size of the role list to be displayed (role list size < 0 also produces default behavior).
Checking the "Sequence diagram role list size" will allow you to enter a threshold value of the maximum role list size. Adding a new interaction instance which causes the role list to exceed the set threshold value, will produce the following results which ultimately improves the role list display performance.
- Role list efficiently displays and scroll bar of the list becomes inactive.
- You may traverse the list, using the Up and Down arrows, Page Up / Page Down, Home / End to move to the starting / end of the list, or enter the starting letter of the role name.
Previously, upon clicking on the operations dropdown list of the Specification dialog of a Call Message, the operations listed would only include the public operations of the receiver class. This has been enhanced when using RTJava.
Now, the operations dropdown list of the Call message Specification dialog will display operations of the receiver class, as described below.
A new registry string value "OpsVisibility" under the registry key "HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose RealTime\6.5" will determine the method visibility behavior (per user basis) in Sequence diagrams.
- If OpsVisibility="2", the operations list will display all operations. The list will include public, private, protected and implementation operations of the receiver class.
- If OpsVisibility="1", the operations list will only display those operations that are valid according to Java language specifications (see below).
Validity of the operations depend upon the following access specifications:
- Public - Any sender class in any package has access to a receiver class's public operations
- Private - Accessible only when sender class and receiver class are the same
- Protected - Accessible to subclasses (which can be in other packages) and all sender classes in the same package
- Implementation or Default - Accessible to the sender classes which are in the same package of the receiver classes
You will now be able to access the RTJava operations (from the "Call Message Specification" dialog) according to the access rules indicated above.
- If OpsVisibility is set to a value other than "1" or "2", or the OpsVisibility registry entry is not included in the registry, the Operations list will only display the public operations, as before.
Note: If the receivers class language is not RTJava, the original behavior remains - only the public operations of the receiver class are listed.
RTJava Example
Consider the following example where a Rose RealTime model has two classes . Let the class names be class1 and class2. The Receiver's class language type is RTJava.
Assume class1 has the following operations
1. class1_public_op() - public operation
2. class1_protected_op() - protected operation
3. class1_private_op() - private operation
4. class1_implementation_op() - implementation operation
and class2 has the following operations
1. class2_public_op() - public operation
2. class2_protected_op() - protected operation
3. class2_private_op() - private operation
4. class2_implementation_op() - implementation operationLet class1 be the sender class and class2 be the receiver class.
Case 1: OpsVisibility="2"
The operations list will display all the operations of the receiver class class2:
(class2_public_op(), class2_protected_op(), class2_private_op() and class2_implementation_op())
Case 2: OpsVisibility="1"
Sender and Receiver are in Same Package
The public, protected and implementation operations of the receiver class are displayed (class2_implementation_op(), class2_protected_op(), class2_public_op()).
Receiver Class is an Outer Class of the Sender Class
As the Inner Sender Class can see all of the operations of the Outer Receiver Class, the list includes the private, protected, public and implementation operations of the receiver class (class2_implementation_op(), class2_private_op(), class2_protected_op(), class2_public_op()).
Case 3: OpsVisibility is not set to "1" or "2" or the registry entry of OpsVisibility is not included in the registry
The operations list will display the public operations of the receiver class (original default behavior).
Limitations:
The Rose RTJava Improvement to Method Visibility in Sequence Diagrams has the following limitations:
If OpsVisibility="1":
When the Receiver class is a nested (inner) class, the operations drop-down list does not show any operations.
In the example above, when the Receiver class "class2" is a nested class of the Sender class "class1", the operations list will be empty.
Workaround: Set "OpsVisibility" to "2". The operations list will then display all of the Receiver class operations.
Hot Link "operation" will not work (i.e. operation specification dialog will not open) correctly on an operation after resetting OpsVisibility to a value more restrictive than originally used to display the operation in the operations list.
Refer to http://www-1.ibm.com/support/docview.wss?uid=swg21117982 for further information, describing:
Known Issues related to this Add-In
How to Create a Shareable External Library Interface without utilizing the External Library Generation Add-In
RATLC00246421, 519781 / IC39701 | Rose RealTime may hang upon selecting File > Control Unit. When the model is controlled, each Model element (example UseCase etc) are stored in a separate file. Rose RealTime verifies that each file name is unique and generates unique file names for each element. The file name is generated based on the element name given by the user. The general form of the file name is <user given element name>. Extension. An error occurs when attempting to generate a unique file name if the element name contains a "." |
RATLC00246676 / IC39633 | RoseRT may crash and produce the following error, when
loading a model with a hyperlink: NT Exception 001B:005C2C20 |
RATLC00247365 | Enhancement to add Sequence Diagram name to RQART messages.
RQART now displays the name of the test along with the test number that had passed / failed in the test summary pages. |
RATLC376345 / IC39736 | Expansion levels in the Query toolbar option, do not work properly. For example, the value levels in Selected Elements cannot be reset to 1 once they are set to level higher than 1. |
RATLC00516355 | Toolset crash can occur after configuring capsule for both Connexis CRM and CDM, twice. For example, occurs when trying to configure the same capsule for Connexis after re-opening the model. |
RATLC00516591 / IC37635 | Code generation HeaderPreface can be incorrect if the last character in the HeaderPreface is not a newline character. |
RATLC00517053, 519068 / IC38052 | Rose RealTime Toolset times out when using the RoseRT / ClearCase / ClearQuest integration and "Window trigger selection" - "V2" |
RATLC517297 / IC37917 | Slow display of role list for interaction instance on a Sequence Diagram. (See "Enhancement for Slow Performance when Displaying Sequence Diagram Role List", the Rose RealTime Release Notes). |
RATLC00518307 / IC38924 | Generation of dependencies is incorrect for makefiles in relation to Java components. |
RATLC00518507 / IC37876 | After modifying a controlled collaboration diagram which includes children ,under source control, then performing an undo checkout of the collaboration diagram may cause references to the children to be lost. |
RATLC00518786 / IC39194 | Model corruption occurs, on Japanese OS, when including actors in collaboration diagrams. |
RATLC00518787 / IC39069 | Connexis CDR / ASCII Encoding does not function correctly when working with data for which the size is greater than 64K. |
RATLC00518788 / IC39070 | Connexis Viewer metrics collection does not function correctly if the component instance is using ASCII encoding / decoding (-CNXtde-1). |
RATLC00518847 / IC37316 | Slow model validation for large enumeration (i.e. several attributes included). |
RATLC00518960 / IC39135 | Nested classes result in an incorrect collaboration classifier role. (If a nested class is used as a collaboration classifier role, the classifier identified on the classifier role specification points to an incorrect class.) |
RATLC00518986 / IC37640 | Rose RealTime Toolset may crash when copying and pasting Choice-point. |
RATLC00519013 IC39198 | The Check Unique identifiers presence function does not scale to large models. |
RATLC00519023 / IC37640 | RoseRT may crash and display the following error when
deleting send signal that has text attached and then saving the model: NT Exception 001B:0000.. |
RATLC00519049 | Class shape becomes smaller on a diagram, upon adding an aggregation. |
RATLC00519193 | Transition Labels may incorrectly relocate upon editing state diagrams. |
RATLC00519208 / IC37851 | Unresolved references from Interactions to roles may occur, where for example a role is specified by a capsule which is included in nested capsule roles due to decomposition. |
RATLC00519209 / IC37360 | Sending enum in Connexis does not function correctly in Rose RealTime 2003. When data is sent from the sender, Connexis tries to decode the data. If the decode fails, it is ignored. This is due to the fact that the CodeGen does not generate data type installer code for the enum datatype, which helps decoding data. |
RATLC00519358 | Disabling the Add-In, "External Library Generation". See http://www-1.ibm.com/support/docview.wss?uid=swg21117982 for further information. |
RATLC00519456 / IC39013 | The Connexis Viewer truncates long messages (longer
than 4096 bytes) even when the component uses the following command line
options: CNXatud=-1 -CNXtmts=CRM:65500 -CNXtbp=64:1,600,32:65500:16 |
RATLC00519465 | Faulty renaming of state in superclass, causes RoseRT to crash upon loading model. |
RATLC00519781 / IC39701 | RoseRT may hang upon selecting File > Control Unit if an included element name includes the "." character. |
RATLC00520349 / IC39882 | Unable to decode nested enum implemented according to the enumerated stereotype. For a nested class, both the outer and inner class is installed. However, this is not the case for the enumeration. The code generator should install RT Type_Enuminner as well. |
RATLC00520380, 520437, 520663 / IC39934 | Error executing "rterror.pl", due
to use of un-initialized variables: Use of un-initialized value at rterror.pl line xxx |
RATLC00520393 / IC39947 | Unresolved pathmap occurs when relative pathmaps are used for external documents. (Sequence Diagram). |
RATLC00520402 | Rose RealTime C++ code
generator will not build components where two components refer to the same
class. When the component being built references two different
components that have the same referenced items, the following error may
occur: Error: The name of this class (from component 'Component View::Three') is not unique in component 'Component View::One' NMAKE : fatal error U1077: 'rtcppgen' : return code '0x3' Stop. New command line option available, "-fignore-dup-names" which can be set to ignore the duplicate name conflicts when a component is referring to two other components, and both of which are referring to the same class. This would be allowed even if name conflicts exist. |
RATLC00520425 / IC39999 | Enhancement to remove the "-nostdinc" flag from the TargetRTS for Tornado 2.2. |
RATLC00520598 / IC40273 | Model Integrator may create corrupt model when merging file with Rose RealTime 2003, as pipe characters are incorrectly removed. |
RATLC00521496 / IC40535 | Model line colors are not saved correctly. |
RATLC00521728 / IC40581 | External document links don't work correctly when using pathmaps. |
RATLC00521821 / IC40591 | Font color for Default Font is not saved correctly, if font color is set to black. |
RATLC00522059 / IC40688 | TargetRTS may be missing in Tools Menu for Rose RealTime 2003.06.12. Corrected by adding the necessary registry entry. |
RATLC0052223 | Enhancement in Rose RealTime Java to improve method visibility in Sequence Diagram. See "Rose RTJava Improvement to Method Visibility in Sequence Diagrams" in the Rose RealTime Release Notes. |
RATLC000522638 / IC41029 | Upon attempting to load
the latest version of a Rose model could result in the following error: Error: Error reading file C:\rose_sample.mdl at line XXX Fix included to maintain compatibility with newer Rose petal file format. |
RATLC00522942 | Connexis CRM application enters tight loop when Connection is broke at the server end. This consumes 100% of CPU cycles before the rtUnbound is received. The problem does not occur with CDM. |
RATLC00524473 / IC41405 | Memory Leak in Connexis DCS.rtmdl The transportName was deleted incorrectly in the Logical View -> DCSComponents-> DCSController-> RTDRemotePort->cleanup function. "delete transportName; changed to delete [] transportName; |
RATLC00525351 / IC41665 | Rose RealTime / SoDA
generated Sequence Diagrams are not identical.
In Rose RealTime, if the Sequence Diagram includes many arguments (args) to the method, the method signature is drawn as method(arg1, arg2, ...). However when the SoDA report is generated all the parameters are completely displayed which makes the report difficult to read. |
RATLC00526175 / IC41994 | RTProtocol::size() crash on Connexis could occur when disconnections and reconnections of ports happen frequently. |
[Release_Location]/RQART/bin/sun5/librqart.so
[Release_Location]/RQART/bin/sun5/rqart.rsb
[Release_Location]/bin/sun5/modelintRT
[Release_Location]/bin/sun5/modelintRT.rsb
[Release_Location]/bin/sun5/rtrun
[Release_Location]/bin/sun5/rtjavaui.rsb
[Release_Location]/bin/sun5/rtjavagen
[Release_Location]/bin/sun5/rtcbld.rsb
[Release_Location]/bin/sun5/rtcgen
[Release_Location]/bin/sun5/rtcppbld.rsb
[Release_Location]/bin/sun5/rtcppgen
[Release_Location]/bin/sun5/RoseRT
[Release_Location]/bin/sun5/RoseRT.rsb
[Release_Location]/bin/sun5/RationalRose.tlb
[Release_Location]/bin/sun5/RationalRoseRT.tlb
[Release_Location]/bin/sun5/rtcppbld.dll
[Release_Location]/bin/sun5/rtcbld.dll
[Release_Location]/bin/sun5/rtjavaui.dll
[Release_Location]/bin/registry/c.reg
[Release_Location]/bin/registry/connexis.reg
Release_Location]/bin/registry/ConvertRoseComponent.reg
[Release_Location]/bin/registry/cpp.reg
[Release_Location]/bin/registry/filetypes.reg
[Release_Location]/bin/registry/MoveModelElements.reg
[Release_Location]/bin/registry/RoseRT.reg
[Release_Location]/bin/registry/RTJava.reg
[Release_Location]/bin/registry/rtwizards.reg
[Release_Location]/bin/registry/webpub.reg
[Release_Location]/bin/registry/BuildRTS.reg
[Release_Location]/bin/registry/AddExternalJava.reg
[Release_Location]/Connexis/C++/lib/LYNX30T.ppc-cygnus-2.7-97r1/libDCS.a
[Release_Location]/Connexis/C++/lib/LYNX30T.x86-cygnus-2.7-97r1/libDCS.a
[Release_Location]/Connexis/C++/lib/OSE411T.ppc603-Diab-4.3f/libDCS.a
[Release_Location]/Connexis/C++/lib/OSE411T.sparc-gnu-2.95.1/libDCS.a
[Release_Location]/Connexis/C++/lib/OSE411T.x86-VisualC++-6.0/DCS.lib
[Release_Location]/Connexis/C++/lib/SUN5T.sparc-SunC++-5.0/libDCS.a
[Release_Location]/Connexis/C++/lib/SUN5T.sparc-gnu-2.8.1/libDCS.a
[Release_Location]/Connexis/C++/lib/SUN5T.sparc-gnu-2.95.1/libDCS.a
[Release_Location]/Connexis/C++/lib/TORNADO2T.simpc-egcs-2.90.29/libDCS.a
[Release_Location]/Connexis/C++/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libDCS.a
[Release_Location]/Connexis/C++/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libDCS.a
[Release_Location]/Connexis/C++/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libDCS.a
[Release_Location]/Connexis/bin/sun5/libTraceData.so
[Release_Location]/Connexis/bin/sun5/ConnexisViewer
[Release_Location]/Connexis/bin/sun5/ConnexisViewer.rsb
[Release_Location]/Connexis/bin/sun5/connexis.rsb
[Release_Location]/Connexis/bin/sun5/libconnexis.so
[Release_Location]/Connexis/Model/DCS.rtmdl
[Release_Location]/C++/TargetRTS/lib/CHORUS40T.ppc603-egcs-2.91.66/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/CHORUS40T.ppc603-egcs-2.91.66/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/CHORUS40T.ppc603-egcs-2.91.66/main.o
[Release_Location]/C++/TargetRTS/lib/LYNX30T.ppc-cygnus-2.7-97r1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/LYNX30T.ppc-cygnus-2.7-97r1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/LYNX30T.ppc-cygnus-2.7-97r1/main.o
[Release_Location]/C++/TargetRTS/lib/LYNX30T.x86-cygnus-2.7-97r1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/LYNX30T.x86-cygnus-2.7-97r1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/LYNX30T.x86-cygnus-2.7-97r1/main.o
[Release_Location]/C++/TargetRTS/lib/LYNX31T.ppc-gnupro-2.9-98r2/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/LYNX31T.ppc-gnupro-2.9-98r2/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/LYNX31T.ppc-gnupro-2.9-98r2/main.o
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/main.o
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/main.o
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTimeTypes.LIB
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/main.OBJ
[Release_Location]/C++/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTime.LIB
[Release_Location]/C++/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/main.o
[Release_Location]/C++/TargetRTS/lib/NUCLEUS11T.x86-VisualC++-6.0/libObjecTimeTypes.LIB
[Release_Location]/C++/TargetRTS/lib/NUCLEUS11T.x86-VisualC++-6.0/main.OBJ
[Release_Location]/C++/TargetRTS/lib/NUCLEUS11T.x86-VisualC++-6.0/libObjecTime.LIB
[Release_Location]/C++/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/main.o
[Release_Location]/C++/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/main.o
[Release_Location]/C++/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTimeTypes.LIB
[Release_Location]/C++/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/main.OBJ
[Release_Location]/C++/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTime.LIB
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/main.o
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.95.1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.95.1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-gnu-2.95.1/main.o
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.0/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.0/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.0/main.o
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.3/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.3/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/SUN5T.sparc-SunC++-5.3/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.simpc-egcs-2.90.29/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.simpc-egcs-2.90.29/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.simpc-egcs-2.90.29/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.simso-cygnus-2.7.2-960126/main.o
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTimeTypes.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTime.a
[Release_Location]/C++/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/main.o
[Release_Location]/C++/TargetRTS/lib/WINCE300T.sh3-eMVisualC++-3.0/libObjecTimeTypes.LIB
[Release_Location]/C++/TargetRTS/lib/WINCE300T.sh3-eMVisualC++-3.0/main.OBJ
[Release_Location]/C++/TargetRTS/lib/WINCE300T.sh3-eMVisualC++-3.0/libObjecTime.LIB
[Release_Location]/C++/TargetRTS/src/RTAsciiDecoding/get_indirect.cc
[Release_Location]/C++/TargetRTS/codegen/rterror.pl
[Release_Location]/C++/TargetRTS/config/TORNADO22T.ppc603-gnu-2.96/config.mk
[Release_Location]/C++/TargetRTS/config/TORNADO22T.simnt-gnu-2.96/config.mk
[Release_Location]/C++/TargetRTS/config/TORNADO22T.simnt-gnu-2.96/setup.pl
[Release_Location]/C/TargetRTS/lib/eCos20020128_uITRON302T.x86-gnu-2.95.3/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/eCos20020128_uITRON302T.x86-gnu-2.95.3/main.o
[Release_Location]/C/TargetRTS/lib/eCos20020128_uITRON302T.x86-gnu-2.95.3/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/main.o
[Release_Location]/C/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/main.o
[Release_Location]/C/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTimeCTransport.LIB
[Release_Location]/C/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/main.obj
[Release_Location]/C/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTimeC.LIB
[Release_Location]/C/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/main.o
[Release_Location]/C/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/main.o
[Release_Location]/C/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTimeCTransport.LIB
[Release_Location]/C/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/main.OBJ
[Release_Location]/C/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTimeC.LIB
[Release_Location]/C/TargetRTS/lib/SUN5S.sparc-gnu-2.8.1/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/SUN5S.sparc-gnu-2.8.1/main.o
[Release_Location]/C/TargetRTS/lib/SUN5S.sparc-gnu-2.8.1/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/SUN5S.sparc-SunC-5.0/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/SUN5S.sparc-SunC-5.0/main.o
[Release_Location]/C/TargetRTS/lib/SUN5S.sparc-SunC-5.0/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/main.o
[Release_Location]/C/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/SUN5T.sparc-SunC-5.0/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/SUN5T.sparc-SunC-5.0/main.o
[Release_Location]/C/TargetRTS/lib/SUN5T.sparc-SunC-5.0/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO2S.m68040-cygnus-2.7.2-960126/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO2S.m68040-cygnus-2.7.2-960126/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO2S.m68040-cygnus-2.7.2-960126/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO2S.ppc-cygnus-2.7.2-960126/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO2S.ppc-cygnus-2.7.2-960126/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO2S.ppc-cygnus-2.7.2-960126/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO2S.x86-cygnus-2.7.2-960126/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO2S.x86-cygnus-2.7.2-960126/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO2S.x86-cygnus-2.7.2-960126/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTimeC.a
[Release_Location]/C/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/main.o
[Release_Location]/C/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTimeCTransport.a
[Release_Location]/C/TargetRTS/codegen/rterror.pl
[Release_Location]/C/TargetRTS/config/TORNADO22T.ppc603-gnu-2.96/config.mk
[Release_Location]/C/TargetRTS/config/TORNADO22T.simnt-gnu-2.96/config.mk
[Release_Location]/C/TargetRTS/config/TORNADO22T.simnt-gnu-2.96/setup.pl
Note:
[Release_Location] is the
directory that the IBM Rational Products are installed in. This is
typically "C:\Program Files\Rational\Rose RealTime*".
The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support homepage can be found at http://www.ibm.com/software/support.
Voice Support is available to all current contract holders via a telephone number in your country (where available). For specific country phone numbers, please refer to the IBM Software Support Handbook, Appendix B: Contact Information, found at http://www.ibm.com/software/support.