IBM^® Rational^® Rose ^® Real Time v2003.06.15b

Fix Pack 1 Release Notes

February 2007

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

Scope

This Fix Pack updates with Enhancements and Defect Fixes.

This has been tested on Solaris 8, 9.

Hardware/Software Information

Hardware / Software requirements for this Fix Pack are the same as those described in the installation Guide for Suites v2003.06.00.

Getting Started

In addition to the instructions provided in the "Getting Started" section of the Rose RealTime 2003.06.00 Release Notes, please review the following information new in this Fix Pack for Rose RealTime 2003.06.15b.

Installation Information

Installation Instructions

Note: $ROSERT_HOME is the Rational Rose RealTime Product installation directory.

Rose RealTime 2003.06.15b must be installed prior to installing this Fix Pack.
Backup (rename) the files listed in section “Files Updated or Added by this Fix Pack” (if they exist).
Copy the Fix Pack – RoseRT.SR5b.FixPack1_2086.tar.gz in $ROSERT_HOME
cd $ROSERT_HOME
gunzip < RoseRT.SR5b.FixPack1_2086.tar.gz | tar xpf -

Compatibility Issues

This section describes any compatibility issues that could arise from use of this Fix Pack.

With Third-Party Products

This Fix Pack does not introduce any known compatibility issues with third-party products.

Rose RealTime Petal Format or Code Generation Impacts

This Fix Pack does not impact or include changes to existing Petal Format.

There are Code Generation changes included, but no changes that will cause compatibility issues.

Rose RealTime TargetRTS Impacts

This Fix Pack includes TargetRTS changes to provide extended support for simple C++ types in protocols.

Additional, changes made to the following files - please review:

$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/reply.cc

$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/sendOne.cc

Refer to the section below entitled “Fix Pack Changes to TargetRTS” for a complete description of the changes.

Rose RealTime Solaris v2003.06.15b Test Fixes Included

This Fix Pack includes Solaris Rose RealTime v2003.06.16b Test Fix 1 through Test Fix 11.

Enhancements

Rose RealTime Enhancements included in this Fix Pack

§ Rose RealTime C++

o Extended Support for simple C++ types in protocols

§ Rose RealTime ClearCase Integration

o Improved Efficiency when performing ClearCase actions through Rose RealTime

o Ability to invoke ClearCase source control command move within Rose RealTime

o Ability to add comments from within the RoseRT SCC Check Out dialog

o Ability to invoke ClearCase commands: rename, and delete from RealTime

§ Rose RealTime Toolset

o Suppress Code Generation warning “transition has no events” for capsules with ‘abstract’ stereotype

o Ability to Browse Generated Makefiles

o Enhanced Flexibility and Performance by providing ability to Build Multiple Components

o Ability to perform Multiple Select Drag and Drop

o Ability to perform a String Search through all Inherited Classes

§ Integrated Support with Quantify & Pure Coverage

§ Rose RealTime Model Integrator

o Ability to view Rose RealTime model code differences using ClearCase Diff / Merge tool through Rose RealTime Model Integrator Compare view

Rose RealTime Toolset

Suppress Code Generation warning “transition has no events” for capsules with ‘abstract’ stereotype

An ‘abstract’ stereotype may now be applied to capsules.

Now, the warning message “transition has no events” will be suppressed when generating code for a capsule if the capsule’s stereotype is set to abstract even if there are no apparent triggers associated with a transition. In this case, the triggers may be defined in the derived capsule state diagram.

The warning message “transition has no events’ will continue to display when generating code for capsules for which the stereotype is not set as abstract when there are no triggers associated with the transition.

Also, when the notification checkbox is cleared, as shown in the figure below – the “transition has no events” warning will not display in any case.

To suppress the “transition has no events” warning for a capsule which contains transitions without associated triggers, set the capsule’s stereotype to ‘abstract’ in the Capsule Specification as shown below.

Ability to Browse Generated Makefiles

You may now view Makefiles generated for specific components, within Rose RealTime.

Upon selecting a component and selecting the File menu, a new “Browse Generated Code” menu option is available which includes the following sub-menu options:

§ Header…
Browse Header

§ Body…
Browse Body

§ Root Makefile…
Browse Makefile in the root directory of the component.

§ Src/Makefile…
Browse Makefile inside the src directory within the root directory of the component.

§ Build/Makefile...
Browse Makefile inside the build directory within the root directory of the component.

IMPORTANT: It will be possible to edit the Makefile in addition to viewing, however, this would be similar to editing the Makefile from any external editor and the same considerations apply.

Enhanced Flexibility and Performance by providing ability to Build Multiple Components

You may now build multiple components without verifying all dependencies and performing a recursive make. This significantly reduces the amount of time necessary to perform a build, when it is only necessary to build specific multiple components.

In order to build specific multiple components:

Select the components you wish to build in the browser and right click to show the new context menu “Build Multiple Components”

Selecting the new context menu will cause the standard Build… dialog to display.

The Build… dialog offers the ability to Generate code or Generate and compile (link).

When utilizing the “Build Multiple Components”, Rose RealTime will only verify the dependencies among dependent components. The build will be consistent only up to the dependency hierarchy where you have selected the component.

Limitations:

§ When building the Rose RealTime model the first time, a complete “Build” is necessary. If you select “Build Multiple Components” without first performing a complete Build, a dialog box indicating “Use Build Option” will appear and it will be necessary to perform the complete Build.

§ If the Rose RealTime component settings have been changed or any new references are added to components, you will need to generate the makefile using the “Build” option, as these changes require makefile updates.

§ The current Build option generates dependent object files. The new Build Multiple Components option does not generate all dependent object files.

§ “Build Multiple Components” is only available when selecting multiple components.

IMPORTANT: After performing a component build (“Build Multiple Components”) it will be important to verify parent components are in a consistent state.

Rose RealTime C++

Extended Support for simple C++ types in protocols

In addition to the original existing C++ data types, you may now select the following unsigned (in addition to signed) C++ data types from the Signal Specification dialog:

§ unsigned char

§ unsigned short

§ unsigned int

