Version 2003.06.13, November 2004
This file last updated: 11/16/2004
Material ID/Part Number: C818ANA
This documentation (the "Work") is protected under the copyright laws of the United States and/or other jurisdictions, as well as various international treaties. Any reproduction or distribution of the Work is expressly prohibited without the prior written consent of IBM Corporation.
Product changes described in this document and contained within this service release apply if you are upgrading from v2003.06.12.
These Service Release Notes include:
Service release v2003.06.13 contains product fixes and new features for IBM Rational Test RealTime product.
This IBM Rational service release includes important product fixes, and may include new features. It is developed for a specific product version and does not affect the licensing of your products. Since there is no effect on licensing, the service release does not allow you to configure licensing while you apply it to the software. You will, however, be asked to accept the service release license agreement before installing.
This service release allows you to update selected IBM Rational components on your system. You do not have to find and select product-specific service releases. Because a service release is cumulative, you can apply the latest service release without applying earlier service releases. After you apply a service release, you may see new shortcuts or files. The service release updates the IBM Rational product's version number; for example, from 2003.06.00 to 2003.06.13. You can see the change in the "About IBM Rational Test RealTime " dialog box accessible from the product's Help menu, or in the "Rational Installed Product Information" dialog box, which can be accessed from the Start menu.
What's New in This Service Release
Getting Started
Upgrades
Installation Information
Installation Issues
Defects and Changes
Defects and Limitations In This Service Release
Defects Fixed In This Service Release
Contacting IBM Rational Software Support
It
is now possible to build libraries, including shared libraries (including
dll on Windows), which can be instrumented with any of the runtime analysis,
and be reused for building instrumented applications or component test
drivers.
Editors
have been improved to ease the creation and modification of test scripts.
Less
time and memory is required to load large test projects and test reports.
Assembler
files can now also be built by the user interface as the same time as the C
or C++ files of the application under test.
All
the reports of the current opened project can now be exported into HTML at
once. When performing this operation, a HTML index of all the HTML exported
reports is created.
The
export to HTML report is now also available from the command line.
The
Contract Check capability can now be also be used independently of the
Component Testing for C++ feature. Meaning that there is no more need to
create a test. Users can create a contract file and apply it to either an
application or a library being build within the Test RealTime user
interface.
Protected
and private attributes and method can now be used when defining a Component
Test for C++. An option can be selected to will automatically add a friend
statement to the classes under test.
The
memory profiling for C/C++ offers the capability to find from where the
memory errors come. This new mechanism allow users to define how often the
memory is scanned for detecting ABWL/FMWL errors. A breakpoint can also be
automatically setup when an error is detected allowing developers to
directly debug on the right spot.
The
minimum and maximum time spent in a function is now also computed by the
performance profiling feature in C and C++, allowing a more complete
understanding of any performance issue.
The
new keyword _nocheck in the definition of stubs will allow not to check one
or several parameters of the stubbed function.
Users
can now get one test report for two executions in different context. The
obtained values of the two executions are compared, and differences are
highly in the report. This is very useful for checking that the same
behavior is observed when running a test first on a host environment and
then on a target, or first with code coverage enabled, and then without it.
Stubbing
of separate procedures is now supported.
The
new keyword _nocheck in the definition of stubs will allow not to check one
or several parameters of the stubbed function or procedure.
In
Multi-thread mode, a thread launcher is now automatically created.
Tests
can also be run in local without having to use the supervision mechanism.
Code
coverage results now takes into account manual code review. Users can
designate components as reviewed, and therefore they would count as covered
in the coverage rates.
Capsule
inheritance is now supported by the model coverage view.
Loading
model or code coverage results takes less time.
New
tutorial for the Component Testing and Code Coverage for the Ada language.
More
examples for the advanced capabilities of the Component Testing tools.
All
the online help books have been merged in one searchable online help.
TDP
technology now supports DLL that are loaded and unloaded during the
execution.
New
Troubleshooting section in the TDP guide will help users to find what is
going wrong with the TDP they have adapted or created from scratch for their
own target environment.
A
new set of examples is delivered and constitutes a TDP test suite to help
users to check that newly developed TDPs are thoroughly tested before it is
used.
These Release Notes are accurate at the time this product was prepared for release. The most recent version of this file is available in the IBM Publications at http://www.ibm.com/shop/publications/order. Search for C818ANA to find the latest version of these Release Notes in the IBM Publications Center. (To search for the IBM Publications Center, go to http://www.ibm.com and enter "IBM Publications Center" in the Search field.)
New platforms supported:
Red
Hat Enterprise Linux Workstation Edition 3.0
SuSE
9.1 Professional
Windows
XP Professional Edition SP2
Keep the following current v2003 documents easily accessible during this installation:
For Upgrade information, see the "IBM Rational Suite Upgrade Guide."
For upgrade and installation information, see the "IBM Rational Test RealTime Installation Guide"
For upgrade and installation information, see the "IBM Rational Test RealTime Installation Guide"
For upgrade and installation information, see the "IBM Rational Test RealTime Installation Guide"
See the IBM Rational Suite Release Notes.
See the IBM Rational Suite Release Notes.
See the IBM Rational Suite Release Notes.
See the IBM Rational Suite Release Notes.
This section identifies additional defects and limitations associated with IBM Rational Test RealTime product that were not included in earlier versions of IBM Rational Test RealTime Release Notes.
| Component | SubComponent | RATLC ID/APAR | Description |
| Component Testing for Ada | Test Scripts Compiler | RATLC00866469 / No APAR | When stubbing
a package and a protected unit from this package at the same time, you
cannot use a stub call like this : STUB <package>.<protected>.<function>() because <package> is not recognized. Workaround: use the following syntax : STUB <protected>.<function>() |
| Component Testing for C | Test Scripts Compiler | RATLC00866246 / IC42063 | Large arrays in VAR INIT line in .ptu test script provoke abnormal termination. |
| Component Testing for C | Test Scripts Compiler | RATLC00378538 / IC42471 | The
test script compiler only support up to one hundred INIT IN values for a
single VAR statement Workaround: create multiple TEST ... END TEST blocks limited to 100 different values of the INIT IN. |
| Component Testing for C | Test Scripts Generator | RATLC00866529 / IC43144 | The following
declaration, which is ANSI-C compliant, is not supported: const int my_array[] = { #include "integers.inc" }; |
| Component Testing for C | RATLC00866541 / IC43178 | When stubbing
a function with a const pointer, the input type _inout is generated
by the test script generator. A compiler warning is then generated when
compiling the ptu test script. Workaround: to remove the complier warning, change the input type to _in. |
|
| Component Testing for C++ | RATLC00866376 / IC42739 | Using the -config option while specifying an option which is not used in the project does not produce a warning. Studio silently uses one of the Configurations available from the project. | |
| GUI | Editor | RATLC00865580 / IC39763 | In some cases,
when printing a hardcopy of the test report (xrd), images can be shifted
forward or backward. Therefore, data could be missing in the printed report. |
| GUI | Project Management | RATLC00866257 / IC42136 | Using an environment variable to define an absolute path of a file is not supported by Studio. |
| GUI | Project Management | RATLC00866253 / IC42120 | In the
"Test Selection" dialog box for a Component Test for C node, the
families are incorrectly displayed. It considers the list of families
defined in the test script as space separated instead of comma separated. Workaround: put spaces around the comma and do not select the comma in the list displayed by the test selection dialog box. |
| GUI | RATLC00866247 / IC42068 | After having run tests in headless mode using the command line of studio, the results are not available directly in the user interface when clicking on a test node, they need to be loaded using the "browse" option of the file menu. | |
| System Testing for C | Test Scripts Compiler | RATLC00450977 / No APAR | Japanese font
in PRINT causes error "Abnormally terminated script analysis" If you enter Japanese characters in PRINT instruction in the system testing script, "Abnormally terminated script analysis" appears. |
| Component | SubComponent | RATLC ID/APAR | Description |
| GUI | RATLC00865539 / No APAR | Studio might abnormally terminate when perform the action 'refresh files information'. | |
| GUI | RATLC00865542 / IC39415 | In the settings dialog box the option "Do
not display unnamed classes" is ambiguous. The "Yes" answer
can be interpreted as "Yes I do not want to instrument unnamed classes" or "Yes I do want to instrument unnamed classes". In reality the option "Yes" displays unnamed classes whilst "No" does not. As most compilers don't like the instrumentation of anonymous classes the default of "Yes" provokes problems. |
|
| GUI | RATLC00865577 / IC39797 | The keywords MATCHING, INIT and EV are not highlighted by the test script editor. | |
| GUI | RATLC00865629 / IC40339 | When running tests in headless mode, the project information file (.inf) should be automatically created without prompting a dialog box. | |
| GUI | RATLC00866247 / IC42068 | After having run tests in headless mode using the command line of studio, the results are not available directly in the user interface when clicking on a test node, they need to be loaded using the "browse" option of the file menu. | |
| GUI | Build Mechanism | RATLC00451360 / IC38390 | The GUI sometimes does not notice that a
process has died and so loops forever. When running a sequence of System Testing nodes on Solaris, the GUI sometimes does not notice that a process has died and so loops forever. |
| GUI | Build Mechanism | RATLC00865573 / IC39703 | Test Selection on a Component Testing for C node do not work properly. |
| GUI | Editor | RATLC00452342 / IC38538 | Backspace mucks up the editor on Japanese
source file. In some cases, using the backspace while editing a source file, mucks up the editor. |
| GUI | Editor | RATLC00865533 / IC39356 | After having loaded a large project, pull-down menus might not work correctly. |
| GUI | Editor | RATLC00865580 / IC39763 | In some cases, when printing hardcopy of the
test report (xrd), images can be shifted forward or backward. Therefore, data could be missing in the printed report. |
| GUI | Editor | RATLC00865665 / IC40399 | When executing again the same project with report windows already opened, the user interface might abnormally terminate. |
| GUI | Editor | RATLC00866034 / IC41316 | On HP-UX machines, the source code editor slows down when opening a parenthesis. |
| GUI | Project Management | RATLC00865617 / No APAR | The Copy/Paste/Cut/Delete menu entries are greyed when a file is selected in the Project Browser. |
| GUI | Project Management | RATLC00865618 / No APAR | After having performed a copy/paste action
using shortcut keys Ctrl-C and Ctrl-V, if the user tries to perform an
Undo using Ctrl-Z, no Undo action is performed. Instead the parent node of the pasted item is deleted. If this node is a project, it is closed. |
| GUI | Project Management | RATLC00866253 / IC42120 | In the "Test Selection" dialog box
for a Component Test for C node, the family are incorrectly displayed. i.e. it considers the list of families defined in the test script as space separated instead of comma separated. |
| GUI | Project Management | RATLC00866257 / IC42136 | Using an environment variable to define an absolute path of a file is not supported by Studio. |
| GUI | Project Management | RATLC00866259 / IC42145 KR01649 | If a family is selected and the project is
saved, the family will be saved as a service. If the project is closed and reopened the selected family is not shown any more. |
| GUI | Settings | RATLC00865524 / IC39339 | Try to select on a given test script file .ptu
(right-click with mouse > "Test selection ...") It is impossible to select more than one test of a given Service (either all, or one, but not just some). |
| GUI | RATLC00517300 / IC38291 | The tpf files seems to grow and grow, eventually causing the generation of a memory report to fail. | |
| GUI | RATLC00520375 / IC39912 | A long WRAP/REQUIRE/ENSURE statement will result into an abnormal termination. | |
| GUI | RATLC00865193 / No APAR | In the Code Coverage viewer, the Macro viewer might comes up with a wrong size. | |
| Component Testing for Ada | Test Script Compiler | RATLC00865460 / No APAR | Empty report generated with error "TestRT-F-LEXERRTDC" displayed. |
| Component Testing for Ada | Test Script Compiler | RATLC00865502 / IC39212 | Test script compiler fails with internal error. attolpreproADA gives error "CASE overflow in the module generate_tagged_recursive_string_mask : bad type" |
| Component Testing for Ada | Test Script Compiler | RATLC00865609 / IC39905 | Internal error raised on access type. |
| Component Testing for Ada | Test Script Compiler | RATLC00865615 / IC39956 | Referenced type not generated by test script compiler. |
| Component Testing for Ada | Test Script Compiler | RATLC00865633 / IC40194 | Command line option -restrict=nopos or =noimage do not completed remove the generation quote POS or IMAGE statements. |
| Component Testing for Ada | Test Script Compiler | RATLC00865657 / IC40343 | The test script compiler generates references to the base type of a subtype instead of the subtype in the generated code. Because there is no "with" of the base type (only the package containing the subtype is with-ed) the code does not compile. |
| Component Testing for Ada | Test Script Compiler | RATLC00866469 / No APAR | When stubbing a package and also a protected
unit from this package, you cannot use a stub call like this : STUB <package>.<protected>.<function>() because <package> is not recognized. |
| Component Testing for Ada | Test Script Compiler | RATLC00866589 / IC43294 | Simulating separate procedures results in
abnormal termination: circumstances: - context clauses, specific to the whole PTU; - using body global variables |
| Component Testing for Ada | Test Script Generator | RATLC00452343 / IC37937 | Test script including test of a generic which is a child of a generic fails to compile. |
| Component Testing for Ada | Test Script Generator | RATLC00866375 / IC42734 | Incorrect test script is generated when stubbing a function of the package under test which is separate where all functions are included. |
| Component Testing for Ada | Wizard | RATLC00866568 / IC43244 | In the user interface, if you select the
configuration with a TDP Ada 95, then open the Component Test for Ada
Wizard, and click on "Configuration Settings" and in
"General" > "Target Deployment Port" and set
"Sources Language File" to Ada95. Then, only C and C++ files are now show in the list, you cannot add Ada files. |
| Component Testing for C | Report Generator | RATLC00865720 / IC40568 | If the directory for the reports is modified in the user interface then, although the report is generated in the right place the path of the report in the report header is incorrect. |
| Component Testing for C | Test Script Compiler | RATLC00377568 / IC41255 | Using the FORMAT instruction to display one variable in hexadecimal could result in having all the variables of the same type (typedef) displayed in hexadecimal. |
| Component Testing for C | Test Script Compiler | RATLC00378538 / IC42471 | The test script compiler can only support up to one hundred "INIT IN" values. |
| Component Testing for C | Test Script Compiler | RATLC00865550 / IC39568 | Code generated by test script compiler is incorrect when a stub parameter which is a struct is initialized with variable. |
| Component Testing for C | Test Script Compiler | RATLC00866246 / IC42063 | Large array in .ptu VAR INIT line provokes abnormal termination |
| Component Testing for C | Test Script Compiler | RATLC00866250 / IC42083 | If a parameter of a stubbed function is declare as an array, e.g. int[], wrong C code is generated. |
| Component Testing for C | Test Script Compiler | RATLC00866427 / IC42861 | When the array index in a VAR in an environment line contains a type suffix, such as 'u', the Test Plan compiler aborts with an internal error. |
| Component Testing for C | Test Script Compiler | RATLC00866559 / IC43209 | VAR or STUB lines involving as expected value 0xFFFFFFFF will always be OK, if the returned value is different from 0. |
| Component Testing for C | Test Script Generator | RATLC00865659 / IC40361 | Test script generator gives various warnings when encountering multi-line macro definitions. |
| Component Testing for C | Test Script Generator | RATLC00866529 / IC43144 | The following declaration, which is ANSI-C
compliant, is not supported: const int my_array[] = { #include "integers.inc" }; |
| Component Testing for C | RATLC00865490 / IC41946 | The INCLUDE PTU keyword should only be used to include scripts that do _not_ contain BEGIN or HEADER keywords in them, if these keywords have already been used in the script doing the including. | |
| Component Testing for C | RATLC00865520 / No APAR | Bad warning generated by attolpreproC on array
index when using a typedef to cast the size of an array: #typedef unsigned int Uint32; #int Tab[(Uint32)2]; In order to get the warning, the array must be initialized in an environment: environment test ARRAY Tab, init={others=>0}, ev== end environment use test The warning says: TestRT-W-ARRINDENV, [.\struct.ptu:31] Invalid array index with environment overloaded Tab[] |
|
| Component Testing for C | RATLC00865772 / No APAR | Stubbed functions does not always have a return statement, which might result in a warnings with some compilers. | |
| Component Testing for C | RATLC00866217 / IC42701 | Environments with parameters do not initialize STUB calls in some cases. | |
| Component Testing for C | RATLC00866541 / IC43178 | When stubbing of a function with a const
pointer, the input type _inout is generated by the test script generator. Then, a compiler warning is generated when compiling the ptu file. |
|
| Component Testing for C++ | Instrumentor C++ | RATLC00865566 / IC39631 | Instrumentor does not support the following C++ construction: class MyClass { template <typename T> int f(T *); void g(); }; |
| Component Testing for C++ | Instrumentor C++ | RATLC00865598 / No APAR | An internal error occurs in the following
situation: class A : B { void f(B b); }; i.e. a method has a parameter of type that is the ancestor of the defining class And a WRAP clause is defined for this method. |
| Component Testing for C++ | Instrumentor C++ | RATLC00865672 / No APAR | When using the option "-BODY=" the contract check C++ instrumentor might generate incorrect code. |
| Component Testing for C++ | Instrumentor C++ | RATLC00866278 / IC42370 | When performing contract checking on a destructor of a class the code for the contract checking is not generated for the destructor on Windows. Thus in the report the contract check is always marked as "Not executed". |
| Component Testing for C++ | Report Generator | RATLC00865658 / IC40356 | abnormal termination of the report generator on a large number of class attributes. |
| Component Testing for C++ | Report Generator | RATLC00865709 / IC40494 | In the "1. Report Information" section of the test report, some test cases which failed are not reported. |
| Component Testing for C++ | Report Viewer | RATLC00865786 / IC40773 | CHECK PROPERTY keyword does not show the optional comment in Trace when specified. |
| Component Testing for C++ | Test Script Generator | RATLC00865695 / IC40464 | If in the settings (Build > Compiler), the include path points to a relative location starting with dots, like "..\src" or "..\..\src", then the path generated in the .dcl file will be truncated up to the first non-dot letter. |
| Component Testing for C++ | Test Script Generator | RATLC00866265 / IC42178 | The test script generator (atostart), also used to generate the static metrics, is limited to 256 command line parameters. Note you have to add to the number of parameters on the command line the number of parameters in the TDP's atl.opp file. |
| Component Testing for C++ | Wizard | RATLC00865537 / No APAR | A progress bar is displayed when metrics are
calculated in the Component Test Wizard. Closing this progress bar by clicking on its upper right cross button leads to an abnormal termination of Studio. |
| Component Testing for C++ | RATLC00138724 / IC41287 | Attempting to use _ATO_result more than once in an ENSURE statement causes an error at build time. | |
| Component Testing for C++ | RATLC00451948 / IC37708 | If a C++ Component project has to be moved to another directory, all relative paths (../../..) are not updated. Issue occurs on HP and Solaris | |
| Component Testing for C++ | RATLC00452318 / IC37918 | Regression test cannot be run if project under
version control It is not possible to run only a regression test without having to regenerate/recompile the test if all the project test assets are under source control. |
|
| Component Testing for C++ | RATLC00866376 / IC42739 | Using the -config option and specifying an option which is not used in the project does not yield a warning. Studio silently uses one of the available from the project. | |
| Component Testing for C++ | RATLC00866381 / IC42754 | The user interface (studio) still opens dialog boxes on errors when used in headless mode from the command line. | |
| Component Testing for Java | Instrumentor Java | RATLC00138966 / IC41373 | The Java parser now reports a warning when an archive (jar file) is not found in the classpath rather than exiting with a fatal error. |
| Component Testing for Java | Metric Generator | RATLC00865605 / No APAR | Multiple conditions and the ternary "*?*:*" statement are ignored when performing a Metrics calculation in Java. |
| Component Testing for Java | Metric Generator | RATLC00865787 / IC40776 | If two files in separate directories have the same file name, only one of them can be viewed in the Metrics viewer window. |
| Component Testing for Java | RATLC00458863 / IC41557 | J2ME WTK 2.1 not supported out of the box. | |
| Documentation | Reference Manual | RATLC00865543 / No APAR | The metcc command is not documented. |
| Documentation | RATLC00866218 / IC41748 | If a STR statement is used in an ENVIRONMENT, then all components are shown in the report, regardless whether the test is OK or not. | |
| Integration with TestManager | Installation | RATLC00865212 / No APAR | Test manager plug-in not installed correctly if
Test RealTime installed first. The Test Manager plug-in is not installed correctly if Test RealTime is not installed with the Test Manager feature: Steps of the installation: 1- Installation of Test RealTime v2003.06.00 with or without Test Manager feature 2- Installation of Team Test 3- Restart the Test RealTime installation to select the Test Manager feature. In this case the files: TestRTConsoleAdapter.dll and TestRTTsea.dll are not copied in the Test Manager directory. |
| Integration with TestManager | RATLC00865379 / No APAR | TestManager integration does not work on Windows NT4. | |
| Plug-in RoseRT | Build | RATLC00865627 / IC40124 | The nointrdir flag set used to exclude the RoseRT TargetRTS should point one level up in the directory hierarchy. |
| Plug-in RoseRT | RATLC00457155 / IC40923 | It is not possible to use the integration with RoseRT with the TDP for Visual Studio 7.0 out of the box. | |
| Plug-in Visual | RATLC00865578 / IC39835 | If you build a MFC application in .NET 2003 studio using the TestRT integration, the result cannot be seen, only *.tsf are shown. | |
| Runtime Analysis | Code Coverage Viewer | RATLC00865488 / IC39156 | Coverage Viewer does not display a warning when
count information is ignored. If you re-instrument an application with count information, option -COUNT, then the .tio file contains traces with count information and traces without count information. The Coverage Viewer refuses to display count information. If you run "attolcov" on the same fdc and tio files then it displays a warning message "WARNING: Some traces are count-orientated and others not, count is ignored". |
| Runtime Analysis | Code Coverage Viewer | RATLC00865744 / IC40634 | Coverage report shows magnifying glasses containing partially only '}'. |
| Runtime Analysis | Instrumentor Ada | RATLC00865528 / IC39349 | The access to a protected type is not recognized by the Ada parser. |
| Runtime Analysis | Instrumentor C/C++ | RATLC00865300 / No APAR | Instrumentor fails with internal error. First issue is a break inside a Gnu expression-statement. Second issue is a non standard use of template specialized methods as friend. |
| Runtime Analysis | Instrumentor C++ | RATLC00139405 / IC41615 | With Code Coverage, the colorization of the portions of code following a switch inside a while loop might be wrong in the viewer. |
| Runtime Analysis | Instrumentor C++ | RATLC00865544 / IC39467 | Instrumenter might fail to instrument a 'if' statement without bracket which contains a call to a constructor. |
| Runtime Analysis | Instrumentor C++ | RATLC00865631 / IC40133 | Incorrect line numbers might be given in the Memory Profiling report |
| Runtime Analysis | Instrumentor C++ | RATLC00865673 / IC40133 | When the result of a 'new' operation is stored
in a static member variable of a class during the execution of a static
member function of the class (classic getInstance of a singleton class) and the 'new' operation is after an 'if' statement, then the instrumentor does not insert the line number of the new statement. Hence if a memory leak occurs the line numbers are not correct. |
| Runtime Analysis | Instrumentor C++ | RATLC00865770 / IC40671 | C++ instrumentor with memory profiling option might insert a reference to a static variable before the variable is declared. |
| Runtime Analysis | Launcher | RATLC00865607 / No APAR | When the compilation command includes some dependency generation options such as -MD -MP -MF, attolcc cuts the -MD option when compiling the instrumented code. This leads to compilation errors because the -MF option must be used with the -MD one. |
| Runtime Analysis | Launcher | RATLC00865616 / No APAR | attolcc gives a incorrect command line to gcc, the object file is misplaced. |
| Runtime Analysis | RATLC00453969 / IC39175 | Instrumentor generates an illegal code on macro expansion in 'case'
statement. The error 'Case expression not constant' occurs when the coverage is turned on. A sample code below reproduces the issue: #define CALC(a) (a==1? 1:2) int main(void) { int a=1; switch(a){ case CALC(1): break; } } |
|
| Runtime Analysis | Memory Profiling Viewer | RATLC00865532 / No APAR | Links from Java Memory profiling reports to
source code do not work on Windows. This does not happen for delivered examples. It however happens for projects created from scratch by the user. |
| Runtime Analysis | RATLC00865791 / IC40882 | C++ instrumentor generates code that does not
compile when Runtime Tracing is on, with the following error: class `foo' can not be fully instrumented because its base class `Type' is not instrumented (state chart check may fail) |
|
| Runtime Analysis | RATLC00865806 / IC40898 | When running C++ tests using the "C++ WinCE .NET Unmanaged" configuration, no results are obtained at the end of the test run. | |
| System Testing for C | Report Generator | RATLC00865498 / IC39207 | If the command line tool atsmerge terminates with warnings, the expected return-code for this run would be '3' according to documentation, instead of '0' when warning messages are issued. |
| System Testing for C | Report Generator | RATLC00865768 / IC40670 | System Testing report generator (atsmerge) abnormally terminates if lines are too long in the intermediate trace file (.rio). |
| System Testing for C | Report Generator | RATLC00866581 / IC43278 | System Test report generator (atsmerge) abnormally terminates when parsing a test result file, generated when the test script was compiled with the -TRACE=ERROR option, due to there being a single line beginning with "z" instead of the usual pair. |
| System Testing for C | Target Deployment Port | RATLC00865719 / IC40566 | When System Testing is used with virtual testers running on a remote machine the compiled virtual tester is not copied onto the target machine and the execution fails. |
| System Testing for C | Test Script Compiler | RATLC00865784 / IC40749 | The System Testing test script compiler does not recognize the following construction: typedef int foo[sizeof(char[2])]; |
| System Testing for C | RATLC00457476 / IC41154 | The report generator does not support extremely long strings with more than 4096 characters in the RIO file, and generates a Lexical Error. | |
| System Testing for C | RATLC00865875 / No APAR | The number of participants to a rendezvous s not computed correctly when using a test script involving 2 instances. | |
| Target Deployment Port | RATLC00865613 / No APAR | The precision defined by RTRT_NBDIGITS_FLT is not take in account correctly | |
| Target Deployment Port | RATLC00865660 / IC40376 | When Runtime Tracing Buffer Enable option is
set to Yes, but multithread option is left to No, then the following link
error is shown when the project is built: TP.obj : error LNK2001: unresolved external symbol __att_print_thread_info |
The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Rational Software Support Home page 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/.