Rational® Rose RealTime® Release Notes


Updated:
04/28/2003 10:59:32 AM

This file is located in: <ROSERT_HOME>/rosert_readme.html


Version 2003.06.00


Copyright © 2003 Rational Software Corporation. All Rights Reserved.

This documentation (the "Work") is protected under the copyright laws of the United States and/or other jurisdictions, as well as various international treaties. Any reproduction or distribution of the Work is expressly prohibited without the prior written consent of Rational Software Corporation.

Legal Notices Information


Contents

Introduction

What's New in This Release 

Hardware/Software Information 

Installation, Upgrading, and Licensing  

Compatibility Issues 

General Issues and Known Problems

Documentation Updates 

Contacting Rational Customer Support 

License Support Contact Information

Legal Information

Introduction

This topic is organized as follows:

[Go To Top]

Overview

Thank you for selecting Rational Rose RealTime, the real-time industry's leading environment that unifies software teams by integrating with best-in-class Rational products including Rational ClearCase, Rational RequisitePro, Rational Test RealTime, and Rational SoDA.

The Rational Rose RealTime Readme file contains updates for the version 2003.06.00 product release. For additional information regarding Rational Rose RealTime, see the Rational Rose RealTime Release Notes and the Rational Rose RealTime web site, http://www.rational.com/support

We recommend that you read this Readme file before you install or use Rational Rose RealTime.

Note: In some cases, you may notice discrepancies between the printed documentation, the online documentation, and this Readme file. In these cases, the Readme file located in the directory <ROSERT_HOME>/rosert_readme.html, is the most up-to-date and should be followed.

Please visit the Rational Web site for the latest Release Notes, patches, and other information:

http://www.rational.com/support

If you encounter any problems while installing or running Rational Rose RealTime, review this Readme as well as the Release Notes to see if you have encountered a known problem. If you find a problem that is not yet documented, please call Rational Customer Service so we can investigate it, provide you with a workaround, and track the problem for further action.

See Customer Support for telephone numbers and e-mail addresses of the Rational Customer Service contacts for your region.

[Go To Top]

PLEASE READ FIRST

Please read the following notes before you install Rational Rose RealTime:

[Go To Top]

Reviewing the Latest version of the Release Notes 

To review the latest version of the Release Notes, open the file <ROSERT_HOME>/rosert_readme.html.

You Must Install License Keys to Run this Product

With your software shipment, you received a Welcome letter containing your Start-up License Key Certificates for this product. You need these keys in order to run your software. The start-up keys will expire a few weeks after shipment. Ensure that you request your permanent license keys as soon as they are available. The availability date for your permanent keys is indicated in the top section of your Start-up License Key Certificate.

Please check the Rational Rose RealTime Installation Guide for detailed instructions on how to install your license keys and how to request permanent license keys.

Notice To Customers Running Earlier Releases of Rational Rose RealTime on Windows

You cannot run earlier versions of Rose RealTime with the latest version of Rose RealTime on Windows NT, Windows 2000, and Windows XP Pro.

[Go To Top]

What's New in This Release

Welcome to Rational Rose RealTime Version 2003.06.00. Based on extensive customer consultation and feedback, this release contains many updates and corrections designed to streamline user workflows and enhance developer productivity. Listed below are some of the more visible changes that you will discover in this release. We hope that you find the following enhancements helpful and we look forward to serving your needs in future releases:

[Go To Top]

Improved UML Support

Rational Rose RealTime now supports UML activity diagrams. You can create and view activity diagrams.

User Interface Enhancements

Many new features were added to this release that simplify user workflows associated with editing and navigating models and code. These features include:

  • Improvements to the Find engine to provide easier access and find more things in more places. The engine also now helps find model elements in the navigator and provides better searches of generalizations, messages and sequence diagrams, diagram notes, and connectors.
  • Improvements to model navigation and the ability to modify the design from model element specifications without having to use diagrams. This has been extended to:
  • Modifying class relations and relation ends
  • Adding ports, connectors, and triggers, and other elements
  • You can now navigate models from package specifications with a new tab that lists the contained elements from the package. You can select all references on a component specification using Ctrl-A.
  • Improvements to state diagram editing and manipulation with better support for copy-paste, improved diagram layout and label positioning, and the addition of a tab listing transitions and their trigger conditions on state specifications.
  • Usability improvements for associations. Association ends are now visible in the model navigator as well as in a compartment on classes in class diagrams.
  • Usability improvements to aggregations. It is now easier to modify association ends using the aggregation tool as well as from the relations tab on class specifications.
  • Improved sequence diagram layout, editing and navigation with better support for copy/paste, additional choices for layout, the ability to navigate sequence diagrams using the keyboard, the ability to create sequence diagrams from the capsule structure navigator, and the ability to add create messages to existing interaction instances.
  • Improved support for user defined stereotypes and increased support of built in stereotypes and specialized icons.
  • Many other general improvements such as more consistent menus, additional keyboard shortcuts, more interactive diagram layout, and the ability to print user code when printing a model.
  • Improved requirements modeling with the addition of the Show Participants in Use Case report, the ability to create relationships between use cases, and support for finer granularity requirements traceability with Rational Requisite Pro.

Improved Rational Rose Compatibility

  • Rational Rose model import has been improved including support for importing C++ code associated with Classic C++ Rose models. Rose model artifacts are preserved and displayed in Rose RealTime, including state, activity, sequence, collaboration, class, component, deployment, and sequence diagrams. Because of differences in the diagram formatting between the two tools, some diagrams may appear differently in Rose RealTime than in Rose, but the information is preserved. Rose RealTime now imports models from Rose v2002 without having to convert to Rose98 format.
  • For users migrating their Rose models and code to Rose RealTime, improvements have been made to the sharing and interworking between code and model artifacts from Rose C++ within Rose RealTime . You can reference Rose C++ code from Rose RealTime during build, or you can import the model and C++ code into Rose RealTime for further development.

[Go To Top]