§ unsigned long

Ability to perform Multiple Select Drag and Drop

For the following use case scenarios, you may multi-select elements from a source list and drag and drop them to the target list. The items selected will be copied or moved, according to the appropriate semantics of the drag and drop functionality between these lists.

1. Multiple Drag and Drop attributes or operations from:

§ Capsule to Capsule

§ Capsule to Class

§ Class to Class

§ Class to Capsule

In this case the attributes / operations are moved from the source to the target list.

Before Drag and Drop

After Drag and Drop

2. Drag and Drop signals from within Protocol Class Specification dialog (Signals tab)

§ From in-signals list to out-signals list

§ From out-signals list to in-signals list

In this case the signals are copied from the source to the target list.

Before Drag and Drop

After Drag and Drop

Limitations:

§ Multiple Drag and Drops may only be performed through Specification dialogs

§ Unable to Drag and Drop multiple components from Browser

Future Drag and Drop scenario considerations:

§ Operation parameters

§ Signals

o Browser to Protocol Specification

o Protocol class to Protocol class

§ Collaboration diagram

o Class to Capsule

o Capsule to Class

o Capsule to Capsule

§ Sequence diagrams from Capsule’s State structure diagram to CSSD

§ Class, capsule and/or Protocol classes across reference tabs of Component Specification dialogs

§ Classes across Nested tabs of Class Specification dialogs

§ Model elements – Package to Package

§ Files and URL’s from Files tab of Specification dialogs

§ Multiple elements across browser windows

§ Multiple components to a processor

Ability to perform a String Search through all Inherited Classes

You now have the ability to search through an entire class, capsule, or protocol class hierarchy.

Two new check-box options Search in the Parent Tree and Search in the Derived Tree are now available in the Find in and Replace in dialogs for classes, capsules or protocol classes. These menu options are enabled when selecting a Class, Capsule, Protocol class, Actor, ClassUtility or Interface in the browser. Right clicking on one of these elements, and selecting the Find in or Replace in context menus will display the corresponding dialog with the new check-box options.

Search in the Parent Tree - Searches from the selected class, capsule or protocol class, it's parent, etc. until reaching the starting node without a parent.

Search in the Derived Tree - Searches from the selected class, capsule or protocol class, it's children, etc. until reaching all of the leaf nodes.

Search in the Parent Tree + Search in the Derived Tree - searches through the entire selected class, capsule or protocol's class hierarchy.

Note:

Search in the Parent Tree and Search in the Derived Tree options will be disabled if any element selected in the browser other than Class, Capsule, Protocol class, Actor, ClassUtility or Interface.

Rose RealTime ClearCase Integration

Improved Efficiency when performing ClearCase actions through Rose RealTime

It is no longer necessary to click on the “Parameters…” button of the corresponding dialog, while performing ClearCase actions such as Check Out, Check In and Undo Checkout within Rose RealTime, in order to set the properties such as Reserved Check Out or Save copy of the file with a ‘.keep’ extension etc.

The following illustrates the new check-box options in standard Rose RealTime / ClearCase integration dialogs.

1. Check Out dialog

§ Added a new “Unreserved” check-box (by default, disabled)

§ Removed Parameters… button

To perform Unreserved check out of a file, check the “Unreserved” check-box.
To perform Reserved check out of a file, uncheck the “Unreserved” check-box.

2. Undo dialog

§ Added a new “Save copy of the file with a ‘.keep’ extension” checkbox (by default, disabled)

§ Removed Parameters… button

To save copy of the file with *keep extension, check the “Save copy of the file with a ‘.keep’ extension.” check-box.

3. Check In dialog

§ Added a new “Check in even if identical to previous version” checkbox (by default, disabled)

§ Retained existing “Keep checked out” check-box

§ Removed Parameters… button

To Check In the file even if it is identical to the previous version, check the “Check in even if identical to previous version” check-box.

To disable the Check In of the file if it is identical to the previous version, uncheck the “Check in even if identical to previous version” check-box (default behavior).

Ability to invoke ClearCase source control command move within Rose RealTime

Selecting the element under ClearCase control and performing a ClearCase “move” will move the file corresponding to the controlled unit from the original source control location to the new source control location. Move will occur by using the “cleartool mv” command. This will cause an implicit check-out of the relevant directory(ies). The files and folders being checked-out will be listed in the dialog box. Once the actions are complete, the user will need to check-in the elements, which can be completed through the RoseRT / ClearCase integration.

How to use ClearCase move from Rose RealTime

§ Go to Tools > Options

§ Check the check-box “Enable ClearCase move”

*Note: By default Tools > Option “Enable ClearCase move” will be unchecked. In this case the right mouse click maintains original behavior (allowing you to move elements without using ClearCase move).

By default the right mouse click drag and drop exhibits the same behavior as the left click drag and drop. The “Enable ClearCase move” setting will be persistent through the Rose RealTime sessions.

§ Right click* on the ClearCase element to be moved and drag to the source control location where it is to be moved. In the illustration below – the user has right clicked on NewClass1 and will drag it to NewPackage2

Once the drag and drop action is completed – the warning dialog will be displayed as illustrated below.

After selecting “Yes”, the Source will be physically moved (using the ClearCase mv command) to the NewPackage2 source control destination. In this case, NewClass.rtclass will physically move to the NewPackage2 source code location.

Please refer to the table below for the detailed set of use cases and behaviors involving the ClearCase Move feature.

Limitations: As illustrated in the chart below – the ClearCase Move will only be allowed when right clicking and dragging and dropping element from Clear Case source control to another ClearCase source control location.

Attempting to perform right click drag and drop from ClearCase source control to a location not under ClearCase source control will not be allowed and user will see the following message box:

Table 1. Right Click Drag and Drop (source) Under Source Control & Not Under Source Control

Source / Destination

Under Source Control

Not Under Source Control

Scratch Pad

Under Source Control

Right click

drag and drop

CLEARCASE MOVE. File location changes on disk.

Right click

drag and drop

NOT ALLOWED

Right click

drag and drop

Same as before, not allowed.

Not Under Source Control

