Rational Rose

(2) The SoDA eval license expired. Stay tuned.

(3) The newer version of StarNet's X-Win32 (4.0.1) on NT workstations does not suffer from the problems described below. Rose seems to work with "TrueColor" and probably other display settings.

Running Rational Rose 98 at SLAC

We currently have 2 floating licenses, managed by flexlm, for Rational Rose on the Sun/Solaris operating system. The distibution is installed in /afs/slac.stanford.edu/package/rational/rose98dir. The installed version of Rose 98 is "98.2" also known as 4.5.8303, though the license refers to it as Rose 5.0 (!).

Additional information can be found in the release notes, or the Rational Home Page.
Some of the older information on this page (farther down) may also be useful.

If you have previously run an older version of Rose, you should move (rename or delete) the rose.ini file from you home directory before running Rose 98. Rose 4.0 does not run under Solaris 2.6, so you should switch to this version. Rose 4.0 should remain available until the end of 1998.

Note that if you switch from running Rose4.0 to Rose98, you may have background Rose4.0 windu processes still running which are incompatible with Rose98. You should kill them. To find them do:
ps -elf | grep windu | grep <your username>
You should also delete the .WindU file and .windu* subdirectories from your home directory (do this while Rose is not running).

To set up your environment, source the following c-shell script while logged onto a Solaris computer (such as a Flora):
/afs/slac.stanford.edu/package/rational/rose98/config.csh

OR

execute the following shell script:
/afs/slac.stanford.edu/package/rational/rose98/config.sh

Use the following executable to start Rose:
rose

Use the following executable to reverse engineer existing code:
analyzer.

Quick instructions for reverse engineering are here. Refer to the manual, Round-trip Engineering in Rational Rose/C++ or the online help for more details.

Note: Each executable starts its own GUI and then exits, so there is no need to run either in the background.

There is fairly extensive hypertext help in the GUIs. The Rose 4.0 user manuals are in my (John Bartelt's) office, Bldg 50 (SCS) room 363.

(10 July 1998) The old version of rose has been removed.

Rational SoDA 2.2.4 for Solaris has been installed on a trial basis; the installation appears successful. The following is the revised list of environment variables which must be set:

  setenv SODA_HOME           /afs/slac.stanford.edu/package/rational/soda
  setenv ROSE                /afs/slac.stanford.edu/package/rational/rose
  setenv ROSE_STANDALONE     true
  setenv ROSE_CPP_MENU_PATH  $SODA_HOME/editor_files/rose.mnu
  source $ROSE/config.csh
  set path = ( $path $SODA_HOME/bin )

Caution: if you have run Rose before, it may be necessary for you to delete the files .rose.ini and .rose_check from your home directory before starting rose_cpp to get the new SoDA menu items. However, this may delete preferences you have set.

Then rose can be started by saying "rose_cpp".
Soda can be started by saying "soda".

CAUTION! The Rose GUI only supports 256 (8-bit) pseudocolor displays. This limitation has various results on different devices: on a Dell Windows NT workstation the (Starnet) X-Win32 session crashes, unless the display is set to use only 256 colors. Note! This problem seems to be cured in the newer version of X-Win32. With the number of colors set to 256, it seems to work. Similarly, it will not display properly on a unix worksation with 16-bit truecolor. If you run and display on a Solaris sparc workstation (e.g., "charger"), it works fine, because the workstation has built-in capability to display 8-, 16-, or 24-bit color. It has been run successfully with the display going to a DEC NT workstation, NCD xterminals and unix workstations, all using 8-bit color.

This problem has been reported to Rational, but so far their suggestions have been useless. The X-Win32 crash has also been reported to Starnet.

The first time you start Rose (see below), it creates a number of files in your home directory: .WindU, .rose.ini, .rose_check, and a subdirectory: .windu (note capitalization). Sometimes, if you change from one kind of display to another (e.g., Xterminal to Sun workstation), you may have some problems with the display: for example, some of the icons may not appear. This can often be fixed by quitting Rose, deleting the files just mentioned, and restarting. Note that this will also delete some of your default Rose settings.

Lately, running rose across the network (i.e., executing on one machine, displaying on another) has been very slow, so it may require patience.

Running Rational Rose 4.0 at SLAC

We currently have 2 floating licenses, managed by flexlm, for Rational Rose 4.0 on the Sun/Solaris operating system, but you should switch to Rose 98 (above). The distibution is installed in /afs/slac.stanford.edu/package/rational/rose4dir. The installed version of Rose is 4.0.15. Additional information can be found at the Rational Home Page.

Rose 4.0 will not work on Solaris 2.6; you should switch to Rose 98 (above).

To set up your environment, source the following c-shell script while logged onto a Solaris computer (such as a Flora):

/afs/slac.stanford.edu/package/rational/rose/config.csh

OR

execute the following shell script:

/afs/slac.stanford.edu/package/rational/rose/config.sh

Use the following executable to start Rose: rose_cpp

Use the following executable to reverse engineer existing code: analyzer.

Quick instructions for reverse engineering are here. Refer to the manual, Round-trip Engineering in Rational Rose/C++ or the online help for more details.

Note: Each executable starts its own GUI and then exits, so there is no need to run either in the background.

There is fairly extensive hypertext help in the GUIs.