Build and Target Enhancements

Many new features that enhance target support and code centric workflows have been added:

  • It is now easier to edit the generated code with the addition of Browse Header and Browse Body menus to navigate to the generated source code from the model.
  • The generated source code is now easier to read with the ability to turn off the generation of codesync and model tags in the generated code.
  • Rose RealTime can include model documentation in the generated C and C++ code, and can code-sync documentation changes back into the model.

Integration with source debuggers has been enhanced with support for adding source breakpoints to operations:

  • Source debugging integration without UML debugging is now supported. This permits source debugging on targets that do not have TCP/IP support required for UML debugging.
  • It is now possible to create and delete source breakpoint to operations in the UML model and have those appear in an external source debugger.
  • Source breakpoints are easier to manage with the addition of a source breakpoints viewer to view model-level source breakpoints.
  • The watch window has been enhanced to show the class of a variable, and to better display long class names and data values.
  • Improvements to better indicate where a model is halted on a model halt.

Code generation, Target platform and IDE support, and integration with non-Rose RealTime applications has been enhanced:

  • Wind River Tornado 2.2, as well as bare C and C++ environments without an operating system have been added to the list of reference configurations.
  • Rose RealTime code generation has been extended to support a wider range of target applications. Rose RealTime now supports C++ template code generation from Parameterized Classes, state-machine code generation for standalone C and C++ classes, and generation of standalone C and C++ libraries and executables. Rose RealTime can be used to generate standalone software without capsules or a run-time for integration to non-UML based applications.
  • An "External" service API has been added to simplify the integration from non-Rose RealTime threads and Rose RealTime generated capsule-based applications.

There have been numerous other improvements as well:

  • The add class dependencies feature has been improved and now supports a finer granularity of choices.
  • Report file progress is now reported during code generation.
  • It is now possible to build a component directly from a component diagram.
  • The TargetRTS wizard has been updated.
  • Path maps are now available for library scripts.

[Go To Top]

Enhanced Configuration Management Integration and Faster Loading

  • New background synchronization, faster model loading, and toolset shutdown improves support for large scale development have been added to this release of Rose RealTime. Model merging has been improved with enhancements such as addition of the ability to work with Rational ClearCase to support merging of code and text in UML models. In addition, sequence diagrams can now be controlled units letting you create simpler models with faster saves and improved model merging.
  • Model sharing and restructuring has been simplified with the ability to easily change units from shared to owned and back, the addition of a Save As command for controlled units to easily modify the storage location of controlled units, the ability to easily create controlled units in uncontrolled units, the ability to view the ClearCase version tree from within Rose RealTime, and support for ClearCase unreserved checkouts. The Apply Label command now works recursively by model element instead of file system.

Installation and Platform Support

  • Rational Rose RealTime has a single installation process and does not require a separate Companion CD or installation key.
  • Host platform support has been extended with support for Solaris Version 9.

Product Documentation 

Additional product documentation is available in the following locations:

  • All manuals are available online, either in HTML or PDF format. The online manuals are on the Rational Solutions for Windows Online Documentation CD. 
  • For more information about Rational Software technical publications, see: http://www.rational.com/documentation

Hardware/Software Information

For information on hardware and software requirements, see the Installation Guide, Rational Rose RealTime.

Installation, Upgrading, and Licensing

Rational Installer Incompatible with Windows "Change Journal" Feature 

Rational has determined that under certain circumstances file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has the Windows "Change Journal" (log) enabled on it. Therefore, the Rational Installer will not install to such partitions. Rational is actively working with Microsoft to better understand, repair, and/or work around the problem. 

Before installing any Rational Version 2003 product on a computer running Windows 2000, please read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434 for the latest information. Alternatively, you can search the Rational Solutions Knowledge Base at www.rational.com/solutions for the text "Change Journal". 

For information on licensing requirements, see the Installation Guide, Rational Rose RealTime.

Compatibility Issues

For additional information on compatibility issues, see the Product Support section of the Rational Rose RealTime web site at:

http://www.rational.com/support

[Go To Top]

General Issues and Known Problems

Startup, Installing, and Uninstalling

Installing Rational Rose RealTime after Installing Rational Suite DevelopmentStudio

If you install Rational Suite DevelopmentStudio, and then install the Rational Rose RealTime point product, select Add-Ins > Add-In Manager and select the appropriate add-ins, such as SoDA, RequisitePro, and Trace Tool.

Receiving a Warning when Missing the File Objects.dll

When installing Rational Rose RealTime on Windows, or starting Rational Rose RealTime for the first time after installing, you may receive an error message indicating the following:

 "suite objects.dll" cannot be found in the path."

This problem only occurs on Windows NT systems that have had a previous version of Rational Rose RealTime installed. To solve this problem, add "C:\Program Files\Rational\common" to you Path variable.

[Go To Top]

 

Start-up Issues

If you encounter problems starting Rational Rose RealTime, look at the Task Bar and use the Task Manager to see if there are any running copies of Rational Rose RealTime. Terminating all running copies allows new copies of the tool to start properly.

More than one copy of Rational Rose RealTime can run at the same time; however, if startup problems exist, find and terminate any runaway processes.

Note: On UNIX, if a Rational Rose RealTime version 2003.06.00 (version 6.5) exits unexpectedly, prior to starting an earlier version of Rational Rose RealTime (2002.05.xx), we strongly recommend that you delete the windows directory in  your $HOME directory. If you do not delete the windows directory, printing will fail.

Toolset Freezes on Startup

Under certain configurations, when starting Rational Rose RealTime on Solaris and displaying to a Hummingbird Exceed X-server, the "Welcome to ..." window appears momentarily, and then disappears. After this, the main application GUI is locked out and freezes.

The workaround is as follows:

  1. Kill the Rational Rose RealTime process.
  2. Edit the RoseRT.ini file in the ~/.registry.2003.06.00 directory and change ShowStartupDialog=Yes to ShowStartupDialog=No.
  3. Run RoseRT -cleanup.
  4. Run RoseRT.

