Transition Notes

• Installation and Startup Issues
• General Issues
• Integrations Issues
• Online Help Issues
• Windows 2000 Issues
• UNIX Issues
• RQA-RT
• Updates
• Problems Addressed

• File Association for Compiled Scripts
• Suite Objects.dll Not Found
• Start-up Problems
• Error Occurring During Installation into a Double-Byte Folder
• Uninstall

• Rational Rose RealTime Professional Edition:
  • Installing Rational Rose RealTime Professional Edition on HP-UX

[Go To Top]

File Association for Compiled Scripts

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

[Go To Top]

Suite Objects.dll Not Found

When installing on Windows NT, or attempting to run Rose RealTime, an error message sometimes occurs indicating that "suite objects.dll " cannot be found in the path.

Adding "C:\Program Files\Rational\common" to the path will fix this problem.

This problem only occurs on Windows NT systems that have had a previous version of Rose RealTime installed.

[Go To Top]

Start-up Problems

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

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

[Go To Top]

Error Occurring During Installation into a Double-Byte Folder

An error may appear when installing Rational Rose RealTime into a double-byte folder. Please use the following workaround. 

1. After you installed Rational Rose RealTime, copy the Web Publisher files to a non-double byte folder. For example, move
   $ROSERT_HOME\WebPublisher to C:\WebPublisher. 

2. Select Start > Run. 

3. Type "regsvr32 C:\WebPublisher\rosertwebpub.dll" (where C:\WebPublisher is the non-double byte folder to which you copied the Web Publisher file) and click OK. 

4. Select Start > Run again. 

5. Type "regedit" and click OK. 

6. In the Registry Editor, open the folder for "RoseRT Web Publisher" under the following:

 HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\Rose RealTime\6.4\Addins. 

1. Change the entry "InstallDir" to the new location (for example, "C:\WebPublisher\win32"). 

[Go To Top]

Uninstall

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

[Go To Top]

Unique Ids

Unique ids are unique internal names associated with model elements. They are used internally by Rational Rose RealTime, and not all model elements require unique ids. Rational Rose RealTime includes a feature that helps Model Integrator by generating unique ids for those model elements that would otherwise not require them, for internal use. For Model Integrator, an element with a unique id is easier to merge.

For information on how and when to enable the Unique ids, see Model Specification in the online Help.

RRTEI users will find traceability easier when they set this option. Unique ids improve the traceability of model elements of other tool integrations that use RRTEI.

It is necessary to plan and choose when to incorporate the new unique ids into the project model since virtually all controlled units will be modified implicitly. Additionally, the generated new ids are dependent on time and location. For example, generating unique ids for a given model at different times, or on different machines, produces different ids.

Caution: We strongly recommend any team involved in parallel development use this option.

Caution: Setting this option creates unique ids for model elements that currently do not have them. This typically affects most of the model, so you will be prompted to check out those parts when setting this option.

When saving the model, the size of the affected file increases by approximately 20%, and the time to load the model also increases.

Caution: Do not set this option in multiple streams, otherwise, objects with similar characteristics will be treated differently since their unique id's will differ.

For more information about when and how to use this feature, see the Guide to Team Development for Rational Rose RealTime.

Caution: If you clear this option, your merge results will not be as reliable.

[Go To Top]

Probes

When a message hit causes a probe to halt the execution of a running model, there is no way of finding out which probe in the model causes the model to stop executing. To determine which probe execution is halted on, open trace windows for each enabled probe.

[Go To Top]

License Manager

When there is no License manager running, a pop-up window appears indicating that the toolset cannot obtain a license at that time.

[Go To Top]

Changes to Code that Uses Default Arguments

ObjecTime Developer models which used the RTTimespec constructor with only one parameter, as in the following code:

timer.informIn(RTTimespec(2));

will result in a compile error after conversion of the model to Rational Rose RealTime. The compile error will appear something like:

 ..\rtg\Driver.cpp(67) : error C2440: 'type cast' : cannot convert from 'const int' to 'struct RTTimespec'

 No constructor could take the source type, or constructor overload resolution was ambiguous.

