Rational Rose RealTime

March 1999

• Chapter 1 - Introduction
• Chapter 2 - Platform and toolchain requirements
• Chapter 3 - Licensing requirements
• Chapter 4 - Integration notes
• Chapter 5 - Troubleshooting
• Chapter 6 - Known problems and limitations
• Chapter 7 - Documentation Updates
• Chapter 8 - Technical support

Chapter 1 - Introduction

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

Please read this release note before you install or use Rational Rose RealTime.

Note: In some cases, you may note discrepancies between the printed documentation and the online documentation. In these cases, the online documentation is the most up-to-date and should be followed.

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

www.rational.com/products/rosert

If you encounter any problems while installing or running Rose RealTime, please check here first to see if you encountered a known problem. If you find a problem that is not yet documented, please call Rational Technical Support so we can investigate it, provide you with a workaround, and track the problem for further action.

Contact information for this release is in "Technical Support" on page 23.

PLEASE READ FIRST

You Must Install License Keys to Run this Product!

With your software shipment, you receive an envelope 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. Be sure to 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 Licence Key Certificate.

Please check the Rational Rose Realtime Install Guide for detailed instructions on how to install your start-up license keys and how to request your permanent license keys.

Notice To Rational Beta Customers
IF YOU WERE A BETA CUSTOMER FOR RATIONAL ROSE REALTIME, PLEASE UNINSTALL BOTH THE WINDOWS AND UNIX COMPONENTS OF THE BETA VERSION FROM YOUR SYSTEM.

Chapter 2 - Platform and toolchain requirements

Platform requirements — Windows NT

The minimum supported configuration for running Rose RealTime 6.0 on Windows NT is:

• Windows NT 4.0, Build 1381 with service pack 3 or service pack 4.
• Minimum Pentium 150 MHz or faster CPU.
• Minimum 64 MB of RAM, we recommend 128 MB.
• Minimum 65 MB of disk space for the Rose RealTime installation.
• Minimum 800 * 600 * 256 color video resolution or better.
• Postscript printer for printing.
• Browser requirement - Internet Explorer 4 or Netscape Navigator 4. Internet Explorer 4 is recommended.

Platform requirements — Solaris

The minimum supported configuration for running Rose RealTime 6.0 on Solaris is:

• Solaris 2.5.1 or Solaris 2.6.
• We recommend 128 MB of RAM.
• Minimum 150 MB of disk space for the Rose RealTime installation.
• Postscript printer for printing.
• Browser requirement - Netscape Navigator 4.

HTML Browser

An HTML browser is required to access the online Help provided with Rose RealTime. Supported browsers are:

• Netscape Navigator version 4.04 or greater, we recommend version 4.07 or greater.
• Internet Explorer version 4 or greater.

For optimum online Help performance, use Internet Explorer 4.

Compiler

You must have a C++ compiler installed on your system to make use of the code generation and execution capabilities for Rose RealTime. Different compilers are required for host workstation and for embedded system targets. The list of supported compilers and targets is provided in the Getting Started Guide.

Real-time Operating System

If you are planning to deploy your model on a real-time operating system, your operating system, hardware and tool lineup must be one of the supported lineups listed in the Getting Started Guide. If you do not have a supported lineup, you may be able to get support for your lineup from a Rational RoseLink partner, or by customizing the Rose RealTime Services Library for your target. See the C++ Target Guide for instructions on customizing the Services Library and compiling for new target platforms.

Chapter 3 - Licensing requirements

Please refer to the Install Guide for instructions on installing a Startup License on page 13 and on obtaining Permanent License Keys on page 15.

Note: Do not follow the instructions on the Rational Start-up License Certificate or on the envelope in which the certificate is delivered to you.

Chapter 4 - Integration notes

Requisite Pro 4.0

Before running Requisite Pro 4.0 (Req Pro) with Rose RealTime, you must first start Rose RealTime with a command line option so that the emulated REI is activated.

Note: You cannot start Rose RealTime from Req Pro because of the way in which it starts Rose. Req Pro does not use the automation interface, but rather relies on the file association mapping.

This can be done by creating a shortcut to the application and then editing the properties. Add the option -emulateREI to the command target in the shortcut

%ROSERT_HOME%\bin\win32\RoseRealTime.exe -emulateREI.

When Rose RealTime is started, it will register a Rose98 compatible REI. The reason this is not done by default is so that Rose98(I) and Rose RealTime can coexist on the same machine.

The current integration between Rose RealTime and the Req Pro synchronizer does not support sequence diagrams. That is, it is not possible to have Requisite Pro retrieve or create sequence diagrams as part of a model to database synchronization. This will be addressed as part of a future release.

Migrating from Rational Rose and ObjecTime Developer

In order to migrate models into Rose RealTime from either Rational Rose or ObjecTime Developer when models were previously stored in a configuration management system, the model must be brought into the Rational Rose or the ObjecTime Developer tool and written out to a single file. Please refer to “Model upgrades and conversions” on page 15 of the Getting Started with Rational Rose RealTime guide.

