Copyright © 1993-1998 Rational Software Corporation.
All rights reserved.
This document is subject to change without notice.
GOVERNMENT RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Rational Software Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.
"Rational", the Rational logo, and Rational's products are trademarks or registered trademarks of Rational Software Corporation in the United States and in other countries. All other names are used for identification purposes only and are trademarks or registered trademarks of their respective companies. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. Microsoft, Windows, Windows NT, and MS-DOS are trademarks or registered trademarks of Microsoft Corporation.
[Next]
[Prev]
[TOC]
[Info]
Preface
This guide explains how to install Rational Rose/C++®, hereafter Rose, on UNIX platforms.
Before starting the installation, you need:
Proceed straight through all the chapters in this guide, following instructions in the order given.
This section summarizes conventions that are followed by this guide and by the scripts you run to install Rose.
Installation GuideThis guide uses the following text conventions:
Also, the variable element I.J.K is used to represent the current release number, where I is the major release number, J is the minor update number, and K is the micro release number. Please substitute the current release number - for example, 1.0 or 2.5.1 - wherever you see I.J.K.
Installation ScriptsRose installation scripts can be run on any type of character terminal or in an xterm window on a workstation that is running the X Window System. The scripts assume only that the terminal can print characters and new lines. All output is sent to the shell's standard output or standard error.
The script first prints the Rose version and a copyright notice. Then the script prompts you for any information that it needs. You are allowed to step through the prompts as many times as you wish. Once you are sure that you have provided the proper responses to each prompt, the script proceeds with its installation steps.
Many prompts give you a limited number of choices - for example: yes or no . In such cases, the scripts provide the following interface:
If you are installing Rose on a client-server network, observe that you must enter specific commands on specific workstations. For example, daemons that run on the Rose license server must be started on that license server, not on some other workstation.
rational_dir/ -Rational Software product area
base/cots/ -License server, etc.
config/ -data for installed products
releases/ -installed products
rose.4.0.x/ -release 4.0.x of Rose
install/ -Rose installation scripts
If previous Rose releases or other Rational products have already been installed, directories such as rational_dir , rational_dir /base/cots , and rational_dir /releases will already exist. Since you will not be creating them yourself while installing this Rose releases, make sure that you have write permission to them before starting the installation.
Recommendation: If you have Rose models that were created with a previous Rose release, do not delete your previous release until your models have been successfully converted to Rose 4.0.
The installation scripts log progress to the
install/install.log
file. In case you encounter a problem with the installation, this file may help you (or Rational Technical Support) diagnose it.
[Next]
[Prev]
[TOC]
[Info]
Prerequisites
Ensure that you have the required hardware and software before proceeding with the Rose installation.
Recommendation: Before installing Rose, you might find it helpful to get a copy of the system management guide from your platform vendor.
Note that there may be additional Operating System patch requirements. These are described in Appendix C, " Operating System Patch(es) Requirements Specification ". Refer to this specification before proceeding.
The following tables list the recommended configuration to successfully install and use Rose.
You do not need to log in as root to verify that most of these requirements are satisfied. If all are satisfied, you can proceed with the installation. If any are not satisfied, however, you probably will need help from your system administrator. Changing most of these items requires knowledge of your network and workstation configurations as well as root permissions.
Recommendation: Check all the items listed, noting any requirements that are not satisfied. Give the list of needed changes to your system administrator, wait for the changes to be made, and then proceed with the installation.
The first 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 larger 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 here.
| Software Item | Requirement | For |
|---|---|---|
| Operating system | AIX 4.1 | Solaris 2.5HP-UX 10.20Digital UNIX 4.0SGI Irix 6.2Use |
| TCP/IP | Must be running | Installation, Use |
| Host names | Must be configured | Installation, Use |
| Swap space | 100 + (32 * N) MB | (where N is the number of users running Rose simultaneously on a given workstation)Use |
| X Window System | MIT X11R5 or X11R6 | Sun OpenWindows on SolarisUse |
| Window Manager | OSF/Motif© 1.2, | window manager (mwm),Sun olwm or CDE 1.1Use |
A script named check_rose_reqs is included in the
rose.I.J.K/bin
directory that is loaded from the Rose release disks. This script can assist you in the verification of required configurations and the minimum recommended resource settings.
While you are installing Rose, the installation scripts automatically use check_reqs -install to verify TCP/IP, the portmap daemon, and host names. These are requirements for the workstation(s) on which you install Rose.
Before using Rose, you (or each Rose user) can use check_rose_reqs to verify TCP/IP, the portmap daemon, host names, memory swap space, pseudo terminals, resource limits, the X Window System, and the Motif window manager. The check_reqs script cannot check the available physical memory on some platforms.
Your hardware can be configured in various ways. For example:
This chapter describes the requirements for a single-user desktop workstation that you will use either stand-alone or with a file server that provides no support other than file service. The desktop workstation will run all Rose processes.
The alternative is to run all Rose processes on a remote compute server, redirecting the display to your local workstation or X-terminal. If the compute server is shared by several Rose users, it will need to be more powerful than a desktop workstation that supports only one Rose user.
This chapter provides instructions for loading the Rose release from the Rose release media.
The Rose Release media is delivered on CD-ROM and contains installation scripts and the Rose components. You use the rinstall script to read the installation scripts, and then use one of the scripts to load the Rose components.
Do not log in as root. Use a regular login.
% mkdir rational_dir
For rational_dir , supply a pathname such as:
/someplace/rational
Note that on a client-server network, rational_dir must be visible (by NFS mounting) to all Rose workstations.
% cd rational_dir
Rose/C++ for UNIX is provided on CD-ROM. Follow the following instructions to install from this media.
Solaris 2.5 with volume management mounts /cdrom automatically after loading the CD into the CD-ROM drive:
# mkdir /cdrom # mount -r -F hsfs /dev/dsk/c0t6d0s0 /cdrom
# mkdir /cdrom # mount -r -v cdrfs /dev/cd0 /cdrom
# mkdir /cdrom # mount -r -F cdfs /dev/dsk/c0t2d0 /cdrom
# mkdir /cdrom # mount -r -t cdfs -o rrip /dev/rz4c /cdrom
NOTE: If the following error occurs when attempting to read the CD-ROM on your DEC Alpha (Digital UNIX 4.0) machine:
verify that /dev/rz4c is the correct device name. If so, it may be necessary to have your System Administrator include the following line in the system configuration file:
options CDFS
Once this has been done, it will be necessary to rebuild the kernel.
Refer to "man cdfs(4)" for additional information.
Contact Rational Technical Support if you continue to have problems.
Irix 6.x with volume management mounts /CDROM automatically after loading the CD into the CD-ROM drive.
# mkdir /cdrom
# mount -r -t iso9660 /dev/scsi/sc0d6l0 /cdrom
(requires eoe2.sw.cdrom package)
% exit
% cd /CDROM % ./rinstall
% cd /cdrom/cdrom0 % ./rinstall
% cd /cdrom % ./rinstall
From the rinstall menu, enter the rd key to set the rational_dir directory where you are going to be installing each product. Enter the go key to begin the install.
% cd releases/rose.I.J.K/install % ./install
The install script allows you to quickly and easily load the default product from the release media with very little user input. If you want to install something other than the default product, you must tailor the installation.
The install program has 5 menus. When you run it, you start from the General Menu. You must traverse to the Product-Configuration Menu or the Group Menu and tailor the install. Option `t' will traverse you to one of these 2 menus. From there, you can use option `t' to traverse to the next menu or use option `r' to return to the previous menu. The menus are:
General menu [( Product-Configuration Menu] (optional) ( Group Menu ( Component Menu ( Storage-Location Menu
At each menu, you can select option `h' to get help.
The Product-Configuration Menu allows you to select one, and only one, product configuration. If there is only one product on the release media, this menu is skipped.
The Group Menu allows you to select or deselect a group of components to install. Each group is numbered for you to easily specify a particular one. You may select one or more group numbers at a time.
The Component Menu allows you to select or deselect a component to install. You may enter one or more component numbers at a time.
FLEXlm license code is included for all target operating systems.
% eject cd
% eject /CDROM
% su # umount /cdrom
Store the CD-ROM in a safe place in case you ever need to reinstall Rose.
The Rose installation is structured in such a way that executables for several architectures may be present on the same media. You may install executables for more than one platform into the same installation area without conflict, even if those executables come from different sets of media.
The media contains the following kinds of components:
A Platform Independent Component. This component must always be installed. However, if you are installing from more than one media set, it must only be installed once.
A Shared Binary Component for each platform. This component must be installed for each platform on which you will execute any variant of Rose.
A Rose/C++ and Analyzer Component for each platform. This component must be installed for each platform on which you will execute Rose/C++.
A FLEXlm Component for each platform. This component must be installed for each platform on which you will run a Rose license manager. Note that a license manager running on any platform can serve Rose running on any other platform.
Note: Converter components, which must be installed for each platform on which you need to convert models from other OO tools to Rose models, are no longer included on the media. The conversion tools are now available on Rational's World Wide Web page; its URL is http://www.rational.com .
This chapter tells you how to configure Rose after loading it from disks. You must complete these steps before using Rose.
To complete the installation, you must run four scripts:
Rose uses the FLEXlm license manager to manage access to the product. FLEXlm manages Rose floating and node-locked licenses. FLEXlm version 5.0b is the version of FLEXlm used, beginning with Rose 4.0.15i. If upgrading from a version of Rose prior to Rose 4.0.15i, you must install FLEXlm 5.0b.
If you want to integrate Rose licensing with an existing license manager, you need to know the name of the license server and the location of the license file.
You will also need to provide a TCP port number for the license server. The default port number is 1706. Use it unless you have already assigned that port number to another application.
You can check for conflicts by searching the /etc/services file or by entering this command if you are running the Network Information Service (NIS).
% ypcat services | grep 1706
Note: 1706 is the default port number for other Rational products. If you are installing Rose, and if you want to use the same license server, specify the same port number.
% cd rational_dir/releases/rose.I.J.K/install
% ./get_license_info
This script will help you gather the information you need for configuring your Rose license. This information is stored as a part of the
rational_dir
/releases /rose.
I.J.K
/install/install.log
file.
% ./add_license_info
This script will help you add your licensing information to your license file - for example: license.dat.
% su # become root # ./start_lm # exit # leave root
% ./post_install
Note: You need to run post_install for each architecture on which you are installing Rose. For example, if you are installing Rose for use on workstations, some of which are running Solaris and some of which are running HP-UX, you should have already loaded the platform-specific components for both Solaris and HP-UX from your release media. You need to run post_install twice-once while logged into a Solaris system, and once while logged into an HP-UX system.
% cd rational_dir/releases/rose.I.J.K/xprinter
The xprinter directory contains several subdirectories whose names end in PPDS. Each file in a PPDS directory contains the description for a single print device. Most printer descriptions begin with manufacturer and model for the printer the file describes. For example, the printer description xprinter/PCLPPDS/HP3SI.PPD begins:
*Product: "(HP LaserJet IIISi) " *ModelName: "HP LaserJet IIISi PCL Cartridge" *NickName: "HP LaserJet IIISi PCL Cartridge"
% cd ..
% chmod 644 WindU
SymbolicName=PPDSPrefix Type, VariableName:
For example, the device listing for the HP LaserJet printer described in Step 1 is:
[Devices] HP LaserJet SI=HP3SI PCL5,mylaser:
Note that the device specification determines device-dependent characteristics of output generated by the Rose Print commands. It does not determine the actual printer or file to which the output is written.
In the [Ports] section of the WindU file, assign the UNIX print command you want used for printing to the VariableName that you defined in the [Devices] section. The command should include any options needed for your printer to recognize a PostScript file. Continuing the example above, the following assignment causes output sent to the printer named HP LaserJet SI to be printed using the UNIX lp command:
mylaser:=cat | lp
By default, the lp command sends output to the printer specified in your $LPDEST or $PRINTER environment variable. If you have not set either of these variables, you may want to supply a printer name as an option to the lp command in the port assignment:
mylaser:=cat | lp -d laser1
% chmod 444 WindU
When a user first starts Rose, Rose copies the $ROSE/WindU file into a file called .WindU in the user's home directory. The user then has access to the printers and print command you have to set up. If you make changes to the $ROSE/WindU file after users have begun using Rose, you should merge the new $ROSE/WindU file with each Rose user's .WindU file.
source rational_dir/releases/rose.I.J.K/config.csh
rational_dir/releases/rose.i.j.k/config.sh
You have completed the Rose installation. Use the following commands to start Rational Rose products:
|
Product
|
Command
|
|---|---|
|
Rose/C++
|
|
|
Analyzer
|
analyzer
|
These commands are shell scripts contained in the rational_dir /releases/rose. I.J.K /bin directory. The same scripts can be used to run Rose on any architecture; the scripts automatically determine the architecture and run the appropriate executable for the architecture.
When you buy Rose, you purchase some number of node-locked and/or floating licenses. A node-locked license allows you to use Rose on a specific workstation. Floating licenses allow anyone on your network to use Rose as long as a floating license is available. Thus, the number of licenses that you purchase determines the maximum number of users who can use Rose simultaneously.
For example, if you purchased five licenses and three users are currently using Rose, then two more users can use Rose.
Licenses are controlled by a license manager (software delivered as part of Rose) that runs on a license server (one of your workstations). The license manager monitors license access, simultaneous usage, idle time, and so on.
When you start Rose, you are initially unlicensed. If a license is available, the license manager gives you a license and you retain it as long as you keep using Rose. When you exit Rose, your license is returned to the license manager and becomes available for another user.
If no license is available, you are unable to use Rose until the license is returned by another user.
Rose uses the Flexible License Manager, FLEXlm, from Globetrotter Software, Inc. The license manager includes the following components:
Once the daemons and license file are in place, all that remains is to start the license daemon, which in turn will start the vendor daemons.
For convenience, you will probably want to augment a system initialization script on your license server to automatically start the license daemon each time the license server boots.
The names, locations, organization, and contents of system initialization scripts varies from system to system. You might begin by looking at the following files:
Digital UNIX: /sbin/init.d/SlmRational.sh
HP-UX: /sbin/init.d/SlmRational.sh
Rose provides installation scripts to guide you through this setup. They are described in "Configuring Rose" .
Note: You cannot run two rational daemons on the same host, so even though FLEXlm allows you to run multiple lmgrd daemons, you cannot put Rational products under the control of multiple lmgrd daemons on the same host.
To verify that your license manager is operational, you can enter these commands on your license server to see if its daemons are running:
% ps axww | grep -v grep | egrep "lmgrd|rational"
% ps -e | grep -v grep | egrep "lmgrd|rational"
Their output should include lines similar to the following (your pathnames will vary):
1719 - S 0:00 /someplace/rational/rose/ROSEARCH/license/lmgrd -c /someplace/rational/rose/license.dat
10424 - S 0:13 rational -T garcon 4 -c /someplace/rational/config/license.dat
The license manager supports several system-administration commands.
The default Rose license file is rational_dir / config/license.dat. As you install Rose, you can merge the Rose license data into another license file that you have already set up for another product.
When users start Rose, the start up script automatically defines the environment variable LM_LICENSE_FILE for them. FLEXlm uses this variable to locate the license file.
The license file is a text file that you can edit with any text editor. Your license file will contain lines similar to:
SERVER garcon 1874350 1706
DAEMON rational /someplace/rational/rose/ROSEARCH/license
FEATURE rose.cpp.sun4 rational 4.00 1-oct-98 6 FBE669014E142A4CF37 " "
In general, one or more server lines are followed by one or more vendor daemon lines, which are followed by one or more feature lines. Rose requires only one of each, but your license file may include data for other products, too.
Each server line contains, in order, the:
Each vendor daemon line contains, in order, the:
Each feature line contains, in order, the:
The tokens on each line can be separated by any amount of white space (spaces or tabs). You can edit only four kinds of tokens in the license file:
All other tokens are included as input to the encryption algorithm that produces the encryption codes on the FEATURE lines.
Note: A DEMO FEATURE Line (includes "DEMO" at the end of the FEATURE Line) is a special temporary license which does not require running lmgrd or start_lm . Licensing is activated when the DEMO FEATURE Line is placed in the license file.
The feature names for Rose have changed from those used in previous releases. Feature names are now of the form rose. product . host. The product is cpp for Rose/C++. The host is sun4 for Solaris, hppa for HP-UX, alpha for Digital UNIX, mips for SGI Irix, and rs6k for IBM AIX.
Note that a single floating license cannot be used to run Rose on more than one architecture. In past Rose releases, while this was not enforced, it was in violation of Rational's license agreement.
If you desire to have one or more floating licenses that may be used across machine architectures, you may obtain such a license (with the host set to " any ") for an additional charge.
You can customize Rose access by:
An options file allows you to:
For Rose, lines in the options file have this format:
GROUP name list_of_users
RESERVE number rose.cpp.host
{USER | HOST | DISPLAY | GROUP} name
INCLUDE rose.cpp.host {USER | HOST | DISPLAY | GROUP} name
EXCLUDE rose.cpp.host {USER | HOST | DISPLAY | GROUP} name
TIMEOUT rose seconds
Contact Rational Software Corporation to obtain the encryption code for your Rose installation.
Please be prepared to supply the host name and ID number of your Rose license server, the number of licensed users, and the licensing version of your Rose release. The get_license_info installation script will help you gather them. It creates a file called LICENSE_INFORMATION that can be e-mailed to support@rational.com .
Rational Software Corporation will provide your encryption code and its expiration date. The code will be a 20-digit hexadecimal string - for example: 4B868981DB6D7295573E. The date will be in a dd-mmm-yy format - for example: 30-oct-94. The day must be expressed as two digits - for example: 01-oct-98, not 1-oct-98. If your encryption code never expires, the year ( yy ) in your expiration date will be 00.
This chapter describes procedures for interacting with Rational Software Corporation's Technical Support services.
Online support can be found on the World Wide Web at the following locations:
http://www.rational.com/support/index.jsp
This location includes a section for Rose UNIX which provides step by step instructions in relation to using Rose and solving common problems.
http://solutions.rational.com/solutions/
This location includes a search engine to help locate information on commonly asked questions. There is also a section regarding specific Rose UNIX issues.
When Contacting Rational Technical Support, please be prepared to supply the following information:
If your site has a designated, on-site support person, please try to contact that person before contacting Rational Technical Support.
Rational Customer Support can provide information and assistance via:
Please look at Rational's web site at www.rational.com for current customer support listings.
Telephone support is available Monday through Friday from 6:00 a.m. to 6:00 p.m. Pacific time. International telephone support hours span the normal local business hours.
Sometimes Rational technical support engineers will ask you to fax information to help them diagnose problems. You can also report a technical problem by fax if you prefer. Please mark faxes "Attention: Technical Support" and add your fax number to the information requested above.
The telephone and fax numbers for Rational Technical Support are:
You can obtain technical assistance by sending electronic mail to support@rational.com . Electronic mail is acknowledged immediately and is usually answered within one working day of its arrival at Rational. Please include the information requested above with a description of your problem when reporting a problem. When sending e-mail concerning a previously-reported problem, please include in the subject field: "re: Log XXXXX", substituting your assigned support log id for XXXXX.
You can exchange information with Rational through the Internet, using Rational's anonymous FTP site. The service is available 24 hours a day, 7 days a week. To access the site:
You can also correspond with Rational at the following mailing addresses. Please mark correspondence to expedite its routing once it reaches Rational - for example: "Attention: John Smith" or "Attention: Technical Support."
Rational Software Corporation
18880 Homestead Road
Cupertino, CA 95014
U.S.A.
Rational Software AB
Celera AB, Box 26
S-175 21 Järfälla
SWEDEN
Rational Software Corporation Pty Ltd
Zenith Center
Level 13, 821 Pacific Highway
Chatswood NSW 2067
AUSTRALIA
RATIONAL SOFTWARE DO BRASIL LTDA.
Rua Guarara, 529, conj 72
Jardim Paulista - Sao Paulo - SP 01452-001
BRAZIL
Rational SARL
Immeuble de la Gare
1, Place Charles de Gaulle
78180 - Montigny le Bretonneux
FRANCE - C - 78180
Nihon Rational Software K.K.
SAISEI Ikedayama Bldg 2F
5-10-25 Higashi Gotanda
Shinagawa-ku, Tokyo 141
JAPAN
Rational Software Korea Ltd.
10fl, WonBang Bldg
143-42, Samsung-dong, Kangnam-ku
Seoul, 135-090
KOREA
Rational International
7F-4, 2 Lane 150, Hsin-Yi Road, Sec. 5
Taipei, Taiwan, R.O.C.
Rational Software Corp. (India) Pvt. Ltd.
No. 40, 100 Feet Road, 4th Block
Koramangala, Bangalore 560 034
INDIA
Rational GmbH
Rosenstraße 7
Großhesselohe
Pullach im Isartal D-82049
GERMANY
Rational Technology Limited
First Floor, Olivier House
10 Marine Parade
Brighton
East Sussex BN2 1TL
U.K.
The following describes the Rose/C++ for UNIX operating system runtime and/or patch requirements.
The requirements listed below, are in relation to the following platforms (operating system versions):
Note:
This release has been tested with the following patch versions. While we encourage you to contact the appropriate vendor to determine if a patch has been superseded we cannot guarantee release compatibility with a patch version we have not yet tested.
Please contact
support@rational.com
if you encounter any compatibility difficulties after installing a patch which may have superseded any of the patches listed below.
Rational Rose/C++ for UNIX requires that the appropriate HP aC++ runtime be installed on your HP-UX 10.20 machine:
To verify the versions installed on your system, run 'what' on each file (ie):
what /usr/lib/aCC/dld.sl
If the appropriate aC++ runtime is not installed, you will need to install the following necessary HP-UX OS patches.
If /usr/lib/dld.sl (version B.10.27 or greater) is not installed, we recommend installing the following HP-UX OS patch to enhance operation of the dynamic loader (dld.sl) and to avoid erroneous "out of memory" error messages:
These patches are included in your release under the .../install/patches/hppa_hpux directory.
( The 4.0.16b Release included PHSS_13625 which has been recalled by HP. PHSS_10765 is recommended until a new patch PHSS_14716 is available - check with HP to see if this patch is available. )
The aC++ runtime environment is now part of the standard HP-UX OS distribution, beginning with 10.20ACE, eliminating the need for the HP-UX OS patches described above.
When you display an application running on the hp700mt platform to a different platform, the application does not exit properly if you are using a csh or tsh shell. When you exit the application, the xterm continues to receive carriage returns and you must kill your xterm session. If you are displaying on an HP workstation, the application exits properly. HP patch PHCO_13632 is a csh patch that fixes the problem for csh, but a patch for tsh is not available yet. This error typically only occurs with rlogin, so using telnet instead may be a temporary workaround. If this error affects your application, contact Rational Technical Support for the current status.
Note:
**Prior to Installing HP-UX OS Patches**
The OS patches included in this release may have been superseded with newer patches. In order to obtain information in relation to the latest HP-UX patch(es), contact either location below.
HP WWW Patch Site (Electronic Support System)
http://us-support.external.hp.com/
Rational Rose/C++ for UNIX requires that the "libsvld.a" archive from the AIX Shared Library Hookable Symbols Runtime Environment (RTE) be installed on your system.
Attempting to run Rose/C++ for UNIX without this archive, will typically generate the following error message:
Could not load program ../release/rose.4.0.16b/rs6k/bin/rose_cpp_exe
Could not load library libsvld.a[dl.so]
Rational Rose/C++ for UNIX requires that the following SGI patches be installed on your system.
For your convenience, these patches are included in your release under ../install/patches/mips_irix5.
Carefully, read the README file associated with each patch to verify the patch is correct for your specific machine and processor.
In addition, the OS patches included in this release may have been superseded with newer patches. Obtain current patch information from the following SGI website.
SGI WWW Patch Sitehttp://support.sgi.com/surfzone/patches
Rational Rose/C++ for UNIX requires that the Solaris Shared library patch for C++ ( Patch-ID# 101242-13, or greater)), be included on your system.
For your convenience this patch is included in your release under
../install/patches/sun4_solaris2
.
To verify if this patch has been installed, run the following command:
showrev -p | grep -i 101242-13
*Note: Special Instructions When Installing Patch-ID#: 101242-13 on Solaris 2.6:
This patch may be installed on Solaris 2.6. In order to install the patch, run "pkgadd" as described in the "README.101242-13" file.
Do not
remove (do not run pkgrm) the SUNWlibC package (if it is installed), as it includes additional files (/usr/lib/libdemangle.so.1 & /usr/lib/libdemangle.so) necessary for Solaris 2.6.
In addition, the OS patch included in this release may have been superseded with a newer patch. Obtain current patch information from the following SUN Web site.
SUN WWW Sitehttp://access1.sun.com/search.html