Usage Note 48578: In SAS® Anti-Money Laundering, replace calls to get the system date and time with a new macro %aml_start_datetime in the alert generation process
 |  |  |  |  |
The %aml_agp_start_datetime_init macro must be called at the start of the alert generation process (AGP). The macro variable %aml_agp_start_datetime_init stores the alert generation starting date and time in a data set. The value is used to create the dates for the alerts. This action prevents alerts from having different creation dates if the AGP spans two days.
Besides the %aml_agp_start_datetime_init macro, there are two other new macros that are used to process date and time value within the AGP:
%aml_start_datetime_read: Reads the start date and time that was stored by the %aml_agp_start_datetime_init set and assigns its value to the macro variable %aml_start_datetime. The macro variable %aml_start_datetime is used instead of date(), today(), and datetime() calls throughout the alert generation process.
%aml_start_datetime_clear: Deletes the data set that stores the start date and time of the alert generation process. This macro is called at the end of the AGP.
If the %aml_agp_start_datetime_init macro is not executed, then the following message appears in the log:
WARNING: Apparent invocation of macro AML_START_DATETIME_INIT not resolved. WARNING: Apparent invocation of macro AML_START_DATETIME_READ not resolved
As a result, the AGP fails when it tries to obtain the date from the macro variable %aml_start_datetime.
To resolve this error, place a call to %aml_agp_start_datetime_init macro in the beginning of the aml_agp.sas code, as shown in the following example:
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering | Solaris for x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 |
| Linux for x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Linux | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| HP-UX IPF | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| 64-bit Enabled Solaris | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| 64-bit Enabled HP-UX | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| 64-bit Enabled AIX | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows Vista for x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Enterprise x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Enterprise 32 bit | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows XP Professional | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2008 for x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2008 R2 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2008 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 for x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows Vista | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Ultimate x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Ultimate 32 bit | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Professional x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Professional 32 bit | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Home Premium x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Windows 7 Home Premium 32 bit | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Standard Edition | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||
| Microsoft® Windows® for x64 | 4.2 | 5.1_M1 | 9.2 TS2M3 | 9.3 TS1M2 | ||