Right click

drag and drop

Same as before. Model Move. No change in file location.

Right click

drag and drop

Same as before. Model Move. No change in file location.

Right click

drag and drop

Same as before, not allowed.

Ability to add comments from within the RoseRT SCC Check Out dialog

When performing ClearCase Check Out commands utilizing the Rational Rose RealTime / Rational ClearCase integration, a new window is available in the Check Out dialog, allowing you to enter comments.

To add comments when performing a ClearCase Check Out from Rational Rose RealTime add comments in the Comment text window of the Check Out dialog.

Limitations:

§ It is not possible to apply different comments when making a multiple element Check Out.

§ When performing a ClearCase Check In through Rational Rose RealTime, the comments entered during the Check Out will display, except if entered during a multiple element Check Out (similar to the behavior when adding a comment to multiple elements through the ClearCase Explorer).

Ability to invoke ClearCase commands: rename, and delete from RealTime

Now, when invoking the following commands on a Rose RealTime element (which is under ClearCase control and accessed via the Rose / ClearCase integration), the associated ClearCase action will occur on the underlying ClearCase element.

§ Source Control > Rename

Triggers rename of underlying ClearCase controlled unit.

§ Source Control > Delete

Deletes files corresponding to ClearCase controlled unit (utilizing ClearCase rmname command).

The following message will display prior to performing these ClearCase actions. You have the option to select "Yes" or "No".

Warning: This is a ClearCase operation and cannot be reverted. Would you like to proceed with the operation?

Limitations: Utilizing any of the above options will cause an implicit Check Out of the relevant directory(ies). Once the actions are complete, you will need to manually perform the Check In, which may also be completed through the Rose RealTime / ClearCase integration.

Integrated support with Quantify and Pure Coverage

The integration with Quantify & Pure Coverage is similar to the long-standing integration with Purify. You may now link with Quantify and Pure Coverage through Rational Rose RealTime and view the results in the applicable application (i.e. Quantify or Pure Coverage).

Steps to utilize this integration:

1. Verify Quantify and /or Pure Coverage are installed on your machine, or accessible via an NFS mounted disk.

2. Include Quantify and /or Pure Coverage on your $PATH prior to starting Rational Rose RealTime.

3. Set $PURE_HOME to point to the installation of Purify / Quantify / Pure Coverage.

4. Older models will need to be rebuilt (see new Build options below) as a new target will be added to the makefiles.

5. New systems/models will need to be built only once, similar to the Purify integration as rebuilding is only necessary the first time the code is instrumented, unless there are changes in the components.

6. Once the build / link is complete, select Run with Quantify or Run with PureCov.

7. When execution completes the applicable application (i.e. Quantify or PureCoverage) will be invoked to display the output*. You may then use the Quantify or PureCoverage display options to show graphs, function list, function details, etc.

To support this integration new Build and Run menu options are now available:

Note:

Once the executable is instrumented, you may also view the Quantify and Pure Coverage results outside of a Rational Rose RealTime session via the command line.

Limitation: *The Quantify & Pure Coverage integrations differ from the Purify Plus integration, as the output is displayed in the applicable application vs. Rational Rose RealTime. This allows you to utilize all display options available by these applications.

Rose RealTime Model Integrator

Ability to view Rose RealTime model code differences using ClearCase Diff / Merge tool through Rose RealTime Model Integrator Compare view

You may now review code changes made to a Rational Rose RealTime model, which is under ClearCase control, through the ClearCase Diff / Merge tool when reviewing the model under Compare mode of the Rational Rose RealTime Model Integrator. To use this capability, the model must be under ClearCase control and xcleardiff must be on your $PATH before running Rational Rose RealTime. The following new options are available in Compare mode of the Model Integrator:

§ Fixed button "C" (next to Merge button)

§ File menu option: Compare Source Code

§ Context menu option: Compare Source Code

The new Compare Source Code options are enabled in the Rational Rose RealTime Model Integrator Compare mode when there are source code differences in the contributors.

When selecting one of the Compare Source Code options, the ClearCase Diff / Merge tool will display.

All ClearCase Diff / Merge tool options will be available, i.e.:

All source code differences will be displayed in the ClearCase Diff / Merge tool text windows.

Standard highlight and color coding options will be available.

Also, it is possible to synchronously scroll through contributor code windows (difference information for each contributor will be displayed in each code window).

Rose RealTime Solaris Model Integrator Performance Improvements

This Fix Pack contains the following performance improvements for the Rational Rose RealTime Model Integrator. The performance improvement is greater when the operation body of the contributors is very large.

Rose RealTime Model Integration Performance is enhanced during the following actions:

1. Loading contributors that contain large operation bodies

2. Displaying tool-tip information for the property selected

3. Displaying property values in the Rose RealTime Model Integrator editors

4. Opening the ClearCase Diff-Merge tool from the Rose RealTime Model Integrator

New Model Integrator Tool-tip behavior

Previously, when mouse hovered over the body property of an operation, there was a delay for the tool-tip to display the complete body contents. Now, the Model Integrator will only show 1024 characters in the tool-tip. If the body of the operation is more than 1024 characters then “…” will be shown at the end of the tool-tip. This behavior is as shown in the figure below.

Defects Fixes

Rose RealTime Defects Fixed in this Fix Pack