[Go To Top]

Virus Scanning Applications Affect Startup and Shutdown

On startup or shutdown, virus scanning applications, such as McAfee VirusScan and Trend, will scan the RoseRT.ini file many times, causing a very slow startup or shutdown. To enable a much faster startup and shutdown, exclude the file RoseRT.ini from your virus scanning software.

Uninstall Issues

Occasionally, files are left behind after an uninstall. For example, if a model was saved in one of the Rational Rose RealTime subdirectories, the subdirectory and its parent directories will not be removed. To return your system to a clean state, you must manually remove these directories. 

Note: After you uninstall, your license files will remain in your /common directory, for example, C:/Program Files/Rational/Common. We strongly recommend that you copy the license files to another secure location before deleting the /common directory.

[Go To Top]

Connexis

Running  Connexis Where the Board has Multiple IP Addresses

Connexis may not function as expected when a board has multiple IP addresses (a multi-homed situation). For example, you may have a server (server A) that is accessible by a client (client B) through two IP addresses (address 1 and address 2). If client B assumes that server A is at address 1, based on the address specified in their registerSAP call, the AYA audit message will be sent to that address. When the IAA reply returns from client B, the UDP identifies the IP address of the sender if the IP address is different from the one originally sent. Because  the sender was at address 2 instead of address 1, you may interpret from this information  that client B never received a reply to the AYA for address 1, although the connection continues to be good. Also, with respect to the locator, the published services are only known by one IP address. This means that the client using the locator cannot send to an alternate IP address.

CRM - CRM supports a full address in the same format as used in the registration string. It also supports the specification of a port number. The IP address is determined at startup to be the primary IP address of the board. If no address is supplied, the primary IP address and any free port is used as the listening address.

CDM - When the DCS starts, it calls into the RTS to obtain the IP address for the node that it is running on. This information is stored by the DCS, and it is used at a later time. The CDM transport uses this information, including situations when the user specifies different data using the CNXep parameter. On single-homed machines, this is not an issue because they will be the same (for example, only one IP address is available). However, on multi-homed machines, you may want to use the network connection that was not returned by the call to the RTS.

[Go To Top]

UNIX-Specific

Printing on UNIX

If you click the Print icon in the Toolbar, the Print Topics dialog appears with two options: Print the selected topic and Print the selected heading and all subtopics. Because the Print the selected heading and all subtopics option is not available, it is not possible to print all of the subtopics on Solaris.

 Browser Requirements for UNIX

The Installation Guide, Rational Rose RealTime indicates that the browser requirement for UNIX is Netscape 7.0. This is not correct. The correct browser requirements for UNIX are Netscape 4.78 and Netscape 4.8.

Troubleshooting when the Toolset Freezes on UNIX

In the unlikely event that the  Rational Rose RealTime toolset freezes on UNIX,  the toolset does not respond to user input, or the window will not refresh).

To recover from a toolset freeze:

  1. Run /usr/proc/bin/pstack [Rose RealTime pid] > [outfile].
  2. Run /bin/truss -o [output file] -p [Rose RealTime pid] for 15 seconds.
  3. Kill the Rational Rose RealTime process:

Run kill -SEGV [Rose RealTime pid]

You are also prompted for the following:

  • Information on how to reproduce this problem.
  • To run a resource cleanup utility on your session.
  • To indicate whether you want to be contacted by Rational Customer Service.

If you answer Yes to "Would you like to be contacted by Rational Customer Service", a Rational Customer Support engineer will contact you shortly. You are also prompted to provide the information you gathered in steps 1 through 6.

  1. Click Help > About Rational Rose RealTime and obtain the Rational Rose RealTime build number.
  2. Attempt to reproduce the problem:
  • If you can reproduce the steps that caused the toolset freeze, take note of these steps.
  • If you are unable to reproduce the steps that caused the toolset freeze, any information you can provide on what activities you were doing at the time of the toolset freeze will be helpful to our investigation.
  1. If you use ClearCase, were you in a ClearCase view at the time of the toolset freeze and what version of ClearCase are you currently using?

Forward all of the above information to Rational Customer Service (for contact information, see Rational Customer Support). Ensure that you include "Rose RealTime" in the subject of your email.

[Go To Top]

Rational Rose RealTime Crashes when Debugging Using Tornado 2.2 on UNIX

If you are using debugger integration with Tornado 2.2, as Rational Rose RealTime loads a component instance it will crash. To resolve this problem, go to the WindRiver web site (www.windriver.com) and download the latest patch for Tornado 2.2 that includes an update to the file libwtxapi.so.

Refresh Problems with Exceed

Occasionally, the screen does not refresh completely when running the UNIX version of Rational Rose RealTime on a PC using Hummingbird Exceed.

To change your Exceed settings:

  1. Start Xconfig.
  2. Open the Performance dialog.
  3. Use these settings:

Save Unders = No
Maximum
Backing Store = When Mapped
Default Backing Store
= None
Minimum Backing Store
= None.

Using Hummingbird Exceed 7.1 on a Computer Running Windows Applications and Rational Rose RealTime

If you use a computer running Microsoft Windows XP Pro, Microsoft Office XP Service Pack 1, Microsoft Word (selected as editor for Microsoft Outlook), while Microsoft Outlook is open, if you start Rational Rose RealTime from a Hummingbird Exceed (version 7.1) window, shortly after launching Rational Rose RealTime, Microsoft Outlook, Microsoft Word, and spoolsv.exe CPU activity increases to near 100%. These applications remain at that level for approximately one minute after Rational Rose RealTime closes. Your Rational Rose RealTime session will function normally. However, Microsoft Outlook and any currently open Microsoft Word documents become unusable.

[Go To Top]

Specifying a Location or File Name Containing Spaces (UNIX)