When importing a model from Rose 98/98i into Rose RealTime, you are encouraged to resolve any model errors in Rose98 (Tools > Check Model) before trying to import the model. In particular it is important to fix unresolved references. In general, Rose98 does not care as much about unresolved references; however, they are very important in Rose RealTime as they can result in incomplete code generation and compilation errors.

In order to export the ObjecTime model in a format which is readable by Rose RealTime, a patch must be applied to the 5.2 or 5.2.1 toolset to format the file in a single linear form file with all the required information. The patch will be made available by Customer Support for both the 5.2 and 5.2.1 product release only.

Once the model has been imported into Rose RealTime, it can then be stored in the configuration management system.

Configuration management

In order to avoid time-outs while saving larger models to a CM system, these models should be split up into separate control units. Set the "Control all units" check box in the Model Specification general tab.

Naming directories

Avoid using spaces in directory names if you plan to integrate with Tornado, OSE or VRTX embedded operating systems.

Microsoft development environment

We recommend that you install the latest service packs available from Microsoft for Visual Studio or Visual C++.

Chapter 5 - Troubleshooting

Troubleshooting UNIX

This section lists common problems and errors encountered when installing and running Rose RealTime. With the description of the problem is the suggested course of action required to overcome the problem.

CD read errors

If you are installing from a CD-ROM drive across the network and you are using a fast CD-ROM device, you may see some tar read errors during the installation process. To avoid the problem, either copy the CD contents to a local disk drive and run the installation from there, or run setup.sh from the machine to which the CD-ROM drive is connected.

Supported Window Managers

Rational Rose RealTime supports the following window managers under Solaris with the exceptions listed below.

• olwm (Open Look Window Manager)
• olvwm (Open Look Virtual Window Manager)
• twm (Tab Window Manager)
• dtwm (Desk Top Window Manager)

Unsupported Combinations

Dtwm cannot be used if Rose RealTime is being executed on a remote host. This includes the use of dtwm on an Xterm.

Installation

Rose RealTime has “secondary windows” such as specification dialogs, which should remain above the main tool window. Configure your window manager as described below. See window manager documentation to make these settings system-wide defaults.

Olwm, olvwm

Add this line to your.Xdefaults file

OpenWindows.KeepTransientsAbove: True

then run

xrdb ~/.Xdefaults

Twm

Twm does not support keeping secondary windows on top of a main application window. If you use twm, place specification dialogs where they will not be covered up. If a specification dialog does not come up when an "Open Specification" menu item is selected, move the main window aside to look for it.

Dtwm

In the Style Manager - Window tool, ensure that "Allow Primary Windows On Top" is not selected.

To set this up as the default, add this line to your .Xdefaults file

Dtwm*secondariesOnTop: True

xrdb ~/.Xdefaults

Dtwm

Dtwm is the standard CDE window manager. If it is used with a remote host, specification dialog buttons do not appear.

Xterm Use

On an Xterm, dtwm should work with the following configuration:

• In Style Manager - Window, set
• Point in Window to Make Active
• Raise Window When Made Active
• Use RoseRealTime -cde.

Using -cde will give Rose RealTime a Windows window frame. The tool will remain on top of all other windows and cannot be moved, sized or minimized when the tool is busy.

Console Use

Dtwm can be used from one Solaris console remotely to another host if dtwm is started through OpenWindows instead of CDE. Set up your .xinitrc file to call dtwm. Then at login, select
Options>Session>OpenWindows Desktop

Mwm

Mwm is not supported for this release of Rose RealTime.

Online Help

If the UNIX platform in which the toolset is running does not have a browser installed an error message will be displayed when Help is launched.

Note: Do not run more than one Help session at a time.

Troubleshooting Windows NT

Video Inconsistencies

If there are any display inconsistencies and your system is set for 256 colors, increase the number of colors in your display settings.

Install/Uninstall Problems

Install will not proceed for non-Administrators

The user doing the install must be in the Administrator group to run Rose RealTime Install. There is a concept of Administrator privileges on the System in NT, rather than network administrator. To add the user administrator privileges, you have to login as an administrator for the system (not a network administrator) and run "User Manager" utility in Start Menu\Programs\Administrative Tools(Common). Select Administrators group and add the user to the group. Refer to Windows NT documentation for further details.

Uninstall leaves incrementally installed Rose RealTime files on the disk

Always run the uninstall program before re-installing Rose RealTime. If components have been incrementally installed they will not be removed by the uninstall and must be removed manually.

Listbox is empty

During setup the user can go to the Directory Browser to select the destination directory for 'Rose RealTime Install'. When the user enters the browser a second time (for example: click Cancel and click Browse again) sometimes the user will not see mapped network drives, the listbox will be empty. This is a known limitation related to the InstallShield software, the installation utility used by Rose RealTime. To work around the problem, press then network button on the browser and press cancel in the network dialog to go back to the Browser.

Online Help

If the Windows NT platform in which the toolset is running, does not have a browser installed, an error message will be displayed when Help is launched.

Compilation problems

Compile fails on valid C++ model with VC++ 5.0 / 6.0

