Please refer to the Rose for UNIX/Linux Installation Guide that is provided as your primary guide for installing and setting up licensing for this product.
If you encounter any problems while installing or licensing the Rose product, please check here first to see if it is a known problem. If a problem is not yet documented, please contact Rational Technical Support so we can investigate it, provide you with a workaround, and track the problem for future action.
This chapter contains the following sections:
As a precaution, always make back ups of any Rose model files that you will be accessing with this software.
This product includes FLEXlm, a licensing product from Globetrotter, Inc. A startup license key that allows you to start using your product immediately is shipped with this product. You must obtain a separate permanent license from Rational in order to continue using this product beyond this startup key expiration date. Please refer to the licensing section of the Installation Guide for detailed instructions on obtaining and installing permanent licenses. Also, see Licensing Information for any last minute licensing notes.
You may want to back up your Registry prior to running the installation program. Specifically, we recommend you make backups of the following files:
Follow these steps to back up path maps:
Follow these steps to restore path maps:
Before installing this software, please verify that your system meets the minimum system requirements listed below. If the requirements are not met, the product may not install and/or operate correctly.
The following table contains the hardware requirements for installation and use of this product. Note that the recommended amount of memory is only the suggested minimum amount. Additional memory may improve performance. Your memory requirements will also be larger if you are constructing large models.
The next table contains the software requirements for installation and use of this product. Note that this is also only a suggested amount of swap space. Your requirements may be larger if you expect to construct very large models. If all of your models are small, you may need less than the amount shown.
Please see "Operating System Runtime and/or Patch Requirements" in the Installation Guide for system patch requirements.
When installing and running Rose for UNIX/Linux for the first time, you will be alerted if hardware or software patches are necessary. If running on a Solaris or HP-UX server, Rose for UNIX/Linux will attempt to automatically determine if patches are necessary on your server and/or Solaris display, and will advise accordingly.
You may also run the following anytime to determine if your computer requires operating system patches to run Rose for UNIX/Linux.
Check that the DISPLAY environment variable is set to your display, and then:
Configure your Window Manager such that pop-up windows will remain on top of their parent windows, in compliance with the Windows API. Under X11, Window Managers may implement different strategies for maintaining the Z-order of pop-up windows.
In order to keep pop-ups on top, if possible:
There is no specific configuration to keep pop-up (transient) windows on top. Pop-up windows are kept on top by default.
Depending on your system's configuration, the default behavior of dtwm may not keep pop-up (transient) windows on top of their owner.
For example, it may be that the window stacking behavior for dialogs is specific, such as "Dtwm*secondariesOnTop = False". In such a case, here are some possible solutions for keeping the pop-ups on top:
If Rose for UNIX/Linux hangs when running on a multi-processor Solaris 2.6 computer, verify that the Solaris 2.6 server and display (if applicable) includes the Sun Solaris XSun Patch 105633-32 or higher. This patch includes a fix for Sun Defect 4233280, Sun SO#3918581 (multi-threaded applications crash/hang on 2.6 multiprocessor computers). To check for this patch, run
on both the server running Rose and the display (if display Solaris 2.6).
When installing or running the application for the first time, Rose will advise if this patch is installed or required.
A CDE crash may occur when displaying Rose for UNIX/Linux on a Ultrabook using a PGX Graphics Card, if SUN Solaris patch 105362-26 is installed.
If using a PGX Graphics Card, we recommend that SUN Solaris patch 105362-20 be installed as this is the latest version tested and determined to be compatible with this release.
If you encounter the CDE crash, uninstall patch 105362-26 and if possible install "105362-20". If SUN Solaris patch "105362-20" is not installed, the following may occur:
If you uninstall patch 105362-26 and encounter any of the issues described above, contact Rational Technical Support if patch 105362-20 is not available.
Rose for UNIX/Linux requires HP-UX OS Patch PHSS_17327 (X/Motif 2.1 Dev Kit Mar99 Periodic Patch). This Patch requires PHSS_17326 (X/Motif2.1 Runtime Mar99 Periodic Patch). PHSS_17326 has been superseded by HP-UX OS Patch PHSS_23823.
It is important to use PHSS_23823 as Rose for UNIX/Linux will not start (display) if an earlier version of this patch is installed (i.e. PHSS_21493).
If it is necessary to have a Motif Xlib runtime patch prior to PHSS_23823 and you encounter this issue, refer to the following instructions to workaround this problem:
When Rose for UNIX/Linux runs for the first time, an $MWUSER_DIRECTORY directory is created which includes MainWin files and directories. Rose is created utilizing MainWin (developed by Mainsoft) and requires specific MainWin components to operate correctly. $MWUSER_DIRECTORY may be set to serve as the windows directory. For example, $MWUSER_DIRECTORY may be set to $HOME/.windows. If $MWUSER_DIRECTORY is not set, the default location will be $HOME/windows.
Within the $MWUSER_DIRECTORY directory, you will find the following type of files and directories:
mwfc-xxxx (where xxxx is dependent on the specific display used)
This file can be removed if it is suspected of interfering with font operations. If removed, it will be regenerated the next time Rose is invoked.
When Rose for UNIX/Linux is invoked by the user on the same X server, the application can quickly look up the font cache file and select the closest X font available.
The registry directory also includes rose_reg_check, an ascii file which includes the version of Rose for UNIX/Linux and it's associated add-ins. This file is created the first time a user runs Rose for UNIX/Linux.
A specific registry file may be utilized by setting the following environment variable:
Rational uses MainWin (by Mainsoft) to rehost Rose for UNIX/Linux platforms. Specific MainWin runtime components are included in Rose. Below is a description of the type of MainWin files included in Rose for UNIX/Linux under the rational_dir/rel*/rose*/mw directory.
Rose for UNIX/Linux now includes the following release fonts which are compatible and may be used on both the PC and UNIX/Linux displays:
As it now is possible to display these same fonts on UNIX/Linux and the PC - models, etc. created on the PC (using these fonts) should display easily and accurately in Rose for UNIX/Linux on PC and UNIX/Linux displays. Furthermore, utilization of these fonts will provide the following additional enhancements:
Font files (in *.pcf - portable compiled format), are now included in the rational_dir/releases/rose.I.J.K/mw/fonts directory of your release. This directory also includes the following fonts* files:
A fontserver.cfg file is included in the rational_dir/releases/rose.I.J.K/mw directory. This file is used when starting the font server to provide the new fonts to the Rose application. A font server (xfs) is also provided in the rational_dir/releases/rose.I.J.K/mw/bin_<os>_optimized directory.
Prior to running Rose for UNIX/Linux for the first time, run rational_dir/releases/rose.I.J.K/bin/rose_cleanup. Upon starting Rose for UNIX/Linux, you will notice some new messages in relation to the availability of the new fonts. Rose will attempt to determine if the new fonts are available for your $DISPLAY, by running the new Rose for UNIX/Linux rose_fonts utility.
rose_fonts will make the fonts available to your DISPLAY by including the path to rational_dir/releases/rose.I.J.K/mw/fonts/ in your DISPLAY's font path.
In this case, fonts must be made available by using a font server and including the font server in the DISPLAY's font path.
rose_fonts will determine if a font server is providing access to the Rose fonts, as described below:
If a font server is running on the Rose server and it is not already providing access to the Rose fonts, contact your System Administrator to perform this setup or refer to the man pages for xfs(1). The following advises how to configure an existing font server on SUN Solaris.
If you elect not to add the Rose font support (as described next) or elect to remove the Rose font support from an existing font server Rose will continue to operate correctly, however the font enhancements listed in Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux Displays will not be available and you may encounter the following defects:
To add Rose font support to an existing font server on SUN (it may be necessary to su to root to perform these actions):
A catalogue path may appear as:
/usr/openwin/lib/X11/fonts/F3bitmaps/,/usr/openwin/lib/X11/fonts/Type1/
Add the Rose font path, by prepending the path to the catalogue path.
rational_dir/releases/rose.I.J.K/mw/fonts/,/usr/openwin/lib/X11/fonts/F3bitmaps/,...
Rose (upon starting) should indicate that the Rose fonts are now available.
Upon performing this setup, it will be important to update the fontserver.cfg file if Rose is uninstalled or moved to a different location (path changes).
If a font server is not running (on the server running Rose), rose_fonts will start a font server provided in the release, if necessary. This is necessary if the DISPLAY is not a UNIX/Linux display, or if the display does not have direct visibility to the fonts provided in the Rose release.
The following commands are typically located in one of the following directories: /usr/openwin/bin, /usr/bin/X11, /usr/X11R6/bin, /usr/openwin/lib/X11, or /usr/openwin/include/X11. The font server "xfs" is provided in your release in rational_dir/releases/rose.I.J.K/mw/bin-$arch_optimized.
xfs -config rational_dir/releases/rose.I.J.K/mw/fontserver.cfg -port 7100
xset +fp rational_dir/releases/rose.I.J.K/mw/fonts/ (direct path to fonts in release)
xset +fp tcp/$host:7100 (font server path)
xlsfonts may hang if a font path includes a path to a font server which is not running. rose_fonts will not let xlsfonts run for longer than a specified period of time (typically 30 seconds), to safeguard against this event. If an xlsfonts hang occurs, rose_fonts will provide status with recommendations.
In summary, rose_fonts will provide the Rose fonts to your DISPLAY by either setting the font path to point to the fonts in the release (UNIX/Linux display with visibility to the fonts), or by setting the font path to a running font server if the font server is providing access to the Rose fonts. rose_fonts will use "xset" to set the font path, "xfs" to start a font server (if necessary) and "xlsfonts" to determine if the Rose fonts are available after the setup has been performed. If a font server is already running and does not already provide support for the Rose fonts, manual setup is necessary (i.e. see Adding Rose fonts to Existing Font Server on SUN Solaris) to complete the Rose font setup. In this case, manual set up is required as it is often necessary to su to root to perform this action. rose_fonts will provide messages describing the current status each time Rose is started.
Contact Rational Technical Support if you should have any questions or encounter any difficulties accessing or utilizing the new Rose fonts.
There may be occasions when the Rose fonts will not be available. rose_fonts will alert you if, when starting Rose, if the Rose fonts are not available. If this occurs, Rose will continue operate correctly, however the font enhancements listed in Installing and Utilizing Fonts Compatible on Both PC and UNIX/Linux Displays will not be available and you may encounter the following defects:
Each time that you start Rose, rose_fonts determines whether the Rose Fonts are available, attempting to make the fonts available when necessary. Each time Rose is started, rose_fonts displays messages advising current Rose Font status. In order to eliminate output from rose_fonts, set the following environment variable prior to running Rose.
Setting this environment variable will allow rose_fonts to run, but will refrain from printing Rose Font status messages.
There are three license types supported by Rose for UNIX/Linux:
For a full description of license types, installation and usage, please consult the Rational Rose for UNIX/Linux Installation Guide.
The software you receive includes a temporary startup license. You must install the software and follow the steps detailed in the Installation Guide to acquire node-locked or floating license for your product. For users who are upgrading from Rose 98i for UNIX/Linux, you may use your existing license key to run Rose for UNIX/Linux.