To properly process a location or file name containing one or more spaces, the command line must be properly quoted. You need two levels of quotation marks: the first set of quotation marks (’) wraps the second ("). Specifying this type of quotation marks ensures that the RoseRT script will not interpret the space character, and that it will pass the file name (including space characters) as a single argument to the RoseRT executable.

For example, given the following path and file name:

Test with Spaces/Model with spaces.rtmdl

you would invoke the toolset using the following command:

RoseRT '"Test with Spaces/Model with spaces.rtmdl"'

The file name parameter is quoted as follows:

<open single quote><open double quote> path/filename<close double quote><close single quote>

You must use the quotation marks as described. If you use double quotation marks to wrap the single quotation marks, the string for the file name is processed as a command and it will produce errors.

Starting vi as an External Editor from Rational Rose RealTime

While using Rational Rose RealTime on Solaris version 2.9, if you perform an action that starts the vi editor (the vi editor starts in a separate xterm window), clicking on the "X" on this window displays the following message:

This will terminate you X client session.

If you click OK, the vi xterm window does not close.

[Go To Top]

Unable to Open Some Links in the Online Help

Some links to multimedia content do not work on UNIX. Where possible, an alternative method for opening certain files is included in the online help.

Exceptions When Using Configuration Management in Rational Rose RealTime

If you encounter an exception when working with models under source control on UNIX, your temporary file,  /var/tmp, is likely full.

Case Sensitivity within Paths

The UNIX temporary directory name is translated to lower case. If you set the environment variable TEMP, ensure that the path name is all lower case; otherwise, the directory will not be found. This will cause problems when you open the online Help.

Window Order Policy

When using the CDE window manager, to ensure that the proper Secondary and Transient window policy is in effect, in .Xdefaults, set the following environment variable:

Dtwm*secondariesOnTop: True

Setting this variable to True ensures that an opened secondary window in Rational Rose RealTime for UNIX (such as an external editing window) does not appear behind the main primary window. Since the secondary window is the active window, you may be unable to regain focus of this secondary window.

When using CDE as your XWindow manager, the Allow Primary Windows on Top and Raise Windows When Made Active options are enabled by default. These options should be disabled when setting the Dtwm*secondariesOnTop option to True.

[Go To Top]

Non-GUI-based External Editors

On UNIX, the toolset will freeze if you specified /bin/vi as the external editor and you attempt to launch the external editor from the Code edit window. If you use a non-GUI-based external editor, to ensure that the editor has a terminal (tty) to display to, specify xterm -e /bin/vi.

Setting the Stack Space Limit

Some operations with large models may require a value larger than 32MB to be set manually. If your UNIX administrator set a hard limit on the stack size, you can set a higher limit by using the limit command in csh, or the ulimit command in sh or ksh. Some operations with large models may require a value larger than 32MB to be set manually.

[Go To Top]

Windows-Specific

Using Rational Rose RealTime on Windows XP Pro Configurations

Before installing Rational Rose RealTime on any Windows XP Pro configuration, ensure that you have service pack 1 installed. The Installation Guide, Rational Rose RealTime is incorrect because it indicates that you can install Rational Rose RealTime on Windows XP Pro and Windows XP Pro with service pack 1.

Using Rational Rose RealTime without Appropriate Privileges

To run Rational Rose RealTime on Windows 2000, you must log on with local Administrator or Power User privileges. You will encounter problems running Rational Rose RealTime 2003.06.00 on Windows 2000 if you log on as a user without local  Administrator or Power User privileges. The types of problems include the following:

  • When opening Rational Rose RealTime, you may see the error message, "Failed to Update the System Registry. Try using REGEDIT."
  • The configuration of the Add-in manager cannot be restored.
  • The two menu items Add Class Dependencies and Component Wizard are missing from the Build menu.
  • When creating a component, you are not able to define the Environment in the Component Specification for the C++ TargetRTS.
  • When selecting Rebuild from the Build menu, or clicking the Build tool from the Toolbar, there is no activity.
  • After selecting Run from the Build menu, then clicking Yes to select Build the component, you will receive the error message Operation not allowed.
  • When clicking Help > About, there is no Version or Company information.
  • You will not be allowed to set a Top Capsule in the Component Specification dialog.

[Go To Top]

Build Dependencies on Case-Insensitive File Systems

During a build, Rational Rose RealTime detects and records build dependencies for comparison during subsequent builds. This is done to facilitate build-avoidance by only regenerating or recompiling targets when a build dependency changes. These build dependencies preserve the case of the file names involved, including situations when the underlying file system (for example, NTFS) is case-insensitive. This may cause problems when using names that are distinct within the toolset, and distinct on case-sensitive file systems, but indistinct on case-insensitive file systems. In most cases, the toolset or code-generator will identify and avoid or warn against potential case-insensitive name collisions.

However, some case-insensitive file name collisions cannot be detected. For example, if a component is renamed to "myComponent" to "MyComponent"), a build may incorrectly reuse all previous build results, since the underlying build dependencies will be indistinct according to the file system.

We recommend that you use case-sensitive file-systems wherever possible, and avoid case-insensitive name collisions when you create or rename classes, components or controllable units.

File Association for Compiled Scripts

On Windows NT,  Rational Rose RealTime does not install a file association for compiled scripts (.ebx). This means that compiled script file cannot automatically run by double-clicking on the file from Windows Explorer.

[Go To Top]

Windows CE GetSystemTime() Function Does Not Return Milliseconds

Some Windows CE targets do not return milliseconds in the GetSystemTime() call. This will cause the resolution of the clock, which is used for timers, to be 1 second. If milliseconds timers are required, you must modify the getclock.cc function  to use GetTickCount().

For example, in the getlock.cc file in the directory $RTS_HOME/src/target/WINCE/RTTimerspec/getclock.cc, you will change the GetSystemTime() call and replace it with GetTickCount() as follows:

#include <RTDiag.h>
#include <RTTimespec.h>
#include <windows.h>

void RTTimespec::getclock( RTTimespec & ts )
{
DWORD ticks = GetTickCount();

ts.tv_sec = ( (long)ticks / 1000L );
ts.tv_nsec = 1000000L * ( (long)ticks % 1000L );
}

