SUPPORT / SAMPLES & SAS NOTES
 

Support

Usage Note 49953: Hot Fix 10 for SAS® Fraud Management 3.2_M2 has been released

DetailsHotfixAboutRate It

This hot fix addresses SAS Fraud Management 3.2_M2 issues. You must have this release of the product installed in order to apply the hot fix.

Hot fixes are cumulative, so issues that are resolved in previous versions of this hot fix are also included in this version.

Click the Hot Fix tab in this note to access the Hot Fix 10 contents. The following issues are addressed in this Hot Fix 10 release:

  • AGS not waiting for Transaction Writers to be idle before starting
  • AGS "resolveHighlightCriteria" step logging SQL error during cleanup
  • Transactions "stuck" in AGS until AGS is shut down
  • Create a job to purge signatures and user variables from the MEH not updated in the last N days
  • Option to *not* write the VXX and FRH_MERCHANT_DIM tables
  • Allow client to supply input values for RUR variables
  • JOSE Unable to Send Reply in an MQ Cluster Environment
  • AGS SAF code not working as expected in very particular events
  • Fraud tagging causes leading spaces need to be preserved when reading ftl_cust fields
  • MEH job 1500 - need to change "BAT_RPT_DB_ENGINE" to "BAT_DB_ENGINE"
  • JOSE Engine fails with syntax error though rule passed syntax check because of TAB in rule code
  • HQO_CARD_NUM not being set in the FRH_RULE_FIRED_FACT table
  • Add more variable names to xms_define_segment and segDef7= parameter
  • Error received during the start-up of the JOSE (SAS) when the sum of all segments exceeds 64K


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Fraud Management64-bit Enabled AIX3.29.2 TS2M2
Linux for x643.29.2 TS2M2
* 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.