Problem Note 33522: Scenarios might generate erroneous alerts due to duplicates in the alert list
 |  |  |  |  |
The scenario code might add duplicate entries to a list that is supposed to only contain unique entries. The count of the number of entries in the list might be exaggerated, and the count is used by the scenario and might affect the triggering of an alert. Sometimes the count is used only for display purposes in alert message.
Select the Hot Fix tab in this note to access the hot fix for this issue.
The problem involves two SAS functions, INDEXW and CATX, One solution is to force a delimiter at the end of the list by always concatenating a delimiter on the end of the list when using the CATX function. This causes a double delimiter when new entries are added. But the list would always end with a delimiter.The other solution, and the one which was implemented, is to use the STRIP function inside the INDEXW function, also specifying the delimiter.
The following scenarios are affected by this problem:
SAS10001 SAS10011 SAS10012 SAS10015 SAS10016 SAS10017 SAS10026 SAS10027 SAS10028 SAS10029
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Microsoft Windows 2000 Advanced Server | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Datacenter Server | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Server | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows 2000 Professional | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows NT Workstation | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows Server 2003 Standard Edition | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Microsoft Windows XP Professional | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Windows Vista | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled AIX | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled HP-UX | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| 64-bit Enabled Solaris | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
| Linux | 2.1.1 | 2.2.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 | ||
A fix for this issue for SAS Anti-Money Laundering 2.1 is available at:
http://www.sas.com/techsup/download/hotfix/aml21.html#033522A fix for this issue for SAS Anti-Money Laundering 2.1.1 is available at:
http://www.sas.com/techsup/download/hotfix/aml211.html#033522
The scenario code might add duplicate entries to a list that is supposed to only contain unique entries.
The count of the number of entries in the list might be exaggerated, and the count
is used by the scenario and might affect the triggering of an alert.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2008-10-06 11:58:58 |
| Date Created: | 2008-10-03 15:32:16 |