Note: GetTickCount() is the system uptime and will rap around after 49.7 days. For systems that are up for longer, a combination of GetSystemTime() and GetTickCount() could be used to gain the desired length and resolution of clock time. This implementation will be system dependant.

[Go To Top]

Symbolic Links with TargetRTS

When using LynxOS 3.1.0, do not install Visual Lynx 3.1.0 for Windows NT on a network (NFS) disk. It should only be installed on a local NTFS drive; otherwise, symbolic links to some include directories will not work properly. This will cause compilation errors if you re-compile the TargetRTS.

If you installed Visual Lynx 3.1.0 on a network disk, and if you see compilation errors stating that the include directories netinet/in.h or net/if.h are not found, locate the net and netinet entries in the following directory:

$LYNX_HOME/usr/lynx/3.1.0/ppc/usr/include

If these entries are text files containing the following text: !<symlink>bsd, rename these files, create new symbolic links called 'net' and 'netinet', and have both of them point to the directory called bsd.

[Go To Top]

Spaces in Directory Names

To allow the use of cross-compilers that do not allow spaces in the path names, use the subst command and map a drive to the value of %ROSERT_HOME% after the installation. For example, if you wish to use the K: drive, and your Rational Rose RealTime installation directory is:

ROSERT_HOME=C:\Program Files\Rational\Rose RealTime

You must map this directory to the drive by running the following commands from a console window:

subst K: "%ROSERT_HOME%"
set ROSERT_HOME=K:

Spaces in directory names can cause problems with the following "operating system.compiler library set.development platform:" systems:

  • OSE411T.ppc603-Diab-4.3f.NT4
  • VRTX4T.ppc603-Microtec-1.4.NT40
  • TORNADO2T.ppc630-GreenVX-1.8.9.NT40
  • TORNADO2T.ppc630-GreenVX-2.0.NT40
  • TORNADO2T.m68040-cygnus-2.7.2-960126.NT40
  • TORNADO2T.ppc-cygnus-2.7.2-960126.NT40
  • TORNADO2T.ppc860-cygnus-2.7.2-960126.NT40

For Tornado configurations, you should also use the substituted drive to point to the load script directory when running Target Observability.

On the Detail tab of the Processor Specification dialog, ensure that the Load Script path does not contain any spaces. If spaces are present, when attempting to load the executable in Basic or Debugger-Tornado2 modes, you will receive the error message "Unable to Execute". This does not occur when loading the executable in Manual mode.

Note: Spaces in directory names can also cause problems with ClearMake.

[Go To Top]

Limitations

Limits on the Number of Open Windows

GDI handles are required to create graphic objects (such as windows, menus, cursors, and bitmaps). Opening windows consumes handles. We recommend that you open a reasonable number of windows. This means that on Windows platforms, do not to exceed 200 open windows at any given time.

Limitations in the Specification History List

The following limitations apply to items in the Specification History list:

  • If an RTS object is "locked", it will not be loaded into the Specification History window with the workspace the next time model is opened.
  • RTS objects are visible in the Specification History window after RTS shutdown. However, if you attempt to open this object with no RTS running, the object is removed from the Specification History list (this also occurs when using the Refresh menu item).

[Go To Top]

Online Help

Navigating Through the Online Help

You can either select a topic in the Contents tab or click the Next or Previous buttons, and the topic appears in the main window. As you click Previous, although the previous topic appears in the main window, the incorrect topic may be highlighted in the Contents tab. However, this does not affect the navigation to the selected topic.

Viewing Animated Demonstrations

Rational Rose RealTime includes animated demonstrations of various topics. To see the current list of animated demonstrations, from the Help menu, click Contents. The Rational Rose RealTime Online Help Start Page appears. Click the Animated Demonstrations button for your specific platform.

Viewlets can be viewed on a number of platforms. However, your browser must have Java 1.1 and JavaScript support to play a Viewlet. Additionally, Java must be enabled in your browser.

It is normal for some larger Viewlets to take 10 to 15 seconds to load. Ensure that your browser cache is not disabled; otherwise, some Viewlets may take longer to load.

If launching a Viewlet takes a very long time, or a gray box displays instead of running a Viewlet, try running the Viewlet in your browser by doing the following:

  1. In your browser, navigate to the <ROSERT_HOME >/Help directory.
  2. Select rosert_watch_demos.htm.
  3. Select a Viewlet to run that demonstration.

[Go To Top]

Problems Accessing Rational Rose Help while Running Rational Rose RealTime on Windows

Running Rational Rose RealTime and Rational Rose at the same time may cause Rational Rose not to access its help files. When accessing the online Help for the Rational Rose RealTime toolset, Rational Rose RealTime temporarily replaces a registry key value installed by Rational Rose. This registry key is located in [HKEY_LOCAL_MACHINE\Software\Rational Software\Rose] and is named HelpFileDir. When the toolset starts, it substitutes this key’s value for its own Help directory. The value installed by the Rational Rose installation program is backed up and restored when the last instance of the running toolset exits.

Workaround

You can disable this behavior by setting the value of the key located in [HKEY_LOCAL_MACHINE\Software\Rational Software\Rose RealTime\6.5] whose name is ReplaceRoseHelpDir to No.

Using Context Sensitive Help May Cause Message to Display

If you have version 4.7.3 of the HTML Help compiler installed on your computer, you will receive the following message:

The window name "Default" passed to HH_GET_WIN_TYPE has not been specified.

To solve this problem, ensure that you install  version 4.7.4.

[Go To Top]

Maintaining a Single Favorites List

The Rational Rose RealTime online Help is modularized. If you select Add on the Favorites tab to add current help topic to your favorites list, this entry will only appear in the favorites list for that component of the online Help.

