Product documentation
Abstract
This document contains a complete listing of releases, refreshes, fix packs and interim fixes sorted by version for IBM Rational Logiscope.
Content
Tab navigation
- Release 6.6- selected tab,
- Support Resources
- Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
- Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.
- Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track development progress.
Helpful Hints For Obtaining Technical Assistance:
Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.
If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.
Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog
Table of Contents:
| Link | Date Released | Status |
|---|---|---|
01/04/2013 |
Current |
| APAR | Description |
| PM76546 | Windoc does not report the error, and does not change the selected components list |
| PM78575 | Incorrect MISRA_17_4 rule violation |
| PM78911 | MISRA_5_7 violation reported when the identifier are declared in header file and used in source file |
| Link | Date Released | Status |
|---|---|---|
14/12/2012 |
Superseded |
| APAR ID | Description |
| PM61353 | The metrics (function level) for the functions are displayed in the HTML report with *** |
| PM71602 | Warning: during tcl evaluation? message for MISRA_10_1 rule during analyzing stage. |
| Link | Date Released | Status |
|---|---|---|
03/05/2012 |
Superseded |
| APAR ID | Description |
| PM26737 | "syntax error near unexpected token `('" occurs when building a C audit project through command line. |
| PM47686 | Renaming rules in the ruleset file do not get applied immediately after they are selected in Eclispe. |
| PM57242 | unexpected violation reported by the MISRA-2-10-3 rule. |
| PM57243 | Incorrect violations reported by MISRA_0_1_4. |
| PM57254 | use of "DPP" notation in the C testchecker Report should be fixed. |
| PM46499 | Logiscope crashes with error: full_prepro.exe has encountered problem and needs to close. |
| PM48477 | Building Logiscope rulechecker project requires the qualitychecker license. |
| PM50615 | The Rules tab in Eclipse when opened through Properties does not update the status of the rule. |
| PM52247 | Unexpected behavior of the C++ MISRA rule 2_10_4. |
| PM53642 | Incorrect violations reported by MISRA_0_1_4. |
| PM35909 | Incorrect violations reported by MISRA_15_1_1. |
| PM36560 | CSV files are not generated when the .ref files does not have criterias and factors or both. |
| PM37232 | The html report does not contain the function metric values if Logiscope.ref does not contain criterias and / or factors. |
| PM10285 | Logiscope C++ TestChecker cannot handle the exception handling in constructors. |
| PM27997 | Three metrics results of the TestChecker extension are added to qualitychecker report and these metrics are set to zero. |
| PM38461 | Incorrect violations reported by C++ MISRA6_6_4 rule. |
| PM28848 | Display problem in the table of Kiviat graph, where some values (under the HIGH column) are displayed out of the cell area. |
| PM38582 | Incorrect violations reported by C++ MISRA18_0_1 rule. |
| PM14016 | Variation observed in the value of the metric ap_vg when viewed in the quality report and the viewer. |
| PM38462 | Variation in the metric values observed when viewed in the html report and the viewer. |
| PM37124 | Logiscope counts the "lc_ccomm" metric for functions, that are 'renames of functions' and 'instantiations of generic packages. |
| PM27999 | Unexpected behavior reported by Logiscope plugin when choosing the rulesets in eclispe. |
| PM31119 | MISRA_19_3 rule functioning anomaly. |
| PM31547 | MISRA_14_3 rule anomaly. |
| PM31550 | Expected violation by MISRA 16_8_i or MISRA_Rule83i. |
| PM32575 | Incorrect violation reported by MISRA C++: 2008 rule 6_3_1. |
| PM34215 | Batch command with "-addin export -format csv" overrides option -o
|
| PM35315 | Incorrect violations reported by MISRA_15_3_1. |
| PM34505 | ReviewerAda.pdf documentation and the Logiscope.ref file has to be updated. |
| PM20829 | Error in the syntax of the
|
| PM23809 | Unexpected behavior of Logiscope due to the variation in the function getName" of the "utilities.tcl" script. |
| PM25343 | Improve the CodePres_26_CommentDefinition rule description and the help documentation. |
| PM10355 | Initialization of struct causes tags in the struct to violate the rule 5.4 in misra-c 2004. |
| PM25531 | MISRA5_5 rule description and the help documentation should me improved. |
| PM26795 | MISRA_8_4 rule reports incorrect violations. |
| PM26403 | MISRA_8_5 doesn't report violation for object definition. |
| PM22810 | MISRA_8_10 rule misses violation. |
| PM25222 | MISRA_10_1 rule depicts unexpected behavior. |
| PM26618 | Sufficient justification should be provided for same violations reported on the same line. |
| PM23772 | Logiscope MISRA12_4 rule misses violation. |
| PM22827 | MISRA_13_4 rule misses violation when used with MISRA_Rule18. |
| PM22811 | MISRA_16_1_i rule misses violation in Logiscope 6.6.3. |
| PM22640 | Logiscope misses violation for MISRA_16_6 rule. |
| PM27025 | Regression between 6.3 and 6.6.3 with Rule MISRA 16_8_iii. |
| PM27143 | MISRA_17_4 rule reports incorrect violation. |
| PM23180 | MISRA_18_2 rules miss violation. |
| PM24683 | MISRA19_14 rules reports unexpected violations. |
| PM26400 | MISRA_20_9 misses violation when the snprintf function is used in the source code. |
| Link | Date Released | Status |
|---|---|---|
12/12/2011 |
Superseded |
| APAR ID | Description |
| PM46499 | Logiscope crashes with error: full_prepro.exe has encountered problem and needs to close. |
| PM48477 | Building Logiscope rulechecker project requires the qualitychecker license. |
| PM50615 | The Rules tab in Eclipse when opened through Properties does not update the status of the rule. |
| PM52247 | Unexpected behavior of the C++ MISRA rule 2_10_4. |
| PM53642 | Incorrect violations reported by MISRA_0_1_4. |
| Link | Date Released | Status |
|---|---|---|
24/06/2011 |
Superseded |
| APAR ID | Description |
| PM35909 | Incorrect violations reported by MISRA_15_1_1. |
| PM36560 | CSV files are not generated when the .ref files does not have criterias and factors or both. |
| PM37232 | The html report does not contain the function metric values if Logiscope.ref does not contain criterias and / or factors. |
| PM10285 | Logiscope C++ TestChecker cannot handle the exception handling in constructors. |
| PM27997 | Three metrics results of the TestChecker extension are added to qualitychecker report and these metrics are set to zero. |
| PM38461 | Incorrect violations reported by C++ MISRA6_6_4 rule. |
| PM28848 | Display problem in the table of Kiviat graph, where some values (under the HIGH column) are displayed out of the cell area. |
| PM38582 | Incorrect violations reported by C++ MISRA18_0_1 rule. |
| PM14016 | Variation observed in the value of the metric ap_vg when viewed in the quality report and the viewer. |
| PM38462 | Variation in the metric values observed when viewed in the html report and the viewer. |
| PM37124 | Logiscope counts the "lc_ccomm" metric for functions, that are 'renames of functions' and 'instantiations of generic packages. |
| Link | Date Released | Status |
|---|---|---|
30/03/2011 |
Superseded |
| APAR ID | Description |
| PM27999 | Unexpected behavior reported by Rational Logiscope plugin when choosing the rulesets in Eclipse. |
| PM31119 | MISRA_19_3 rule functioning anomaly. |
| PM31547 | MISRA_14_3 rule anomaly. |
| PM31550 | Expected violation by MISRA 16_8_i or MISRA_Rule83i. |
| PM32575 | Incorrect violation reported by MISRA C++: 2008 rule 6_3_1. |
| PM34215 | Batch command with "-addin export -format csv" overrides option -o
|
| PM35315 | Incorrect violations reported by MISRA_15_3_1. |
| PM34505 | ReviewerAda.pdf documentation and the Logiscope.ref file has to be updated. |
| Link | Date Released | Status |
|---|---|---|
02/12/2010 |
Superseded |
| APAR ID | Description |
| PM20829 | Error in the syntax of the
|
| PM23809 | Unexpected behavior of Logiscope due to the variation in the function getName" of the "utilities.tcl" script. |
| PM25343 | Improve the CodePres_26_CommentDefinition rule description and the help documentation. |
| PM10355 | Initialization of struct causes tags in the struct to violate the rule 5.4 in misra-c 2004. |
| PM25531 | MISRA5_5 rule description and the help documentation should me improved. |
| PM26795 | MISRA_8_4 rule reports incorrect violations. |
| PM26403 | MISRA_8_5 doesn't report violation for object definition. |
| PM22810 | MISRA_8_10 rule misses violation. |
| PM25222 | MISRA_10_1 rule depicts unexpected behavior. |
| PM26618 | Sufficient justification should be provided for same violations reported on the same line. |
| PM23772 | Logiscope MISRA12_4 rule misses violation. |
| PM22827 | MISRA_13_4 rule misses violation when used with MISRA_Rule18. |
| PM22811 | MISRA_16_1_i rule misses violation in Logiscope 6.6.3. |
| PM22640 | Logiscope misses violation for MISRA_16_6 rule. |
| PM27025 | Regression between 6.3 and 6.6.3 with Rule MISRA 16_8_iii. |
| PM27143 | MISRA_17_4 rule reports incorrect violation. |
| PM23180 | MISRA_18_2 rules miss violation. |
| PM24683 | MISRA19_14 rules reports unexpected violations. |
| PM26400 | MISRA_20_9 misses violation when the snprintf function is used in the source code. |
| Link | Date Released | Status |
|---|---|---|
15/08/2010 |
Superseded |
| Link | Date Released | Status |
|---|---|---|
20/02/2010 |
Superseded |
| Link | Date Released | Status |
|---|---|---|
30/09/2009 |
Superseded |
| Link | Date Released | Status |
|---|---|---|
29/05/2009 |
Superseded |
Related information
V.R.M.F. Maintenance Stream Delivery Vehicle glossary
Software Product Compatibility Reports
Fix Central
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.