Component	Problem ID	Description
Rose RealTime C	PK29464; RATLC00146014	Rose RealTime C Code generator fails when generating protocol without signals.
Rose RealTime C	PK30049; RATLC00146225	Documentation is generated even if "Do not generate" option is set in case of protocol signals.
Rose RealTime C++	PK15081; RATLC01103805	Rose RealTime may crash when changing attribute name.
Rose RealTime ClearCase Integration	PK19678; RATLC00512487	*.rtintractn is now added to cc_rosert_unit.magic for Sequence diagrams.
Rose RealTime ClearCase Integration	PK30409; RATLC00388354	Rose RealTime / ClearCase integration does not display anything from "Source Control -> Show History" when Rational ClearCase v7.0 is used. This was due to a change in the date format returned by the ClearCase v7.0 release.
Rose RealTime ClearCase Integration	RATLC00147393	cm_getcomment required for RATLC00212073.. The following Error will occur when attempting to perform a Rose RealTime / ClearCase Check In operation: "Comments" operation failed. See log for details. The log will contain the following information: 13:32:44\| Error: Command failed to execute: Can't open perl script "C:\Program Files\Rational\Rose RealTime\bin\win32\cmscripts\cc\cm_getcomment": No such file or directory. In the Check In dialog box the comment field will be empty.
Rose RealTime Code Generation	RATLC01184816	Codegen crashes while generating code for any model which is having an empty parameter in one of its operation.
Rose RealTime Connexis	RATLC00248781	Rose RealTime applications may crash while calling port->size (RTProtocol::size()). This problem may occur when disconnections and re-connections of ports occur frequently.
Rose RealTime Model Integrator	IC48675; RATLC00542123	Version stamps in petal files may cause the Rose RealTime Model Integrator to generate a non trivial merge. A new filter flag "Ignore Version" has been added This flag is "on" by default and version information from the base contributor will be selected. This flag has to be turned off if you wish to choose one specific version.
Rose RealTime Model Integrator	PK22505; RATLC00144737	The Rational Rose RealTime Model Integrator fails to merge component's Inclusion paths. When the model is opened in Rational Rose RealTime it contains the following error: "Could not add model property "InclusionPaths" to model."
Rose RealTime Model Integrator	PK23165; RATLC00144841	Model Integrator does not detect differences on Solaris. See information in relation to Performance Improvements.
Rose RealTime Model Integrator	PK32496; RATLC00146803	Rose RealTime Model Integrator updates model with UNIX path separators "/" instead of Windows path separators "\\" The Rose RealTime v2003.06.13 Model Integrator updates model file entries chDirName, file_name and external_doc_path with UNIX path separators ("/") to maintain consistency between the UNIX and Windows Model Integrator. A new registry flag has been added allowing you now to use any of the UNIX ("/") and Windows ("\\") path separators for the entries chDirName, file_name and external_doc_path. Now, you may set the path separator style (UNIX / Windows) which will be used by the Rose RealTime Model Integrator for the directory/file properties: chDirName, file_name and external_doc_path, by setting a new registry string UseWindowsPathSeparator under HKEY_CURRENT_USER\SOFTWARE\Rational Software\Rose RealTime\6.5. If UseWindowsPathSeparator is set to value Yes (care insensitive) the Model Integrator will use the Windows style ("\\") path separators for the directory/file properties. If UseWindowsPathSeparator is set to value other than Yes OR registry entry is missing the Model Integrator will use the UNIX style ("/") path separators for the directory/file properties. This is the default behavior. The UseWindowsPathSeparator registry flag will be effective throughout the Rose RealTime Model Integrator session. After making a change to this registry flag, it will be necessary to restart the Model Integrator to reflect the change.
Rose RealTime Model Integrator	RATLC00513349	Unable to open Diff / Merge in Compare Mode. See Ability to view Rose RealTime model code differences using ClearCase Diff / Merge tool through Rose RealTime Model Integrator Compare view.
Rose RealTime Model Integrator	RATLC00962702	Ability to ignore userDefinedSortWeight flag while using Model Integrator. The UserDefinedSortWeight field was added to the Rose RealTime petal file based on RATLC00046354. The addition of this field in the petal file resulted in the Model Integrator showing differences with respect to the models saved prior to the addition of this field in the petal file. A flag "Ignore User sortweight" was added in the Model Integrator filter which allows you to control displaying this difference.
Rose RealTime Toolset	IC48989; RATLC00963322	Rose RealTime may crash upon opening a custom framework model and then loading any other model. This occurred while Rose RealTime was attempting to free memory.
Rose RealTime Toolset	RATLC00144592	Rose RealTime could crash while loading an old Rose RealTime model, as a check for a null pointer was missing.
Rose RealTime Toolset	PK14369; RATLC00143829	Selecting the Apply button may cause the code window to re-position to the beginning. When transition code is changed at the end of the code and then the Apply button is pressed, the code window and scroll-bar jump to the beginning of the transition code. The location should remain the same as before pressing the Apply button.
Rose RealTime Toolset	PK21882; RATLC00144157	The following crash could occur (primarily when running multiple Rose RealTime sessions and either exiting a session or performing a build): __1cP_AfxThreadEntry6Fpv_I_(0xffbec374, 0x192c6d8, 0x1d29708, 0x1, 0x0, - Rose RealTime Exit.
Rose RealTime Toolset	PK22147; RATLC00144674	Port labels may rearrange in base class, when doing a specialization. When a specialization of a capsule is made, the position of port labels in the base class (capsule) may revert to the default position. This occurs due to repositioning of the labels in the base class.
Rose RealTime Toolset	PK25886; RATLC01184853	ClassDependency (RRTEI) is not accessible when part of a ModelElementCollection.
Rose RealTime Toolset	PK26878; RATLC00387628	Rose RealTime may fail to launch the RUP-SE Add-In.
Rose RealTime Toolset	PK29501; RATLC00146043	Rose RealTime may crash when adding an actor to a Collaboration Diagram in the Use Case view.
Rose RealTime Toolset	PK30432; RATLC00146333	Problem refreshing from source control with a large number of files in one directory. When there are a number of files (controlled units) under the same directory, then there will be problem while opening the model under source control.
Rose RealTime Toolset	PK35354; RATLC01186827	Aggregation of states in the base capsule may change the layout of the sub-diagrams of those states in the inherited capsules.
Rose RealTime Toolset	PK34385; RATLC00147258	Performance delay when attempting to add a dependency in Class Specification dialog.
Rose RealTime Toolset	RATLC0045640	Extended Support for simple C++ types in protocols
Rose RealTime Toolset	RATLC0047012	Suppress Code Generation warning “transition has no events” for capsules with ‘abstract’ stereotype.
Rose RealTime Toolset	RATLC00144775	The following crash could occur while removing packages. This was due to corrupted references between the model elements .__1cKOrdCollectKremoveSame6MpknKRoseObject__p1_(0x7, 0x2313af8, 0x2313b90, 0xfc03c008, 0x0, 0xa304)
Rose RealTime Toolset	RATLC00144952	Rational Rose RealTime may crash upon making changes to model and then attempting to reload model.
Rose RealTime Toolset	RATLC00145448	Compilation error links incorrect in some cases.
Rose RealTime Toolset	RATLC00513531	Enable search for entire class hierarchy. See Ability to perform a String Search through all Inherited Classes.
Rose RealTime Toolset	RATLC00521863	Ability to browse generated makefile. See Ability to Browse Generated Makefiles.
Rose RealTime Toolset	RATLC00962869	Rose RealTime may crash upon running the RRTEI script when creating invalid (null) relation.
Rose RealTime Toolset	RATLC01184952	The following crash will occur when attempting to print a State diagram containing an internal self-transition when using layout "Fit to page" or "Tile". Crash MwDrvLineTo(0xa55e680, 0x5f, 0x27f, 0x17e9fc8, 0xb8, 0xfc3f1104) + 0x28
Rose RealTime Toolset	RATLC01185430	Reduce number of mouse clicks when performing ClearCase operations. See Improved Efficiency when performing ClearCase actions through Rose RealTime.
Rose RealTime Toolset	RATLC001185716	RRTEI event requested to determine if background refresh of CM information is completed. Two new events added: 1. OnBackGroundRefreshStart 2. OnBackGroundRefreshFinish

Fix Pack Changes to TargetRTS

This Fix Pack includes the following TargetRTS changes and additions (as required for Extended Support for simple C++ types in protocols):

Changes to existing TargetRTS source code files
Addition of new source code files to the TargetRTS

Changes to existing TargetRTS source code files

The following existing TargetRTS source code files have been changed, as indicated below. Changes include addition of code only.

$ROSERT_HOME/C++/TargetRTS/include/RTLog.h

$ROSERT_HOME/C++\TargetRTS/include/RTObject_class.h

$ROSERT_HOME/C++/TargetRTS/include/RTEncoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTDecoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTAsciiEncoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTAsciiDecoding.h

$ROSERT_HOME/C++/TargetRTS/src/MANIFEST.cpo

$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/reply.cc

$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/sendOne.cc

Files Changed	Changes ( in blue )
RTLog.h	. . . void log( const void , const RTObject_class ); RTS_INLINE void log( const RTTypedValue & ); void log( unsigned int ); void log( unsigned long ); void log( unsigned short ); void log( unsigned char ); void show( char ); #if RTUseFloatingPoint . . . void show( const RTDataObject & ); void show( const void , const RTObject_class ); RTS_INLINE void show( const RTTypedValue & ); void show( unsigned int ); void show( unsigned long ); void show( unsigned short ); void show( unsigned char ); #endif void space( void ); . . .
RTObject_class.h	. . . extern const RTObject_class RTType_int; extern const RTObject_class RTType_long; extern const RTObject_class RTType_short; extern const RTObject_class RTType_unsigned; extern const RTObject_class RTType_unsignedint; extern const RTObject_class RTType_unsignedlong; extern const RTObject_class RTType_unsignedshort; extern const RTObject_class RTType_unsignedchar; typedef char * RTpchar; typedef void * RTpvoid; typedef unsigned char RTuchar; . . .
RTEncoding.h	. . . virtual int put_ulong ( unsigned long ) = 0; virtual int put_ushort ( unsigned short ) = 0; virtual int put_unsignedint( unsigned int ) = 0; virtual int put_unsignedlong( unsigned long ) = 0; virtual int put_unsignedshort( unsigned short ) = 0; virtual int put_unsignedchar( unsigned char ) = 0; // a nul-terminated string virtual int put_string( const char * ) = 0; . . .
RTDecoding.h	. . . virtual int get_int ( int & ) = 0; virtual int get_long ( long & ) = 0; virtual int get_unsignedint(unsigned int & ) = 0; virtual int get_unsignedlong(unsigned long & ) = 0; virtual int get_unsignedshort(unsigned short & ) = 0; virtual int get_unsignedchar(unsigned char & ) = 0; #if 0 #if _MSC_VER > 1000 virtual int get_long_long( __int64 & ) = 0; #else . . .
RTAsciiDecoding.h	. . . virtual int get_int ( int & ); virtual int get_long ( long & ); virtual int get_unsignedint( unsigned int & ); virtual int get_unsignedlong( unsigned long & ); virtual int get_unsignedshort( unsigned short & ); virtual int get_unsignedchar( unsigned char & ); #if 0 #if _MSC_VER > 1000 . . .
RTAsciiEncoding.h	. . . virtual int put_ulong ( unsigned long ); virtual int put_ushort ( unsigned short ); virtual int put_unsignedint( unsigned int); virtual int put_unsignedlong( unsigned long); virtual int put_unsignedshort( unsigned short); virtual int put_unsignedchar( unsigned char); virtual int put_string( const char * ); virtual int put_opaque( int, const char * ); . . .
MANIFEST.cpp	. . . RTLog log_int OBJECT_ENCODE RTLog log_unsignedint OBJECT_ENCODE RTLog log_unsignedlong OBJECT_ENCODE RTLog log_unsignedshort OBJECT_ENCODE RTLog log_unsignedchar OBJECT_ENCODE RTLog log_long OBJECT_ENCODE RTLog log_short OBJECT_ENCODE . . . RTLog show_short OBJECT_ENCODE RTLog show_unsignedint OBJECT_ENCODE RTLog show_unsignedlong OBJECT_ENCODE RTLog show_unsignedshort OBJECT_ENCODE RTLog show_unsignedchar OBJECT_ENCODE RTLog show_string . . . RTObject_class install RTObject_class int RTObject_class unsignedint RTObject_class unsignedlong RTObject_class unsignedshort RTObject_class unsignedchar RTObject_class isKindOf RTObject_class long . . . RTTypedValue int RTTypedValue unsignedint RTTypedValue unsignedlong RTTypedValue unsignedshort RTTypedValue unsignedchar RTTypedValue long RTTypedValue pvoid . . . RTAsciiDecoding get_ushort RTAsciiDecoding get_unsignedint RTAsciiDecoding get_unsignedlong RTAsciiDecoding get_unsignedshort RTAsciiDecoding get_unsignedchar RTAsciiDecoding ungetByte RTAsciiDecoding unused . . . RTAsciiEncoding put_unsigned RTAsciiEncoding put_ushort RTAsciiEncoding put_unsignedint RTAsciiEncoding put_unsignedlong RTAsciiEncoding put_unsignedshort RTAsciiEncoding put_unsignedchar RTAsciiEncoding unused . . .

sendOne.cc

Before Change

After Change

if( owner->probe != (RTActorProbe *)0 )

owner->probe->evtMessageOut( msg, RTEventInfo::SendNormal );

#endif

#if USE_THREADS

int need_lock = state == BoundXThread;

if( need_lock != 0 )

RTLayerConnector::lock();

#endif

if( state == Unbound )

{

sender->setError( RTController::noConnect,

RTController::CommSend, port, &index );

#if USE_THREADS

if( need_lock != 0 )

RTLayerConnector::unlock();

#endif

sender->freeMsg( msg );

return 0;

}

remoteActor = remote->getOwner();

msg->setDestination( remoteActor, remote, remoteIndex );

msg->internData();

#if USE_THREADS

remoteActor->context()->receive( msg, sender );

#else

sender->receive( msg, sender );

#endif

if( owner->probe != (RTActorProbe *)0 )

owner->probe->evtMessageOut( msg, RTEventInfo::SendNormal );

#endif

if( state == Unbound )

{

sender->setError( RTController::noConnect,

RTController::CommSend, port, &index );

sender->freeMsg( msg );

return 0;

}

msg->internData();

#if USE_THREADS

// The binding may have been severed while we were busy interning the data.

int need_lock = 0;

switch( state )

{

case Unbound:

sender->setError( RTController::noConnect,

RTController::CommSend, port, &index );

sender->freeMsg( msg );

return 0;

case BoundXThread:

need_lock = 1;

RTLayerConnector::lock();

break;

default:

break;

}

#endif

remoteActor = remote->getOwner();

msg->setDestination( remoteActor, remote, remoteIndex );

#if USE_THREADS

remoteActor->context()->receive( msg, sender );

#else

sender->receive( msg, sender );

#endif

reply.cc

Before Change

After Change

if( end->signalMap != (const int *)0 )

inSignal = end->signalMap[ signal - 1 ];

else

inSignal = signal;

// check to see if this is a reply to an invoked message

if( replyBuffer == (RTMessage *)0 )

{

replyBuffer = controller->newMsg();

if( replyBuffer == (RTMessage *)0 )

{

controller->setError( RTController::noMem,

RTController::CommReply, this, &index );

return 0;

}

replyBuffer->setData( data, type );

replyBuffer->setSignal( inSignal );

replyBuffer->setPriority( msg->getPriority() );

#if OBSERVABLE

remotePort = end->remote;

remoteIndex = end->remoteIndex;

remoteActor = end->state != End::Unbound ? remotePort->getOwner()

: (RTActor *)0;

replyBuffer->setDestination( remoteActor, remotePort, remoteIndex );

controller->debugger()->setTimestamp( replyBuffer, this, index );

if( owner->probe != (RTActorProbe *)0 )

owner->probe->evtMessageOut( replyBuffer, RTEventInfo::SendReply );

#endif

#if USE_THREADS

int need_lock = end->state == End::BoundXThread;

if( need_lock != 0 )

RTLayerConnector::lock();

#endif

if( end->state == End::Unbound )

{

controller->setError( RTController::noConnect,

RTController::CommReply, this, &index );

#if USE_THREADS

if( need_lock != 0 )

RTLayerConnector::unlock();

#endif

controller->freeMsg( replyBuffer );

return 0;

}

remotePort = end->remote;

remoteIndex = end->remoteIndex;

remoteActor = remotePort->getOwner();

replyBuffer->setDestination( remoteActor, remotePort, remoteIndex );

replyBuffer->internData();

#if USE_THREADS

replyBuffer->context()->receive( replyBuffer, controller );

#else

controller->receive( replyBuffer, controller );

#endif

if( end->signalMap != (const int *)0 )

inSignal = end->signalMap[ signal - 1 ];

else

inSignal = signal;

// check to see if this is a reply to an invoked message

if( replyBuffer == (RTMessage *)0 )

{

replyBuffer = controller->newMsg();

if( replyBuffer == (RTMessage *)0 )

{

controller->setError( RTController::noMem,

RTController::CommReply, this, &index );

return 0;

}

replyBuffer->setData( data, type );

replyBuffer->setSignal( inSignal );

replyBuffer->setPriority( msg->getPriority() );

#if OBSERVABLE

remotePort = end->remote;

remoteIndex = end->remoteIndex;

remoteActor = end->state != End::Unbound ? remotePort->getOwner()

: (RTActor *)0;

replyBuffer->setDestination( remoteActor, remotePort, remoteIndex );

controller->debugger()->setTimestamp( replyBuffer, this, index );

if( owner->probe != (RTActorProbe *)0 )

owner->probe->evtMessageOut( replyBuffer, RTEventInfo::SendReply );

#endif

if( end->state == End::Unbound )

{

controller->setError( RTController::noConnect,

RTController::CommReply, this, &index );

controller->freeMsg( replyBuffer );

return 0;

}

replyBuffer->internData();

#if USE_THREADS

// The binding may have been severed while we were busy interning the data.

int need_lock = 0;

switch( end->state )

{

case End::Unbound:

controller->setError( RTController::noConnect,

RTController::CommReply, this, &index );

controller->freeMsg( replyBuffer );

return 0;

case End::BoundXThread:

need_lock = 1;

RTLayerConnector::lock();

break;

default:

break;

}

#endif

remotePort = end->remote;

remoteIndex = end->remoteIndex;

remoteActor = remotePort->getOwner();

replyBuffer->setDestination( remoteActor, remotePort, remoteIndex );

#if USE_THREADS

replyBuffer->context()->receive( replyBuffer, controller );

#else

controller->receive( replyBuffer, controller );

#endif

Addition of new source code files to the TargetRTS

The following new fiiles are added to the TargetRTS:

$ROSERT_HOME\C++\TargetRTS\src\RTAsciiDecoding\get_unsignedlong.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAsciiDecoding\get_unsignedint.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAsciiDecoding\get_unsignedshort.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAsciiDecoding\get_unsignedchar.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAciiEncoding\put_unsignedint.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAciiEncoding\put_unsignedlong.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAciiEncoding\put_unsignedshort.cc

$ROSERT_HOME\C++\TargetRTS\src\RTAciiEncoding\put_unsignedchar.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\log_unsignedint.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\log_unsignedlong.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\log_unsignedshort.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\log_unsignedchar.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\show_unsignedint.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\show_unsignedlong.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\show_unsignedshort.cc

$ROSERT_HOME\C++\TargetRTS\src\RTLog\show_unsignedchar.cc

$ROSERT_HOME\C++\TargetRTS\src\RTObject_class\unsignedint.cc

$ROSERT_HOME\C++\TargetRTS\src\RTObject_class\unsignedlong.cc

$ROSERT_HOME\C++\TargetRTS\src\RTObject_class\unsignedshort.cc

$ROSERT_HOME\C++\TargetRTS\src\RTObject_class\unsignedchar.cc

$ROSERT_HOME\C++\TargetRTS\src\RTTypedValue\unsignedint.cc

$ROSERT_HOME\C++\TargetRTS\src\RTTypedValue\unsignedlong.cc

$ROSERT_HOME\C++\TargetRTS\src\RTTypedValue\unsignedshort.cc

$ROSERT_HOME\C++\TargetRTS\src\RTTypedValue\unsignedchar.cc

Files Updated or Added by this Fix Pack

$ROSERT_HOME/bin/sun5/RoseRT (v6.6.2086)

$ROSERT_HOME/bin/sun5/RoseRT.rsb

$ROSERT_HOME/bin/sun5/RationalRoseRT.tlb

$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/rtjavaui.dll

$ROSERT_HOME/bin/sun5/rtjavaui.rsb

$ROSERT_HOME/bin/sun5/rtrun

$ROSERT_HOME/bin/sun5/EclipseIntegration.rsb

$ROSERT_HOME/bin/sun5/EclipseIntegration.so

$ROSERT_HOME/bin/sun5/modelintRT

$ROSERT_HOME/bin/sun5/modelintRT.rsb

$ROSERT_HOME/bin/sun5/RationalRose.tlb

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_checkin

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_add

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_getcaps

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_checkout

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_getcomment

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_history

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_move

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_remove

$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_rename

$ROSERT_HOME/bin/mw502/lib-sun05_optimized/gdiuser32.lib

$ROSERT_HOME/bin/mw502/lib-sun05_optimized/gdiuser32.rsb

$ROSERT_HOME/bin/mw502/lib-sun05_optimized/kernel32.lib

$ROSERT_HOME/bin/mw502/lib-sun05_optimized/kernel32.rsb

$ROSERT_HOME/bin/mw502/lib-sun05_optimized/libgdiuser32.so

$ROSERT_HOME/bin/mw502/lib-sun05_optimized/libkernel32.so

$ROSERT_HOME/bin/registry/cpp.reg

$ROSERT_HOME/bin/tc/sun5/sun5/terminate.pl

$ROSERT_HOME/C/TargetRTS/codegen/rtlink.pl

$ROSERT_HOME/C/TargetRTS/lib/eCos20020128_uITRON302T.x86-gnu-2.95.3/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/eCos20020128_uITRON302T.x86-gnu-2.95.3/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/eCos20020128_uITRON302T.x86-gnu-2.95.3/main.o

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.sparc-gnu-2.8.1/main.o

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.x86-gnu-3.2/main.o

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTimeC.LIB

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/libObjecTimeCTransport.LIB

$ROSERT_HOME/C/TargetRTS/lib/NoRTOSS.x86-VisualC++-6.0/main.obj

$ROSERT_HOME/C/TargetRTS/lib/NT40S.x86-VisualC++-6.0/libObjecTimeC.LIB

$ROSERT_HOME/C/TargetRTS/lib/NT40S.x86-VisualC++-6.0/libObjecTimeCTransport.LIB

$ROSERT_HOME/C/TargetRTS/lib/NT40S.x86-VisualC++-6.0/main.obj

$ROSERT_HOME/C/TargetRTS/lib/ NT40T.x86-VisualC++-6.0/libObjecTimeC.LIB

$ROSERT_HOME/C/TargetRTS/lib/NT40T.x86-VisualC++-6.0/libObjecTimeCTransport.LIB

$ROSERT_HOME/C/TargetRTS/lib/NT40T.x86-VisualC++-6.0/main.obj

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.ppc603-Diab-4.3f/main.o

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.sparc-gnu-2.95.1/main.o

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTimeC.LIB

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/libObjecTimeCTransport.LIB

$ROSERT_HOME/C/TargetRTS/lib/OSE411T.x86-VisualC++-6.0/main.obj

$ROSERT_HOME/C/TargetRTS/lib/REDHAT73T.x86-gnu-3.2/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/REDHAT73T.x86-gnu-3.2/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/REDHAT73T.x86-gnu-3.2/main.o

$ROSERT_HOME/C/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/REDHAT80T.x86-gnu-3.2/main.o

$ROSERT_HOME/C/TargetRTS/lib/SUN5S.sparc-gnu-2.8.1/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5S.sparc-gnu-2.8.1/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5S.sparc-gnu-2.8.1/main.o

$ROSERT_HOME/C/TargetRTS/lib/SUN5S.sparc-SunC-5.0/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5S.sparc-SunC-5.0/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5S.sparc-SunC-5.0/main.o

$ROSERT_HOME/C/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5T.sparc-gnu-2.8.1/main.o

$ROSERT_HOME/C/TargetRTS/lib/SUN5T.sparc-SunC-5.0/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5T.sparc-SunC-5.0/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/SUN5T.sparc-SunC-5.0/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.m68040-cygnus-2.7.2-960126/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.m68040-cygnus-2.7.2-960126/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.m68040-cygnus-2.7.2-960126/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.ppc-cygnus-2.7.2-960126/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.ppc-cygnus-2.7.2-960126/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.ppc-cygnus-2.7.2-960126/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.x86-cygnus-2.7.2-960126/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.x86-cygnus-2.7.2-960126/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2S.x86-cygnus-2.7.2-960126/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.m68040-cygnus-2.7.2-960126/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.ppc-cygnus-2.7.2-960126/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO2T.x86-cygnus-2.7.2-960126/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.ppc603-Diab-5.0.1/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.ppc603-gnu-2.96/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.simnt-gnu-2.96/main.o

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTimeC.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/libObjecTimeCTransport.a

$ROSERT_HOME/C/TargetRTS/lib/TORNADO22T.simsparcsolaris-gnu-2.96/main.o

$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/SUN5MT.sparc-SunC++-5.0/libDCS.a

$ROSERT_HOME/Connexis/C++/lib/SUN5T.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/TORNADO2T.ppc-cygnus-2.7.2-960126/libDCS.a

$ROSERT_HOME/Connexis/C++/lib/TORNADO2T.ppc860-cygnus-2.7.2-960126/libDCS.a

$ROSERT_HOME/Connexis/C++/lib/TORNADO2T.simso-cygnus-2.7.2-960126/libDCS.a

$ROSERT_HOME/Connexis/Model/DCS.rtmdl

$ROSERT_HOME/Connexis/bin/sun5/ConnexisViewer

$ROSERT_HOME/Connexis/bin/sun5/ConnexisViewer.rsb

$ROSERT_HOME/Connexis/bin/sun5/connexis.rsb

$ROSERT_HOME/Connexis/bin/sun5/libTraceData.so

$ROSERT_HOME/Connexis/bin/sun5/libconnexis.so

$ROSERT_HOME/Connexis/RUP-SE/RUP-SE.mnu

$ROSERT_HOME/C++/TargetRTS/codegen/rtlink.pl

$ROSERT_HOME/C++/TargetRTS/include/RTAsciiDecoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTAsciiEncoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTDecoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTEncoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTLog.h

$ROSERT_HOME/C++/TargetRTS/include/RTObject_class.h

$ROSERT_HOME/C++/TargetRTS/include/RTVersion.h

$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/

$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/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/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/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-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/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/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/ObjecTime.lib

$ROSERT_HOME/C++/TargetRTS/lib/REDHAT73MT.x86-gnu-3.2/ObjecTimeTypes.lib

$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/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/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-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/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/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.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.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.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/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/src/MANIFEST.cpp

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiDecoding/get_unsignedchar.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiDecoding/get_unsignedint.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiDecoding/get_unsignedlong.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiDecoding/get_unsignedshort.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiDecoding/get_long_long.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiEncoding/put_unsignedchar.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiEncoding/put_unsignedint.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiEncoding/put_unsignedlong.cc

$ROSERT_HOME/C++/TargetRTS/src/RTAsciiEncoding/put_unsignedshort.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/log_unsignedchar.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/log_unsignedint.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/log_unsignedlong.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/log_unsignedshort.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/show_unsignedchar.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/show_unsignedint.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/show_unsignedlong.cc

$ROSERT_HOME/C++/TargetRTS/src/RTLog/show_unsignedshort.cc

$ROSERT_HOME/C++/TargetRTS/src/RTObject_class/unsignedchar.cc

$ROSERT_HOME/C++/TargetRTS/src/RTObject_class/unsignedint.cc

$ROSERT_HOME/C++/TargetRTS/src/RTObject_class/unsignedlong.cc

$ROSERT_HOME/C++/TargetRTS/src/RTObject_class/unsignedshort.cc

$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/reply.cc

$ROSERT_HOME/C++/TargetRTS/src/RTProtocol/sendOne.cc

$ROSERT_HOME/C++/TargetRTS/src/RTTypedValue/unsignedchar.cc

$ROSERT_HOME/C++/TargetRTS/src/RTTypedValue/unsignedint.cc

$ROSERT_HOME/C++/TargetRTS/src/RTTypedValue/unsignedlong.cc

$ROSERT_HOME/C++/TargetRTS/src/RTTypedValue/unsignedshort.cc

$ROSERT_HOME/C++/TargetRTS/include/RTAsciiDecoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTAsciiEncoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTDecoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTEncoding.h

$ROSERT_HOME/C++/TargetRTS/include/RTLog.h

$ROSERT_HOME/C++/TargetRTS/include/RTObject_class.h

$ROSERT_HOME/C++/TargetRTS/include/RTVersion.h

$ROSERT_HOME/RUP-SE/RUP-SE.mnu

Additional Information

Contacting IBM Rational Customer Support

Contacting Rational Customer Support 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 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 www.ibm.com/software/support.

IBM® Rational® Rose ® Real Time v2003.06.15b

Fix Pack 1 Release Notes

Scope

Hardware/Software Information

Getting Started

Installation Information

Installation Instructions

Compatibility Issues

With Third-Party Products

Rose RealTime Petal Format or Code Generation Impacts

Rose RealTime TargetRTS Impacts

Rose RealTime Solaris v2003.06.15b Test Fixes Included

Enhancements

Rose RealTime Enhancements included in this Fix Pack

Rose RealTime Toolset

Suppress Code Generation warning “transition has no events” for capsules with ‘abstract’ stereotype

Ability to Browse Generated Makefiles

Defects Fixes

Rose RealTime Defects Fixed in this Fix Pack

Fix Pack Changes to TargetRTS

Changes to existing TargetRTS source code files

sendOne.cc

reply.cc

Addition of new source code files to the TargetRTS

Files Updated or Added by this Fix Pack

Additional Information

Contacting IBM Rational Customer Support

IBM^® Rational^® Rose ^® Real Time v2003.06.15b