To maintain a single list of favorite help topics:

  1. Use the Search or Index tabs to find the desired online help topic.
  2. Click the Locate button in the Toolbar to see where this help topic appears in the Contents tab.
  3. Close the online help.
  4. Open the online help, using Help > Contents.
  5. From the Contents tab only, find the help topic.
  6. Click the Favorites tab.
  7. Click Add.

Using the Index Tab in the Online Help

When using the Rational Rose RealTime online Help system, if the Index tab has no index entries, close the online Help, and then open the help again. 

[Go To Top]

Toolset (General Issues)

Loading a Workspace may Cause Default Color Settings to Permanently Change

When opening a model and its corresponding workspace, if the workspace specifies a different color scheme for the Line and Fill colors (the third and fourth color boxes in the Custom colors area on the Color dialog box), it will cause the default color settings in the file RoseRT.ini to permanently change.  

To restore the default colors:

  1. Click Tools > Options.

  2. Click the Font/Colors tab.

  3. In the Custom Colors area, set the following:

  • For Line Color, select burgundy.

  • For Fill color, select light yellow.

Alternatively, you can choose not to open the workspace when opening a model.

Do Not Use $& When Defining a PathMap

Do no use $& in your PathMap definitions. If you define a PathMap that includes $&, you will receive a build error similar to the following:

Error: INTERNAL ERROR: File I/O error while trying to open $&/ComponentView.rtcmppkg

Use Caution When Modifying OutPutDirectory

Do not prepend OutputDirectory if ExecutableName appears to be an absolute path.

[Go To Top]

Using Rational Rose RealTime on Non-English Installations Causes Unreadable Font When Viewing Generated Code

When using Rational Rose RealTime on non-English installations, if the font specified is not available, the default font is mapped to an equivalent that is unreadable. To resolve this problem, click Tools > Options, click the Fonts tab, and then select another font.

Unable to use Parameters with the cm_getcaps Script

The cm_getcaps script returns a set of capabilities supported by a source control system. The Rational Rose RealTime toolset does not implement the Parameters button for this operation. This means that you cannot specify any parameters for the UnCheckout operation specified for cm_getcaps scripting.

Problems Compiling Java Models

If you have QuickTime for Java installed, you may encounter problems when compiling your Java models because QuickTime for Java embeds double quotation marks in CLASSPATH. If you remove the double quotation marks, Rational Rose RealTime for Java will compile your models. 

If your CLASSPATH is too long, you will receive the error message "Unable to execute."

[Go To Top]

Problems to Connecting to a Target

If you receive the message "Unable to connect to target" when attempting to connect to a target (both host and embedded), change the value for the Connect Delay box on the Component Instance Specification dialog by increasing the value by two or more seconds.

Using Sequence Diagrams

There are a few conditions under which a Sequence Diagram will incorrectly draw messages and FOCs. If a message or FOC appears to be drawn incorrectly, select the message (or the Message that starts the FOC) and, using the center re-orient handle, move the message slightly. Moving the message causes the Sequence Diagram to recalculate the correct display values for that message.

[Go To Top]

Using the Debugger-xxgdb Tool and Running your Component Instance

When using the xxgdb tool, to enable the breakpoints in gdb, run your component instance, add any breakpoints, and then restart it.

Use of C and C++ Add-ins

You cannot use the C and C++ Add-ins at the same time in Rational Rose RealTime.

[Go To Top]

Code Generator Runs Out of Memory When Generating Very Large Models

When you attempt to generate a very large model, the code generator may run out of memory. To improve memory usage when generating very large models, we recommend that you control all the controllable elements in your model as individual units.

To control elements in your model:

  1. In the Model View tab in the browser, select the model.
  2. Right-click and click either File > Control Units  or File > Control Child Units.
  3. When prompted to control all child units recursively, click Yes
  4. Click Yes on the subsequent confirmation dialog.

For details on controlled units, see the topic, "What is a controllable Element?" in the Guide to Team Development, Rational Rose RealTime.

[Go To Top]

Using the Get and Set Methods in the Attribute and Operation Tools

In the Attribute and Operations tools, you can de-select the Get method and Set method boxes. 

To prevent the deletion of modified code for the Get and Set methods:

  1. Open the Specification dialog for an Attribute or Operation.
  2. Click the General tab.
  3. In the Documentation box, delete the following text:

//GENERATED BY ATTRIBUTE TOOL

or

//GENERATED BY OPERATION TOOL

Deleting this text prevents the deletion of the modifications you made to the Get or Set methods if you de-selected either the Get method or Set method options.

Web Publisher Applet Does Not Load Properly

When using Microsoft Internet Explorer with Microsoft JIT, the Documentation window and the Scroll Bar will not appear the first time you start Rational Rose RealTime. Also, if you use JDK version 1.3.3, the Scroll Bar will not appear.

If you perform a refresh, the Documentation window and the Scroll Bar will appear. If you use appletviewer on JDK version 1.2.2, the Documentation window and the Scroll Bar will appear.

Using the Frameworks Dialog

If you create a framework whose name comes alphabetically before the Empty, RTC, and RTC++, by default, on the Frameworks dialog the highlighted icon is the RTC++ icon, but the text in the Description tab is for the RTC framework. If you click Open, the RTC framework is loaded.

Workaround: Always use your mouse to select a framework, and then click Open.

[Go To Top]

Scoping Descriptors for Nested Classes

If you have the following externally defined classes:

class ExternalClassA
{
   public:
   int x;
   class ExternalClassB
{
public:
int y;
}

}

and model them in Rational Rose RealTime by ExternalClassA and a nested ExternalClassB. For both, generateClass is not selected and generateDescriptor is selected. The type descriptor for ExternalClassB is not generated.

The descriptor for the nested class must be scoped within the top-level class because the nested class is not necessarily public. Since the top-level class is not generated, the descriptor for the nested class (which must be part of the declaration of top-level class), cannot be generated.

[Go To Top]

No Codesync Support for Java

Although codesync options may appear in the menus, Rational Rose RealTime does not support codesync for Java.

Using the GetSelected Functions

