Installation Instructions for Hot Fix G62001

Linux for x64


Hot fix G62001 addresses the issue(s) in SAS Financial Crimes Monitor Server 2.3 on Linux for x64 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/G62.html#G62001


The hot fix downloaded, G62001la.zip, contains the updated files required to address the documented issues.
Do NOT extract the contents of G62001la.zip. The hot fix installation process will extract the contents as needed.


IMPORTANT NOTES

  1. You must have SAS Financial Crimes Monitor Server 2.3 installed on your system before applying this hot fix. Refer to SN-35968 for instructions on how to determine which product releases you have installed.

  2. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

  3. You must have Administrator Privileges on your CLIENT or SERVER machine.

  4. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  5. This hot fix should be installed using the same userid who performed the initial software installation.


INSTALLATION

The G62001 hot fix for SAS Financial Crimes Monitor Server 2.3 will be installed using the SAS Deployment Manager (SDM). By default, the SDM will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading G62001la.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User’s Guide; see the Applying Hot Fixes for Windows and UNIX section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.

The content of this hot fix is listed in the hot fix manifest.


POST-INSTALLATION INSTRUCTIONS

After installing the ICF, you will need to make modifications to the autoexec.sas and FCMMain.sas files located in the SAS configuration directory. Please back up both of those files before proceeding with the post-install steps. You will also need to run a database script if you are using IBM DB2 Database.

The configuration directory is located in one of the following directories, depending on the operating environment.

UNIX Specifics
     <SASConfig>/Lev1/Applications/SASFinancialCrimesMonitor2.3
Windows Specifics
     <SASConfig>\Lev1\Applications\SASFinancialCrimesMonitor2.3

Steps for Modifying autoexec.sas

  1. Backup autoexec.sas in your SAS configuration directory.
    UNIX Specifics
         <SASConfig>/Lev1/Applications/SASFinancialCrimesMonitor2.3/
    Windows Specifics
         <SASConfig>\Lev1\Applications\SASFinancialCrimesMonitor2.3\
    
  2. While being careful not to delete the "options metaport" statement, replace all lines starting at the first "%global" statement until the "libname STAGE" statement, with the following code:
    %global FCM_DEBUG FCM_INTRADAYONLY FCM_LICENSE_CHECK FCM_ERRORHANDLINGDISABLED FCM_RUNDATE FCM_RUNPRJ FCM_SCENARIO FCM_ARRAYDIM FCM_SLIB_NM;
    
    %let FCM_SLIB_NM = FCM_SLIB;
    
    %let FCM_INTRADAYONLY = %sysget(INTRADAY);
    
    %let DateTime = %sysfunc(inputn(%sysget(RUNDATE), DateTime19.));
    data _null_;
          if (&DateTime = '') then
                CALL SYMPUT('DateTime', input(put( date()  ,date7.) || ':00:00:00', datetime.));
    run;
    %let FCM_RUNDATE = %sysfunc( putn(&DateTime, DATETIME19.));
    
    %let FCM_RUNPRJ = %sysget(PROJECT);
    %sysfunc(ifc(
                    (&FCM_RUNPRJ ^= ),                              /* logical expression */
                    ,                                               /* if populated leave as is */
                    data _null_;
                          CALL SYMPUT('FCM_RUNPRJ', 'ALL');         /* if blank set to ALL */
                    run;,
                    data _null_;                                    /* if missing set to ALL */
                          CALL SYMPUT('FCM_RUNPRJ', 'ALL');
                    run;
                )
               );
    
  3. Delete the following lines:
            %sysfunc(ifc(%sysfunc(exist(stage._successfully_run))
                      ,
                     ,
             data stage._successfully_run;
                 set FCM.FCM_PROJECT (obs=0 keep=PROJECT_SK);
            run;
            ,
            )    );
    
  4. Modify the "%include viewlib" statement to remove the reference to final_scenario_template.sas as shown below:
    %include viewlib(recipient_view.sas
                     _scenario_view.sas
                     proj_actionable_entity_view.sas
                     proj_by_variable_view.sas
                     proj_calc_field_view.sas
                     proj_parameter_view.sas
                                    );
    
  5. Modify the "%include ucmaclib" statement to look like the following (note the addition of final_scenario_template.sas and job_calendar_check.sas):
    %include ucmaclib(scoring.sas
                      alert_summary_template.sas
                      final_scenario_template.sas
                      job_calendar_check.sas);
    
  6. Find the "%configure_libraries" statement and add this line before it:
            %resume_handler
    

Steps for Modifying FCMMain.sas

Backup FCMMain.sas in the <SASConfig> directory if you.ve not already done so. Copy the new FCMMain.sas from <SASHome> to the <SASConfig> directory. An example of SASHome and SAS configuration directory locations is:
UNIX
   <SASHome>/SASFoundation/9.3/misc/fincrmmva/config/FCMMain.sas
      to
   <SASConfig>/Lev1/Applications/SASFinancialCrimesMonitor2.3\FCMMain.sas

Windows
   <SASHome>\SASFoundation\9.3\fincrmmva\misc\config\FCMMain.sas
      to
   <SASConfig>\Lev1\Applications\SASFinancialCrimesMonitor2.3\FCMMain.sas

Steps for Running the Database Script

Run the script "fcm_ddl_db2.sql" if the database used for SAS Financial Crimes Monitor is IBM DB2. If using a different database, no further action is required. The script, "fcm_ddl_db2.sql" is located in one of the following directories, depending on the operating environment.
UNIX Specifics
   !SASROOT\fincrmmva\sasmisc\dbmc\ddl\

Windows Specifics
   !SASROOT/misc/fincrmmva/dbmc/ddl/



This completes the installation of hot fix G62001 on Linux for x64.