The INCLUDE and LIB environment variables may not be properly set. Set the environment variables. Refer to the VC++ documentation for further details.

Windows NT Compilation Command Line Limits

If you encounter a compilation error message that complains about the command line being too long, the cause may be that the length of your compile or linker has exceeded a limit.

Windows NT compilation has command line limits in two areas: source compilation and linking. Both limits have been explored for the Visual C++ 5.0, Visual C++ 6.0, VRTX PPC Microtec 1.4 and Tornado 1.0.1 PPC Cygnus 2.7.2 compilers.

Source File Compilation

The variables in source compilation are the update name, the %ROSERT_HOME% path, compilation options, the local working directory and include directories. The only compiler that has a measurable limit is Microtec’s VRTX compiler. The command line limit is 768 characters.

A workaround for the problem is to reduce the number of include directories by combining include files. Other solutions are to shorten paths and names for the variables listed in the previous paragraph.

Linking

The variables in linking are the update name, the %ROSERT_HOME% path (Windows NT), the link options, the number and name length of libraries, the library search paths and the local working directory. The link limits are shown in Figure 1, "Link Limits."

Table 1 - Link Limits

Platforms	Link Limit
Visual C++ 5.0:	more than 20875 characters
VRTX PPC Microtec 1.4	4147 characters
Tornado 1.0.1 PPC Cygnus 2.7.2	4150 characters
HP-UX 10.20	16384 characters (make: “couldn’t load shell.stop”)

A workaround for the problem is to shorten paths and names for the variables listed in the previous paragraph.

MSVSS Library problems

MSVSS Library Interface commands fail to execute with the message ’Cannot execute MSVSS command ’

Possible cause: MSVSS binaries are not on the path.

Solution: Add MSVSS binaries directory to the path and restart the Rose RealTime session.

MSVSS Library Interface commands fail to execute with a message
‘Cannot create project ’

Possible cause: You are not configured as a SourceSafe user.

Solution: Each user has to be configured, before using SourceSafe, through SourceSafe Administrator. Request that your MSVSS administrator add you as a user and restart Rose RealTime session.

Mailing exception files

Windows Messaging must be installed before either exception files or comment files are automatically mailed. The format supported is SMTP (internet format addresses).

Troubleshooting License Manager

For License Manager troubleshooting tips please refer to the Install Guide page 15 and page 20.

ICON Display

If the Rose RealTime icon, which is displayed under Windows NT, does not match the documentation, you may need to increase the number of colors which Windows NT uses to display the program icons. In order to correct this issue, bring up Display Properties from the Desktop of your Windows NT workstation and check the "Show icons using all possible colors" box as shown in Figure 1, "Display Properties Window," on page 15.

Figure 1 Display Properties Window

Chapter 6 - Known problems and limitations

The following is a list of the problems and limitations in the Rose RealTime product at the time of release. Some of these problems may have been addressed by the time you read this. For the most recent list of known problems and any fixes that may have been published, please visit the Rose RealTime web site at:
www.rational.com/products/rosert

Start-up problems

If Rose RealTime has problems starting up, look at the task bar and use the Task Manager to check for running copies of the tool. Terminating them will allow new copies of the tool to start properly.

Shutdown problems

In Unix, starting multiple copies of Rose RealTime and displaying to the same display, may cause problems at shutdown, unless they are shutdown in the same order in which they were started.This issue will be addressed in the next release of Rose RealTime.

Note: If you are unsure of the state of the system, execute the following command: RoseRT -cleanup. This command will terminate any active Rose RealTime sessions.

Uninstall

Sometimes files are left behind after an Uninstall. For example, if a model has been 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.

Rational Suites License Administrator

If after installing Rational Rose RealTime, you are having problems running the Rational Suites License Administrator, please delete the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\rational_LICENSE_FILE.

Keyboard shortcuts on Unix may not work

On Unix, when performing keyboard shortcuts, the control key’s state becomes desynchronized. For example, "copy/cut and paste" operations on an object, sometimes cause the object to lock in position, that is, it cannot be moved after the "paste". This generally occurs with multiple selections in diagrams and browsers. A temporary workaround is to right-click, or hit the Shift key, after pressing the Control key. This resynchronizes the key state.

Specification dialog

In Unix, right-clicking on any of the buttons in a Specification Dialog box incorrectly brings up a File menu. (On Windows NT a "What’s this?" popup box is displayed.) Any selection in the File menu behaves like a "What’s this?", that is, there is no loss of functionality. This issue will be addressed in a future release of Rose RealTime.

Matching signal names and external code may cause problems

Signal names are in global scope. If they are the same as some external code (either in a header file, or as a symbol in a library), then compilation errors may occur.

Visual Differencing tool not responding

If the Visual Differencing tool is not responding, check for additional Rose RealTime processes that may be running. Stop the running Rose RealTime processes and restart both Rose RealTime and the Visual Differencing tool. On Unix, the RoseRT -cleanup command removes any Rose RealTime processes which have been started in error.

Note: The RoseRT -cleanup command will terminate any active Rose RealTime sessions.

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\SduDriver.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 on 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);