Problem Note 41578: Inconsistent results might occur when you use the Failure Relationship analysis feature of SASĀ® Warranty Analysis
In a Failure Relationship analysis, the SEQUENCE procedure identifies rules that characterize a temporal relationship among failure codes. After the rules have been identified, the MBSCORE procedure is used to find out which products the specific rules apply to. This explicit identification of products that satisfy a given rule is required for running subsequent child analyses and calculating the rule cost.
After the PROC SEQUENCE has run, the variable count is shown in the results data set; this count provides the number of products that participated in the given rule. PROC MBSCORE uses this results data set to identify the products that participated in a given rule. The problem is that the count provided by PROC SEQUENCE and the total number of unique products IDs (count of specific products), as provided by PROC MBSCORE, do not match.
This inconsistency affects the accuracy of child analyses as well as the correctness of the rule cost calculations.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Warranty Analysis | Microsoft Windows Server 2003 Datacenter Edition | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 for x64 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2008 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2008 for x64 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled AIX | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
64-bit Enabled Solaris | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
HP-UX IPF | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Linux for x64 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2011-03-04 11:05:15 |
Date Created: | 2010-11-12 10:41:20 |