The reason is that in ObjecTime Developer, the RTTimespec constructor included default arguments, that is, RTTimespec (long=0, long=0). The default constructor values are not supported with RTTimespec in Rose RealTime. Any code that made use of the default arguments needs to be changed to supply both constructor arguments. For example:

OTD = RTTimespec (2);

must be changed to:

RRT = RTTimespec (2, 0);

[Go To Top]

Spaces in Directory Names

If you want to use cross-compilers that do not allow spaces in the path name, after you install Rational Rose RealTime on Windows NT, use the subst command and map a drive to the value of %ROSERT_HOME%. 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, the Load Script path should not contain any spaces. If spaces are present, when attempting to load the executable in Basic or Debugger-Tornado[2] modes, the error message, Unable to Execute appears. This does not occur when loading the executable in manual mode.

Spaces in directory names can also cause problems with ClearMake.

[Go To Top]

Too Many Files Open

You can have a maximum of 1024 file pointers open simultaneously.

[Go To Top]

Exceptions when using Configuration Management in Rose RealTime

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

[Go To Top]

Executing Component Instances

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 by increasing the value by two or more seconds.

[Go To Top]

Sequence Diagrams

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

It is not possible to provide a global ordering of messages since Rose RealTime allows messages to cross
in sequence diagrams; the numbers provided are not intended to be a global order.

[Go To Top]

Naming Association Roles within a Collaboration Diagram

All association roles must have unique names within a collaboration diagram. If you load a model that has one or more collaboration diagrams with non-unique association role names, the names are modified (to make them unique) when the model loads. You will receive a warning message similar to the following: 

Renamed Association Role "c1" to "c1_0" in class/package "Logical View"

Only after you save the model will the changes be made, and be permanent.

[Go To Top]

Build Dependencies on Case-Insensitive File Systems (NT only)

During a build, 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 filenames involved, even when the underlying file-system (for example, NTFS) is case-insensitive. This may cause problems when using names which are distinct within the toolset, and distinct on case-sensitive drives, but indistinct on case-insensitive drives. In most cases, the toolset or code-generator will identify and avoid or warn against potential case-insensitive name collisions.