In Rational Rose RealTime, the browser selections only apply when the browser window has focus (Rational Rose RealTime uses a different definition of what is selected than Rational Rose). In all other cases, the selection is from the active diagram window (if any). When running a script, you are in the script window; the browser window does not have focus. To return focus to the browser window, you can add a delay to your script.

The GetSelected functions (for example, RoseRTApp.CurrentModel.GetSelectedClasses) only find the selected elements in the model browser if the model browser is active. This means that if you select elements in the browser, then run your script (from the Script Editor, or the Tools menu), the model browser is no longer active (the selected elements are gray, not blue) and these functions will not find anything.

For example, if you open the following script in Rational Rose 2000, select your classes in the model browser, then run the script, it will work.

Sub Main ()

Dim theSelectedClasses As ClassCollection

Viewport.Open
Viewport.Clear

Print "Selected classes from model browser:"
Set theSelectedClasses = RoseApp.CurrentModel.GetSelectedClasses()
If theSelectedClasses.Count > 0 Then

For i = 1 To theSelectedClasses.Count

Print "Class name: "; theSelectedClasses.GetAt(i).Name

Next i

Else

Print " No classes have been selected "

End If

End Sub

However, this script will not work in Rational Rose RealTime. It will only work in Rational Rose RealTime if you make the model browser active. For example, if you add the sleep line to the following script, run the script, select the classes in the model browser, and wait 5 seconds, it will find the selected classes.

Sub Main ()

Dim theSelectedClasses As RoseRT.ClassCollection

Viewport.Open
Viewport.Clear
Sleep(5000)

Print "Selected classes from model browser:"
Set theSelectedClasses = RoseRTApp.CurrentModel.GetSelectedClasses()
If theSelectedClasses.Count > 0 Then

For i = 1 To theSelectedClasses.Count

Print "Class name: "; theSelectedClasses.GetAt(i).Name

Next i

Else

Print " No classes have been selected "

End If

End Sub

[Go To Top]

Using the Find Command May Return Too Many Results

When using the Find command, the results returned may be more than expected. We recommend that you refine your searches whenever possible.

No Support for automatic unwired port registration for Java

In Rational Rose RealTime for Java, rtBound messages do not work because there is no support for unwired port registration.

Error Occurs When Printing a Diagram

If you use an 8 bit, 256 color terminal, you may receive the following error message when you print a diagram from your model if the graphics use the default gray shading:

Error Writing to print file <file_name>.

To print diagrams within your models, you must redefine the default fill color. 

To redefine your fill color:

  1. From the Tools menu, select Options.
  2. Click the Font/Color tab.
  3. Click Fill Color.
  4. Select another color other than the default gray.

[Go To Top]

ROSERT_NO_FEEDBACK - Prompting for Information When an Exception Occurs 

On Windows hosted versions of Rational Rose RealTime, a dialog appears after an exception occurs allowing you to specify information about the steps leading up to the exception, your current system configuration, and whether you would like to be contacted. 

On UNIX hosted versions of Rational Rose RealTime, a script is executed after an exception occurs, which has the same functionality as that provided by Windows hosted versions. Whether you specify the requested information or decide not to specify any information, the script runs RoseRT -cleanup

Note: After any Rational Rose RealTime UNIX exception, you must run RoseRT -cleanup to ensure that any remaining crash artifacts are removed. 

On UNIX hosted versions, if you do not want to be prompted for information after exceptions, set the environment variable ROSERT_NO_FEEDBACK to True. When this variable is set, RoseRT -cleanup will continue to run after an exception. Later, if you want to be prompted to provide feedback, set the variable ROSERT_NO_FEEDBACK to False

ROSERT_TORNADO_TIMEOUT - Modifying the Default Timeout for wtx Commands

By default, when downloading a VxWorks module to a target, the timeout value for wtx commands is set to 30 seconds (ROSERT_TORNADO_TIMEOUT=30000). This default value may not be sufficient when downloading large modules, or when using a slow network. You may receive an error if the timeout value is exceeded. Use this variable to increase the timeout period, if required.

 

[Go To Top]

Documentation Updates

For the most recent documentation updates, visit the Product Support section of the Rational Rose RealTime web site at:

http://www.rational.com/support

Where printed documentation exists, always refer to the online Help or PDF versions of the book for the latest updates. 

[Go To Top]

Contacting Rational Customer Support

If you have questions about installing, using, or maintaining this product, contact Rational Customer Support.
Telephone and fax and email information

Your Location

Telephone

Fax

E-mail

North America

(800) 433-5444
(toll free)

(408) 863-4000
Cupertino, CA

(781) 676-2460
Lexington, MA

support@rational.com

Europe, Middle East, Africa

+31 (0) 20-4546-200
Netherlands

+31 (0) 20-4546-201
Netherlands

support@europe.rational.com

Asia Pacific

+61-2-9419-0111
Australia

+61-2-9419-0123
Australia

support@apac.rational.com


When you contact Rational Customer Support, please be prepared to supply the following information:

  • Your name, company name, telephone number, and e-mail address
  • Your operating system, version number, and any service packs or patches you have applied
  • Product name and release number
  • Your SR# (if you are following up on a previously reported problem)

Telephone, fax, and email information for Rational Customer Service are . If you have problems or questions regarding licensing, please see the tables below:

[Go To Top]

License Support Contact Information

If you have a problem or questions regarding the licensing of your Rational Software products, please contact the Licensing Support office nearest you.

Telephone numbers for license support are listed in the following table. Ask for, or select, Licensing Support.

License Support Telephone and Fax

Region

Telephone Number

Fax Number

Americas

 800-433-5444

781-676-2510

Europe, Israel, and Africa

+31 (0)20 4546 200

+31 (0)20 4546 202

North Asia Pacific

(Mainland China,

Hong Kong, Taiwan)

+852 2143 6382

 

+852 2143 6018

 

Korea

+82 2 556 9420

+82 2 556 9426

