Version
7.0.0.1 iFix001
Before using this information, be sure to read the
general information under Appendix. Notices.
About Rose RealTime v7.0.0.1
iFix001
Installing Rose RealTime v7.0.0.1
iFix001
Rose RealTime Petal Format or
Code Generation
Rose RealTime TargetRTS Changes
Announcements, Changes and
Known Issues
Problems Fixed in v7.0.0.1
iFix001
Files Changed or Added by this iFix
Contacting IBM Customer Support for Rational software
products
This iFix001 Release Note is in addition to the
Release Note for Rose RealTime v7.0.0.1.
Copyright International Business Machines
Corporation 1995, 2007. All rights reserved. US Government Users Restricted
Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM(R) Corp.
This document provides information about
installing and using IBM Rational Rose RealTime, including system and software
requirements; new features and enhancements; current known issues and defects
fixed.
This document provides information intended for
these users:
·
System administrators who
install and configure Rational Rose RealTime
·
Project managers who use
Rational Rose RealTime models and documents
·
Advanced users who implement
integrations of Rational Rose RealTime with other products, work on
international systems and localized versions of the product, or encounter
problems that are undocumented in the product documentation
Documentation for IBM Rational is available
on-line at http://www.ibm.com/software/rational/support/documentation/.
This chapter describes updates to the documentation
that pertain to installing Rational Rose RealTime v7.0.0.1 iFix001.
System and software requirements
This iFix supports the following Operating
Systems:
·
Microsoft Windows 2000
Professional SP4; XP Professional with SP1 or SP2, Vista
·
Red Hat Linux v8.0, 9.0,
Enterprise 3 & 4; SLES 9
·
SUN Solaris 7, 8, 9 & 10
What to do after installation
Toolset
Run the toolset and ensure that the version number
is correct. In Rational Rose RealTime, click Help > About Rational
Rose RealTime and verify that the version number for Rational Rose
RealTime is 6.6.3169.0 (Windows); 6.6.3170.0 (Linux or Solaris). If the version
number is not the same, the Release was not installed correctly.
Code Gen
If you wish to take advantage of the problems
fixed in the code generators, you need to rebuild and re-link your models.
RQA-RT
No additional steps are required.
RTJava Models
No additional steps are required.
C TargetRTS
If you wish to take advantage of the problems
fixed in the C TargetRTS, you need to rebuild your Target RTS libraries and
re-link your models.
C++ TargetRTS
If you wish to take advantage of the problems
fixed in the C++ TargetRTS, you need to rebuild your Target RTS libraries and
re-link your models.
C & C++ Models
If you wish to take advantage of the problems
fixed in the code generators, you need to rebuild and re-link your models.
Connexis(TM)
If you wish to take advantage of the problems
fixed in the DCS, you need to rebuild and re-link your models. It will also be
necessary to rebuild the DCS library if your target is not one of the pre-built
DCS libraries supplied in this Release.
This section describes installing Rational Rose
RealTime Version 7.0.0.1 iFix001.
Note:
Rose RealTime v7.0.0.1 must be installed before installing this iFix.
o
Verify Rational Rose RealTime
v7.0.0.1 is installed by running Start > Programs > IBM Rational >
Rational Software Installed Product Information.
You should see IBM Rational Rose RealTime * Build ID 7.0.0.1.
o
Download the iFix specific to
your v7.0.0.1 Release.
o
Once downloaded double-click
on the iFix *msp file to begin the installation.
o
Press Update
o
Press Next
o
Press Install
o
Installation Complete
o
Verify Rational Rose RealTime
v7.0.0.1 iFix001 is installed by running Start > Programs > IBM
Rational > Rational Software Installed Product Information.
o
setenv $ROSERT_HOME
rational_dir/releases/RoseRT.7.0.0.0
o
copy
RoseRT.v7.0.0.1.iFix001.sun5.tar.gz to temporary directory
o
run
the following command to unzip the patch
o
gunzip
< RoseRT.v7.0.0.1.iFix001.sun5.tar.gz | tar xpf -
§
It
will create a directory "700706301-1"
§
cd
700706301-1
run "./install_sol_700706301_1"
This command will back-up the pertinent files in your Release and install the
iFix. You will then have the
following options:
You can later run this install script to restore Rose
RealTime 7.0 to its state prior
to installing patch:
$ROSERT_HOME/install/patches/install_sol_700706301_1 -restore
You can later run this install script to commit patch
700706301_1.
If you do this, you cannot restore later.
$ROSERT_HOME/install/patches/install_sol_700706301_1
-commit
Committing
a patch will save disk space by removing the backup files.
o
setenv $ROSERT_HOME rational_dir/
releases/RoseRT.7.0.0.0
o
copy
RoseRT.v7.0.0.1.iFix001.linux.tar.gz to temporary directory
o
run
the following command to unzip the patch
o
gunzip
< RoseRT.v7.0.0.1.iFix001.linux.tar.gz | tar xpf -
§
It
will create a directory " 700706301-8"
§
cd
700706301-8
run "./ install_linux_700706301_8"
This command will back-up the pertinent files in your Release and install the
iFix. You will then have the
following options:
You can later run this install script to restore Rose
RealTime 7.0 to its state prior
to installing patch:
$ROSERT_HOME/install/patches/
install_linux_700706301_8 -restore
You can later run this install script to commit patch
700706301_8.
If you do this, you cannot restore later.
$ROSERT_HOME/install/patches/
install_linux_700706301_8 -commit
Committing
a patch will save disk space by removing the backup files.
This section describes any
compatibility issues that could arise from use of this iFix.
This iFix does not introduce any known compatibility
issues with third-party products.
This iFix does not impact or include changes to
existing Petal Format.
There are Code Generation changes included, but no
changes that will cause compatibility issues.
This iFix includes a TargetRTS fix to copy data to
a non-critical section, efficiently allowing the mutex to be available for any
higher priority thread much more quickly.
Refer to the document entitled
“iFix001_TargetRTS_Source_Code_Changes.doc” for a complete description of the
changes.
The Rose RealTime / VxWorks 6.0 Integration includes:
Modified TargetRTS (including C/C++) sources compatible with
VxWorks 6.0.
Integration supported on target board with PPC603 cpu and
VxWorks 6.0 image.
You may deploy any Rose RealTime model on a supported board
and run as usual. (Entry point for
Rose RealTime model remains as “rtsMain” method.)
IMPORTANT: Currently, the VxWorks 6.0 Integration supports only Kernel mode application development only. In order to run existing models on VxWorks 6.0, it will be necessary to rebuild and link with the libraries supplied with this iFix. It will be necessary to choose one of the new targets installed with this iFix.
The new targets are a combination of::
SIMNT (VxWorks 6.0 Simulator)
PPC603 Board (i.e. any target board with MPC8260 or
compatible processor)
Diab & GNU Compilers
Problem ID |
Description |
|
Rose RealTime C |
PK00107 / RATLC00141383 |
The -crlf option, which is documented in
online Help is not available in the source code. -crlf
option re-enabled, to generate the source code with line endings as –crlf. |
Rose RealTime / ClearCase
Integration |
PK44750 / RATLC01188476 |
The ClearCase Label operation may fail in Rose RealTime /
ClearCase integration when using both Base ClearCase and UCM. |
Rose RealTime / ClearCase Integration |
RATLC01188459 |
Rose RealTime / ClearCase integration check-out operation
may fail after performing a ClearCase rename operation. |
Rose RealTime CM |
PK42560 / RATLC01018081 |
cmscripts\mvss ‘cm_add’ & ‘cm_checkin’
are duplicates of the similar ClearCase scripts. |
Rose RealTime C |
RATLC00149371 |
Solaris Rose RealTime code generation performance
degradation when building models with large classes. |
Rose RealTime C++ |
Improved Data copy during Send Operation and Improved
RTDictionary::Find operation If a capsule running on a low priority thread acquires
this mutex and tries to send a large amount of data, the TargetRTS layer
makes a copy of the data, before releasing the mutex. If a high priority thread is waiting
for the mutex lock, it can potentially starve as the low priority thread must
continue to hold the mutex until completing the data copy. The fix for this defect moves copying of data to a
non-critical section, efficiently allowing the mutex to be available for any
higher priority thread much more quickly. Also, the RTDictionary find operation has been improved
by adding a new termination condition. Please refer to Additional
Information (below) for necessary build instructions. |
|
Rose RealTime RQA-RT |
PK18242 / RATLC00144143 |
RQA-RT generated executable may have long execution time. |
Rose RealTime Toolset |
IC38113 / RATLC00517145 |
In Rose RealTime 2002 (and 2003) the incorrect class name
may display for an interaction instance in a Sequence Diagram, in special
cases - when sub-classes are utilized. |
Rose RealTime Toolset |
IC48956 / PK35079 RATLC00144669;
RATLC01186774 |
Rose RealTime may crash or hang when copying inherited
states or performing other copy/paste operations in State Diagram.
Solaris Rose RealTime crash: N: :__1cPshPropClipboardSMwGetClipboardOpen6M_pnGHWND____ |
Rose RealTime Toolset |
PK28326 / RATLC00992811 |
Renaming an attribute whose type is the containing class
may cause Rose RealTime to crash.
Steps to reproduce:
Work-around: First change the type of the attribute, click Apply, change the name of the attribute, and then change the type back to the desired type. The resulting stack overflow problem now resolved. |
Rose RealTime Toolset |
PK30281 / RATLC00045546 |
The following SUN Solaris Rose RealTime crash could occur when performing ClearCase actions: __1cHCObjectIIsKindOf6kMpknNCRuntimeClass__i_ |
Rose RealTime Toolset |
PK36207 / RATLC00147600 |
In protocols which have symmetrical signal (same name on in
and out signal), it not possible to use the "Options >
Select Compartment Items..." context menu to hide the out
signal. |
Rose RealTime Toolset |
PK40061 / RATLC01187603 |
Access Violation may occur upon opening large model with
several Unresolved Reference warnings. |
Rose RealTime Toolset |
RRTEI: Method AddLogicalPackageDependency fails to
add a dependency.
As per the Rose RealTime Help, AddLogicalPackageDependency
takes two arguments. The second argument is the Name of the supplier logical
package dependency relation. Passing just the name of the package, not fully
qualified name - the relationship will get created but when trying to create
the package on the diagram - the supplier package search fails because of the
absence of the fully qualified name and Rose RealTime may crash. A check is added to check for qualified name and valid
name. If name is not qualified or valid, an error dialog is displayed. Please
refer to Additional Information
(below) for details. |
|
Rose RealTime Toolset |
PK47815 / RATLC01193843 |
After running a "Find in" in the model,
the results are displayed in the "Find" output window. In Rose
RealTime v2003.06.13, you could right click on an element and choose "Select
in Browser" and the browser would navigate to this element. In Rose RealTime v7.0 and v7.0.0.1, right clicking on the element found - no context menu is displayed, therefore, it is not possible to choose "Select in Browser". Work-around:
Double-click the element found to open the Properties window
for the element and then in the bottom left hand corner of this window, click
on "Browse" and choose "Select in Browser". |
Rose RealTime Toolset |
PK40910 / RATLC00148279 |
The Rose RealTime / ClearCase “Move” feature is not retained between sessions. This information is now retained in the *.ini file. |
Rose RealTime Toolset |
RATLC00147314 |
Move Feature for models maintained in ClearCase. |
Rose RealTime Web Publisher |
IC52000 / RATLC01187656 |
Linux Only Issue: Rose RealTime may crash when
publishing large diagrams.
Whenever a diagram with more than ~20 mega pixels is encountered,
Rose RealTime would crash. Now, whenever a diagram with more than ~20 mega pixels is
encountered, an error dialog box will display to indicate it is necessary to
reduce the size of the diagram. You may either continue Web Publishing by selecting ”Yes”
or Cancel the publishing by selecting “No”. If you choose to continue web publishing, it will skip
publishing the large diagram. To publish this diagram, you need to reduce
it’s size and re-start web publishing. |
§
AddLogicalPackageDependency
RRTEI function call (PK40362 / RATLC00148207)
The prototype of the
function AddLogicalPackageDependency is:
AddLogicalPackageDependency
(theName : String, theSupplierLogicalPackageName : String) :
LogicalPackageDependency.
The second argument, theSupplierLogicalPackageName is the name of the supplier
package in the dependency relationship. This should be the fully qualified name
of the package in the model. You may either specify fully qualified name
explicitly or use the RRTEI function GetQualifiedName(). If the supplier
package is not found in the model, a script error dialog is presented.
The error dialog will be displayed, in the following
scenarios:
1)
The
supplier package is not in the model under Logical View.
2)
Logical
View::supplier_package is not a fully qualified name.
In this case, you may correct the script or the model accordingly.
§
Improved Data copy During Send
Operation and Improved RTDictionary::Find operation (PK32722
/ RATLC00993513)
Refer to the document entitled
“iFix001_TargetRTS_Source_Code_Changes.doc” for a complete description of the
changes.
To incorporate these TargetRTS changes
1.
After applying the TargetRTS
source code changes, build the TargetRTS libraries.
2.
It is necessary to rebuild
Connexis using the latest "TargetRTS” libraries.
3.
The application also needs to
be rebuilt using latest "TargetRTS" libraries.
Note: All Rose RealTime TargetRTS Tornado libraries are provided. Please, extract only the desired set of libraries ( libObjecTime.a, libObjecTimeTypes.a and main.o ).
Solaris
Rose RealTime Fixes Changed or Added
$ROSERT_HOME/bin/RoseRT
$ROSERT_HOME/bin/sun5/cmscripts/cc/cm_getcaps
$ROSERT_HOME/bin/sun5/RoseRT
$ROSERT_HOME/bin/sun5/RoseRT.rsb
$ROSERT_HOME/bin/sun5/rtcbld.dll
$ROSERT_HOME/bin/sun5/rtcbld.rsb
$ROSERT_HOME/bin/sun5/rtcgen
$ROSERT_HOME/bin/sun5/rtcppbld.dll
$ROSERT_HOME/bin/sun5/rtcppbld.rsb
$ROSERT_HOME/bin/sun5/rtcppgen
$ROSERT_HOME/bin/sun5/rtjavaui.dll
$ROSERT_HOME/bin/sun5/rtjavaui.rsb
$ROSERT_HOME/bin/sun5/rtrun
$ROSERT_HOME/C/TargetRTS/src/CmdlnObs/init.c
$ROSERT_HOME/C/TargetRTS/src/Dictnary/get.c
$ROSERT_HOME/C/TargetRTS/src/Main/mainLine.c
$ROSERT_HOME/C/TargetRTS/src/target/OSEK_VDX_BCC1/Main/mainLine.c
$ROSERT_HOME/C/TargetRTS/src/WebObs/init.c
$ROSERT_HOME/C++/TargetRTS/include/RTVersion.h
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.ppc603-Diab-5.2.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.ppc603-Diab-5.2.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.ppc603-Diab-5.2.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.ppc603-gnu-3.3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.ppc603-gnu-3.3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.ppc603-gnu-3.3.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.simnt-Diab-5.2.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.simnt-Diab-5.2.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VXWorks60T.simnt-Diab-5.2.2/main.o
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.simnt-gnu-3.3.2/libObjecTime.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.simnt-gnu-3.3.2/libObjecTimeTypes.a
$ROSERT_HOME/C++/TargetRTS/lib/VxWorks60T.simnt-gnu-3.3.2/main.o
$ROSERT_HOME/C++/TargetRTS/src/RTCmdLineObserver/ct.cc
$ROSERT_HOME/C++/TargetRTS/src/RTDictionary/find.cc
$ROSERT_HOME/C++/TargetRTS/src/RTMain/mainLine.cc
$ROSERT_HOME/C++/TargetRTS/src/RTWebObserver/ct.cc
$ROSERT_HOME/C++/TargetRTS/src/target/Eval/RTMain/mainLine.cc
$ROSERT_HOME/Connexis/C++/lib/VXWorks60T.ppc603-Diab-5.2.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VxWorks60T.ppc603-gnu-3.3.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VXWorks60T.simnt-Diab-5.2.2/libDCS.a
$ROSERT_HOME/Connexis/C++/lib/VxWorks60T.simnt-gnu-3.3.2/libDCS.a
$ROSERT_HOME/MISRAC/TargetRTS/src/CmdlnObs/init.c
$ROSERT_HOME/MISRAC/TargetRTS/src/Dictnary/get.c
$ROSERT_HOME/MISRAC/TargetRTS/src/Main/mainLine.c
$ROSERT_HOME/MISRAC/TargetRTS/src/WebObs/init.c
$ROSERT_HOME/WebPublisher/sun5/librosertwebpub.so
$ROSERT_HOME/WebPublisher/sun5/rosertwebpub.rsb
If you have questions about installing, using, or
maintaining this product, contact IBM Customer Support as follows:
The IBM software support Internet site provides
you with self-help resources and electronic problem submission. The IBM
Software Support Home page for Rational products can be found at http://www.ibm.com/software/rational/support/.
Voice Support is available to all current contract
holders by dialing a telephone number in your country (where available). For
specific country phone numbers, go to http://www.ibm.com/planetwide/.
When you contact IBM
Customer Support, please be prepared to supply the following information:
·
Your name, company name, ICN
number, telephone number, and e-mail address
·
Your operating system,
version number, and any service packs or patches you have applied
·
Product name and release
number
·
Your PMR number (if you are
following up on a previously reported problem)
This information was developed for products and
services offered in various countries throughout the world. IBM may not offer
the products, services, or features discussed in this document in every country.
Consult your local IBM representative for information on the products and
services currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right
may be used instead. However, it is the user's responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent
applications covering subject matter described in this document. The furnishing
of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS)
information, contact the IBM Intellectual Property Department in your country
or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United
Kingdom or any other country where such provisions are inconsistent with local
law: INTERNATIONAL BUSINESS MACHINES
CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are
provided for convenience only and do not in any manner serve as an endorsement
of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply
in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information
about it for the purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one) and (ii)
the mutual use of the information which has been exchanged, should contact:
IBM Corporation
Department BCFB
20 Maguire Road
Lexington, MA 02421
U.S.A.
Such information may be available, subject to appropriate
terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all
licensed material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.
Any performance data contained herein was determined in a
controlled environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been made on
development-level systems and there is no guarantee that these measurements
will be the same on generally available systems. Furthermore, some measurement
may have been estimated through extrapolation. Actual results may vary. Users
of this document should verify the applicable data for their specific
environment.
Information concerning non-IBM products was obtained from
the suppliers of those products, their published announcements or other publicly
available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed
to the suppliers of those products.
USE OF SAMPLES CONTAINED IN THIS INFORMATION:
This information may contain sample application programs in
source language, which illustrates programming techniques on various operating
platforms.
Each copy or any portion of these sample programs or any
derivative work, must include a copyright notice as follows:
(c) (your company name) (year). Portions of this code are
derived from IBM Corp. Sample Programs. (c) Copyright IBM Corp. _enter the year
or years_. All rights reserved.
ADDITIONAL NOTICES:
Additional legal notices may be included with the license
agreement accompanying the licensed program described in this document.
TRADEMARKS:
AIX, ClearCase(R), ClearCase Attache(R),
ClearCase MultiSite(R), ClearDDTS(R), ClearGuide(R),
ClearQuest(R), DB2(R), DB2 Universal Database(TM),
DDTS(R), Domino(R), IBM, Lotus(R) Notes, MVS(TM),
Notes, OS/390(R), Passport Advantage(R), ProjectConsole(TM)
Purify(R), Rational, Rational Rose, Rational RoseRealTime, Rational
Suite, Rational Unified Process(R), RequisitePro, RUP(R),
S/390(R), SoDA, SP1, SP2, Team Unifying Platform(TM),
WebSphere(R), XDE(TM), and z/OS(R) are
trademarks of International Business Machines Corporation in the United States,
other countries, or both.
Java and all Java-based trademarks and logos are trademarks
of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are
trademarks of Microsoft Corporation in the United States, other countries, or
both.
UNIX(R) is a registered trademark of The Open
Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United
States, other countries, or both.
Other company, product or service names may be trademarks
or service marks of others.