Hot fix G49018 addresses issues in SAS Fraud Management 3.2_M2 on AIX.
This hot fix download consists of the following components:
G49018 - SAS Fraud Management 3.2_M2
meh_hotfix_3.2.2.9 - MEH updates (1)
rpthist_db2_hotfix_3.2.2.3 - RH updates for DB2 (1)
rpthist_db2_hotfix_3.2.2.6 - RH updates for DB2 (2)
rpthist_db2_hotfix_3.2.2.7 - RH updates for DB2 (3)
rpthist_db2_hotfix_3.2.2.9 - RH updates for DB2 (4)
rpthist_db2_hotfix_3.2.2.16 - RH updates for DB2 (5)
rpthist_teradata_hotfix_3.2.2.3 - RH updates for teradata (1)
rpthist_teradata_hotfix_3.2.2.6 - RH updates for teradata (2)
rpthist_teradata_hotfix_3.2.2.7 - RH updates for teradata (3)
rpthist_teradata_hotfix_3.2.2.9 - RH updates for teradata (4)
sor_hotfix_3.2.2.3 - SOR updates (1)
sor_hotfix_3.2.2.5 - SOR updates (2)
sor_hotfix_3.2.2.6 - SOR updates (3)
sor_hotfix_3.2.2.7 - SOR updates (4)
sor_hotfix_3.2.2.9 - SOR updates (5)
sor_hotfix_3.2.2.10 - SOR updates (6)
sor_hotfix_3.2.2.12 - SOR updates (7)
sor_hotfix_3.2.2.16 - SOR updates (8)
sor_hotfix_3.2.2.17 - SOR updates (9)
sor_hotfix_3.2.2.21 - SOR updates (10)
The G49018 component is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated. See the Container Hot Fixes section in the
Maintenance Install Tool (MIT) Usage Guide
for more information about container hot fixes.
G51009 for SAS Fraud Management Alert Generation Server 3.2_M2
H04004 for SAS Fraud Management Common Macros 3.2_M2
G50013 for SAS Fraud Management Mid-Tier 3.2_M2
G70005 for SAS Fraud Management Multi Entity History DB Maintenance Macros 3.2_M2
H05009 for SAS Fraud Management Reporting History DB Maintenance Macros 3.2_M2 ***
H06006 for SAS Fraud Management Reporting History ETL Server Macros 3.2_M2
G52008 for SAS Fraud Management Scoring Engine 3.2_M2
G73006 for SAS Fraud Management System of Record DB Maintenance Macros 3.2_M2
G63013 for SAS Fraud Management Transaction Extensions 3.2_M2
I30001 for SAS Fraud Management Operational Reports 3.2_M2
*** member hot fixes that have been updated since the previously released hot fix (G49017)
Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The software components and release numbers should match the list of software components updated by the individual hot fix installers.
G49018r6.bin
meh_hotfix_3.2.2.9.tar
rpthist_db2_hotfix_3.2.2.3.tar
rpthist_db2_hotfix_3.2.2.6.tar
rpthist_db2_hotfix_3.2.2.7.tar
rpthist_db2_hotfix_3.2.2.9.tar
rpthist_db2_hotfix_3.2.2.16.tar
rpthist_teradata_hotfix_3.2.2.3.tar
rpthist_teradata_hotfix_3.2.2.6.tar
rpthist_teradata_hotfix_3.2.2.7.tar
rpthist_teradata_hotfix_3.2.2.9.tar
sor_hotfix_3.2.2.3.tar
sor_hotfix_3.2.2.5.tar
sor_hotfix_3.2.2.6.tar
sor_hotfix_3.2.2.7.tar
sor_hotfix_3.2.2.9.tar
sor_hotfix_3.2.2.10.tar
sor_hotfix_3.2.2.12.tar
sor_hotfix_3.2.2.16.tar
sor_hotfix_3.2.2.17.tar
sor_hotfix_3.2.2.21.tar
$> chmod 755 G49018r6.bin
export DISPLAY=<your_node_name>:0
<path_to_downloaded_file>/G49018r6.binFor example:
./G49018r6.binThis will initiate the installation wizard, which will guide you through the hot fix installation process. During the installation you will be prompted for the SASHOME location to be updated. You should provide the path to the top level SAS directory where the deploymntreg directory exists.
See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.
The contents of G49018r6.bin are listed in the hot fix manifest.
MEH updates (1):Installation Instructions for MEH updates
RH_db2 updates (1):Installation Instructions for RH_DB2 updates
RH_db2 updates (2):Installation Instructions for RH_DB2 updates
RH_db2 updates (3):Installation Instructions for RH_DB2 updates
RH_db2 updates (4):Installation Instructions for RH_DB2 updates
RH_db2 updates (5):Installation Instructions for RH_DB2 updates
RH_teradata updates (1):Installation Instructions for RH_teradata updates
RH_teradata updates (2):Installation Instructions for RH_teradata updates
RH_teradata updates (3):Installation Instructions for RH_teradata updates
RH_teradata updates (4):Installation Instructions for RH_teradata updates
SOR updates (1):Installation Instructions for SOR updates
SOR updates (2):Installation Instructions for SOR updates
SOR updates (3):Installation Instructions for SOR updates
SOR updates (4):Installation Instructions for SOR updates
SOR updates (5):Installation Instructions for SOR updates
SOR updates (6):Installation Instructions for SOR updates
SOR updates (7):Installation Instructions for SOR updates
SOR updates (8):Installation Instructions for SOR updates
SOR updates (9):Installation Instructions for SOR updates
SOR updates (10):Installation Instructions for SOR updates
This completes the installation of G49018. You must perform any "Post-Installation Instructions" documented below
to successfully complete the deployment of this hot fix.
A new property, test_area_path_webapp, has been created as part of this hot fix. This property is closely related to the property test_area_path. Both properties can be found on the SAS Fraud Management web application under the Preferences tab. From the Preferences tab, select System Properties -> Rule Testing.
The value for both of these properties needs to be set to a logical location that is shared between the server running WebSphere and the server hosting the SAS IOM Server. If the properties are not set correctly, rule testing may fail.
It is suggested that the TestArea directory should be in the same location as the Estimates directory as defined in the properties estimate_results_dir_sasiom and estimate_results_dir_webapp found in the Preferences Tab under System Properties->Estimation.
You must be logged in to host machine as the configuration user for your implementation.
You must be logged in to the J-OSE host machine as the configuration user.
You must be logged in to the J-OSE host machine as the configuration user.
After installing hotfix G49018, the script fix_queue_current_recs.sh can be used to correct any records in the FRH_QUEUE_DIM table that have more than one instance of CHANGE_CURRENT_IND='1' for a queue_id.
After installing hotfix G49018, the script change_failed_rff_name.sh can be used to rename new_rff_<timestamp>.sas7bdat files in the etl/data folder which job 4000 has renamed to failed_rff_<timestamp>.sas7bdat when it aborted trying to load the data. If the cause of the failure has been addressed and one wants to run job 4000 again using the failed_rff... file, it must be renamed using this script.
Clients can achieve some transaction processing performance improvements by setting the following 2 new property values to 'true':
ags_disable_insert_vxx
ags_disable_merchant_dim_update
This can be done from the console tab under the Configure Properties -> Alert Engine entry in the left hand navigation tree.
The ags_disable_insert_vxx property will disable the storage of user variable values when a transaction is stored in the SOR and RH. This means that if rules are firing in an unexpected manner, the user variable report cannot be used as a diagnostic tool to examine the values of these variables on past transactions because this data will not have been saved in the SOR or RH.
The ags_disable_merchant_dim_update will disable the storage and update of data in the RH about each merchant involved in a transaction. Setting this option to true should have no effect on the basic operation of the system as the merchant dim table (FRH_MERCHANT_DIM) is an auxiliary table created to support client reports should they choose to write them.
Create the following directories:
Copy $SAS_ROOT/misc/fsmrh/data/cpp_ccca_jobparms.xml to $SASWHSE_IMPLEMENT_HOME/cpp/etc
Copy $SAS_ROOT/misc/fsmrh/source/cpp_autoexec.sas to $SASWHSE_IMPLEMENT_HOME/cpp/src/sas
Copy $SAS_ROOT/misc/fsmrh/source/cpp_obfuscate.sas to $SASWHSE_IMPLEMENT_HOME/cpp/src/obf
In order for this step to execute correctly, the Metadata Server must be running.
$ export DISPLAY=<displayname>:0
From the SASDeploymentManager directory execute config.sh, for example
$ cd <SASHOME>/SASDeploymentManager/9.2
$ ./config.sh
Re-deploy the web applications based on the instructions in SAS Web Application Administration Guide, Chapter 8, for the web application server you are using.
The dml.sql in sor_hotfix_3.2.2.3.tar (sasfmcp\database\db2\sor\patches\patch_3.2.2.3\dml.sql) must be executed after running the SOR table release updates (SOR job 100). Running the sql is needed for preserving the existing key_field_id values in the FCM_ALERT_TYPE table for the alert types present in the 3.2_M1 release. The SOR tables update job sets the key_field_id values as used in a new installation. For an upgrade, the indicated sql must be executed after job 100 is executed. Failing to run the dml.sql will invalidate the execution of rules running in the upgraded environment.
This completes the installation of hot fix G49018 on AIX.
Copyright 2015 SAS Institute Inc. All Rights Reserved.