However, some case-insensitive filename collisions cannot be detected. For example, if a component is renamed to something that is case-insensitive-identical (for example, renaming from "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.

Users are advised to use case-sensitive file-systems if possible. Otherwise, users should avoid case-insensitive name collisions when they create or rename classes, components or controllable units.

[Go To Top]

Using the Debugger-xxgdb Tool and Running your Component Instance

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

[Go To Top]

Running Multiple Sessions on the Same Workstation

If you experience instability when running multiple Rose RealTime sessions on the same workstation, limit your usage to a single session at any given time.

[Go To Top]

Use of C and C++ Add-ins

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

[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 have installed Visual Lynx 3.1.0 on a network disk, and if you see compilation errors stating that include directories netinet/in.h or net/if.h are not found, locate the entries net and netinet 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 and create new symbolic links called 'net' and 'netinet'  that both point to the directory bsd.

[Go To Top]

McAfee VirusScan Affects Startup and Shutdown Performance

On Startup of shutdown, McAfee VirusScan will scan the RoseRT.ini file approximately 426 times, causing a very slow startup or shutdown.

To enable a much faster shutdown, exclude the INI extension from the McAfee VirusScan Program File Extensions list.

[Go To Top]

Creating Capsules with the Same Name in Different Packages

While Rose RealTime allows users to create capsules with the same name in the different packages, Target Observability for both C++ and Java may confuse such capsules.

As a temporary workaround, we recommend either renaming such capsules to have unique names (preferred method), or placing the capsules to be observed directly under the Logical View.

[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:

[Go To Top]

Window Order Policy

When using the CDE window manager, to ensure that the proper Secondary and Transient window policy is in effect, disable Allow Primary Windows On Top in the CDE style Manager, and 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 get caught behind the main primary window. Since the secondary window is the active window, you are unable to regain focus of this secondary window.

If Dtwm*secondariesOnTop is not set to True, since the secondary window is the active window, you may not be able to regain focus of this secondary window when it goes behind the primary window.

[Go To Top]

Running Model Examples

When trying to compile some example model installed with Rational Rose RealTime, such as SocketInterfaceExample, you must have the Rational Rose RealTime Companion Products installed to successfully compile example models.

[Go To Top]

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

In the Attribute and Operations tools, you can de-select the Get method and Set method boxes. If you want to prevent deletion of modified code for the Get and Set methods, do the following:

[Go To Top]

Error Loading Large Models from ClearCase - Windows

If you have problems loading large models from ClearCase - that is, it takes a long time or an empty model appears - check your error messages. It may be because there are too many files open.

[Go To Top]

RequisitePro

When the RequisitePro add-in is enabled in Rose RealTime, there is a known problem with File > Save As.

As RequisitePro attempts to save the units of RTClasses and RTCClasses, there will be numerous prompts, such as "File <path> is write protected by the operating system. Continue?"

[Go To Top]

SoDA

SoDA can be installed without Rose 2001 and will continue to function with Rose RealTime. However, when run from Rose RealTime, the menu of templates presented are from Rose, not Rose RealTime. Some of these templates will issue errors.

For the latest updates on SoDA integration, refer to the product support page at:

http://www.rational.com/support

Note: To install the Rose RealTime domain for SoDA, you need to select the Full/Customer install option during your SoDA installation.

[Go To Top]

Problems Accessing Rose Help when Concurrently Running Rose RealTime on Windows NT

Problem

Running both Rose RealTime and Rose may cause Rose not to access its help files.

Explanation

To enable the help for the Rose add-ins to be accessible when used from within the Rose RealTime toolset, 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.4] 

whose name is ReplaceRoseHelpDir to No.

[Go To Top]

Java Reference

The formatting of some text (including code) may not appear correctly in the Java Reference online Help book. Please refer to either the jguide.pdf file or the Java Reference book to verify the content.

[Go To Top]

Navigating through the QuickStart Tutorial 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.

Note: If 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 navigating to the selected topic.

[Go To Top]

Viewing Animated Demonstrations

Rational Rose RealTime includes animated demonstrations of various How Do I... topics, called Viewlets. 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.

Note: 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:

[Go To Top]

Executing the Current Version with a Previous Version

The current and previous toolsets do not work together by default, due to sharing the MWRPC_ENDPOINT and MWSHM_KEY environment variable settings. These settings are only calculated if the environment does not already have them set.

[Go To Top]

Refresh Problems with Exceed

The screen sometimes does not refresh completely when running the UNIX version of Rose RealTime and displaying it on a PC using Hummingbird Exceed.

[Go To Top]

HP-UX Make Dependency Filename Restriction

On the HP-UX platform, the HP-UX Make restricts dependency filenames to 160 characters. We recommend the use of Gnu-Make to work around this problem. Alternatively, you may shorten the path names to your class files to avoid this issue.

[Go To Top]

Non-GUI-based External Editors

On UNIX, the toolset will freeze when the user specifies /bin/vi as the external editor and then tries to launch the external editor from the code edit pane. If you are using a non-GUI-based external editor, this should be specified using xterm -e /bin/vi so that the editor has a terminal (tty) to display to.

[Go To Top]

Case Sensitivity within Paths

The UNIX temporary directory name is translated to all lower case. If you set the environment variable TEMP, make sure the path name is all lower case or the directory will not be found. This will cause problems when Help is started.

[Go To Top]

[Go To Top]

Online Help

Context-sensitive help on UNIX may not invoke the correct help page

Context-sensitive help on UNIX may not invoke the correct help page. The workaround is to use the advanced search capabilities of the online-help to find the appropriate topic.

Cannot open some links with online help

Some links to multimedia content do not work on UNIX.

[Go To Top]

Lost Information in "To Port" for a Message

If you load an LF-file into Rational Rose RealTime and perform the conversion, there are a number of instances where the
information on the To Port of a message is lost. In Rational Rose RealTime 2002.05.00, the conversion was enhanced to determine the receiver port on any message sent between two instances that have a direct logical connection from the sender port. This calculation increases the time
required to perform the conversion. Diagrams which have messages between instances that skip relay ports will continue to require the receiver port to be entered manually.

When running RQART from a script using the RunVerifyBehavior method do not use the -runScriptAndQuit command line option to cause RoseRT to exit once the script is complete. Since Verify Behavior runs asynchronously after RunVerifyBehavior is called this will cause RoseRT to exit before Verify Behavior is complete. Use the szScriptOnCompletion parameter of RunVerifyBehavior to specify a script that contains the actions that you want to occur after Verify Behavior is complete. This script can exit RoseRT using the Exit method.

[Go To Top]

Creation of Container Capsules

RQA-RT does not automatically create container capsules for a nested capsule when the container is not included in the Sequence Diagram. 

[Go To Top]

Converting MSCs in Rational Rose RealTime using the RQA-RT

Problem

Many MSCs have a variable of the same name (prepareSetupReqD), but they can have a different type. When RQA-RT synthesizes these attributes from the multiple driver instances and attempts to generate one test driver, there is a name conflict and it selects the last Sequence Diagram attribute's type as the type for the attribute of the test driver class.

Background

In ObjecTime Developer, attributes are a characteristic of MSCs; each MSC can have its own attributes. These attributes can be considered variables for the environment which acts as a driver in TestScope.

When the MSCs are converted in Rational Rose RealTime using the RQA-RT conversion tool, each MSC is converted to a Sequence Diagram. In this Sequence Diagram, what was the environment in ObjecTime Developer is now a driver capsule that is automatically created. The interaction instance (of the driver) in the sequence diagram has attributes which were converted from the MSC in ObjecTime Developer.

This newly created interaction instance is set as a driver during the Verify Behavior operation. As a result, a new RQADriver is created. 
For Example:

Seq1:: driver has an attribute xAttrib of type Xtype
Seq2:: driver has an attribute xAttrib of type Ytype

Test harness generates a driver class with an attribute xAttrib of type Xtype or Ytype. The compilation occurs and the result will be many errors in the test harness. The errors occur because some of the action code interprets xAttrib as
type Xtype and some as type Ytype. 

Workaround

Run the Sequence Diagrams from separate test harnesses. This means that you will have completely separate components and will have to
compile again.

[Go To Top]

Code Generator Updates

[Go To Top]

Model File Syntax

The syntax for model files has changed in Rational Rose RealTime version 2002.05.00. As a result, when opening a model in Rational Rose RealTime 2001A.04.00 that was created in Rational Rose RealTime 2002.05.00, you may receive syntax errors.

[Go To Top]

.jar Files

TargetRTS Classes for RTJava applications are now bundled into a single .jar file rather than directory. You may need to modify CLASSPATH in your environment, as well as other locations where Java code is compiled or run outside the toolset. If you run within the toolset, this modification is automatically done for you.

[Go To Top]

rtsetup.pl File

There is a new Perl script, called rtsetup.pl, which you can use to reuse the environment used to build the TargetRTS. The primary usage will be in the CompilationMakeCommand: you want to prefix the existing command with the following:

rtperl -S rtsetup.pl

For example, if the command was

$defaultMakeCommand

it becomes

rtperl -S rtsetup.pl $defaultMakeCommand

The script examines the generated makefile to determine the TargetConfiguration specified for the current component, executes $RTS_HOME/config/<TargetConfiguration>/setup.pl to recreate the environment required to build the TargetRTS, and then, in that environment, executes the command that follows.

It is useful for designers who must build components for different targets which depend on conflicting environment variable definitions.

[Go To Top]

Hot Link for Call Message Operations

For a Sequence diagram, if you open the Call Message Specification dialog and select an Operation from the Detail tab, the label opposite the Operation box become a hot link to that operation.

On Windows hosted versions of 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 opt not to specify any information, the script runs RoseRT -cleanup. After any 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 an environment variable ROSERT_NO_FEEDBACK to True. Even when this variable is set, RoseRT -cleanup will run after an exception. Later, if you want to be prompted to provide feedback, unset the ROSERT_NO_FEEDBACK variable.