South Asia Pacific Australia, New Zealand, Malaysia, Singapore, Indonesia, Thailand, The Philippines, Vietnam, Guam and India

+61-2-9419-0111

+61 2 9419 0123

Japan

+81 3 5423 3611

+81 3 5423 3622

Email addresses for license support are listed in the following table.

License Support Email
Region Email Address

North, Central, and South America 

license@rational.com

Europe, Middle East, and Africa 

license@europe.rational.com

Asia Pacific 

license@apac.rational.com

Asia Pacific
(Mainland China, Hong Kong, and Taiwan) 

license@china.rational.com 

Asia Pacific
(Korea) 

license@apac.rational.com

Asia Pacific
(Japan) 

license@japan.rational.com

[Go To Top]

Legal Notices Information

Legal Notices

©1993-2003, Rational Software Corporation. All rights reserved.

This manual (the "Work") is protected under the copyright laws of the United States and/or other jurisdictions, as well as various international treaties. Any reproduction or distribution of the Work is expressly prohibited without the prior written consent of Rational Software Corporation.


Rational, Rational Software Corporation, the Rational logo, Rational Developer Network, AnalystStudio, ClearCase, ClearCase Attache, ClearCase MultiSite, ClearDDTS, ClearGuide, ClearQuest, ClearTrack, Connexis, e-Development Accelerators, DDTS, Object Testing, Object-Oriented Recording, ObjecTime, ObjecTime Design Logo, Objectory, PerformanceStudio, PureCoverage, PureDDTS, PureLink, Purify, Quantify, Rational Apex, Rational CRC, Rational Process Workbench, Rational Rose, Rational Suite, Rational Suite ContentStudio, Rational Summit, Rational Visual Test, Rational Unified Process, RUP, RequisitePro, ScriptAssure, SiteCheck, SiteLoad, SoDA, TestFactory, TestFoundation, TestStudio, TestMate, VADS, and XDE, among others, are trademarks or registered trademarks of Rational Software Corporation in the United States and/or in other countries. All other names are used for identification purposes only, and are trademarks or registered trademarks of their respective companies.

Portions covered by U.S. Patent Nos. 5,193,180 and 5,335,344 and 5,535,329 and 5,574,898 and 5,649,200 and 5,675,802 and 5,754,760 and 5,835,701 and 6,049,666 and 6,126,329 and 6,167,534 and 6,206,584. Additional U.S. Patents and International Patents pending.

U.S. GOVERNMENT RIGHTS. All Rational software products provided to the U.S. Government are provided and licensed as commercial software, subject to the applicable license agreement. All such products provided to the U.S. Government pursuant to solicitations issued prior to December 1, 1995 are provided with “Restricted Rights” as provided for in FAR, 48 CFR 52.227-14 (JUNE 1987) or DFARS, 48 CFR 252.227-7013 (OCT 1988), as applicable.

WARRANTY DISCLAIMER. This document and its associated software may be used as stated in the underlying license agreement. Except as explicitly stated otherwise in such license agreement, and except to the extent prohibited or limited by law from jurisdiction to jurisdiction, Rational Software Corporation expressly disclaims all other warranties, express or implied, with respect to the media and software product and its documentation, including without limitation, the warranties of merchantability, non-infringement, title or fitness for a particular purpose or arising from a course of dealing, usage or trade practice, and any warranty against interference with Licensee’s quiet enjoyment of the product.

Third Party Notices, Code, Licenses, and Acknowledgements
Portions Copyright ©1992-1999, Summit Software Company. All rights reserved.

Microsoft, the Microsoft logo, Active Accessibility, Active Client, Active Desktop, Active Directory, ActiveMovie, Active Platform, ActiveStore, ActiveSync, ActiveX, Ask Maxwell, Authenticode, AutoSum, BackOffice, the BackOffice logo, bCentral, BizTalk, Bookshelf, ClearType, CodeView, DataTips, Developer Studio, Direct3D, DirectAnimation, DirectDraw, DirectInput, DirectX, DirectXJ, DoubleSpace, DriveSpace, FrontPage, Funstone, Genuine Microsoft Products logo, IntelliEye, the IntelliEye logo, IntelliMirror, IntelliSense, J/Direct, JScript, LineShare, Liquid Motion, Mapbase, MapManager, MapPoint, MapVision, Microsoft Agent logo, the Microsoft eMbedded Visual Tools logo, the Microsoft Internet Explorer logo, the Microsoft Office Compatible logo, Microsoft Press, the Microsoft Press logo, Microsoft QuickBasic, MS-DOS, MSDN, NetMeeting, NetShow, the Office logo, Outlook, PhotoDraw, PivotChart, PivotTable, PowerPoint, QuickAssembler, QuickShelf, RelayOne, Rushmore, SharePoint, SourceSafe, TipWizard, V-Chat, VideoFlash, Visual Basic, the Visual Basic logo, Visual C++, Visual C#, Visual FoxPro, Visual InterDev, Visual J++, Visual SourceSafe, Visual Studio, the Visual Studio logo, Vizact, WebBot, WebPIP, Win32, Win32s, Win64, Windows, the Windows CE logo, the Windows logo, Windows NT, the Windows Start logo, and XENIX, are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or in other countries.

Sun, Sun Microsystems, the Sun Logo, Ultra, AnswerBook 2, medialib, OpenBoot, Solaris, Java, Java 3D, ShowMe TV, SunForum, SunVTS, SunFDDI, StarOffice, and SunPCi, among others, are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Purify is licensed under Sun Microsystems, Inc., U.S. Patent No. 5,404,499.

Licensee shall not incorporate any GLOBEtrotter software (FLEXlm libraries and utilities) into any product or application the primary purpose of which is software license management.
BasicScript is a registered trademark of Summit Software, Inc.

Design Patterns: Elements of Reusable Object-Oriented Software, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides. Copyright © 1995 by Addison-Wesley Publishing Company, Inc. All rights reserved.

Additional legal notices are described in the legal_information.html file that is included in your Rational software installation.

[Go To Top]