Installation Instructions for Hot Fix M33002

HP-UX IPF

Hot fix M33002 addresses the issue(s) in SAS Credit Risk Management for Banking 4.8 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/M33.html#M33002

M33002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

M27002  updates  SAS Credit Risk Studio Mid-Tier 4.8
M28002  updates  SAS Credit Risk Management for Banking Server 4.8
M29002  updates  SAS Credit Risk Management for Banking Server Configuration 4.8
M31001  updates  SAS Risk Reporting Repository 2.2

MANDATORY ACTION REQUIRED PRIOR TO APPLYING THIS HOT FIX:

A REQUIRED update to the SAS Deployment Manager (SDM) is available which will allow this hot fix to be configured automatically after it is applied to your system. Please see Installation Note 52417 for information on downloading and applying this SDM update.

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 release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, M33002pt.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save M33002pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of M33002pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. 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.

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

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

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

INSTALLATION

The hot fix will be applied 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 M33002pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.

The hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the ‘member’ hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each ‘member’ hot fix applied (member hot fixes are listed at the top of these instructions).

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

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

M28002  updates  SAS Credit Risk Studio Mid-Tier 4.8
M28002  updates  SAS Credit Risk Management for Banking Server 4.8
M29002  updates  SAS Credit Risk Management for Banking Server Configuration 4.8
M31001  updates  SAS Risk Reporting Repository 2.2

M28002  updates  SAS Credit Risk Studio Mid-Tier 4.8

NONE

M28002  updates  SAS Credit Risk Management for Banking Server 4.8

Update to SAS Macro files:

Move the following files from <SASCONFIG>/Applications/SASCreditRiskMgmtBankSrvr4.8/ucmacros/common to <!SASROOT>/ucmacros/risk :

rdcube_generate_cube_code.sas
rdcube_generate_im_code.sas
rdcube_get_object_in_tree.sas
rdcube_get_tree_uri.sas
rdcube_main.sas
rdcube_verify_object_in_tree.sas

Create/update Data Marts:

Take a backup of your existing data marts and run the following ddls:

1. For CRMB SDM, run load_sample_data.sas located in <SASCONFIG>/Applications/SASCreditRiskMgmtBankSrvr4.8/omr/data. This will create the SDM tables as well as load sample data

2. For RRR,

   1. Go to following folder:

      Windows: \rskrptrpsbk\sasmisc\programs
      Unix: /misc/rskrptrpsbk/programs

   2. Copy file run_createrrr.sas.orig to run_createrrr.sas

   3. Edit the file run_createrrr.sas and provide the path for RRR by replacing the token (@..@) in the following statement:
      
      

      libname rrr "@data.riskrpt.dir@"
      (e.g. ("<SASCONFIG>/AppData/SASRiskReportingRepository/2.2/reportmart")

   4. Run file run_createrrr.sas to create RRR tables

   If you already have existing business data, load it to the new data marts

Import the ETL Flows:

Complete the following tasks to manually import the ETL bridge component and create the metadata for the same.

1. Go to the <SASCONFIG>/AppData/SASCreditRiskMgmtBankSrvr/4.8/ETL/packages directory.

2. Use a SAS import utility (SAS Management Console 9.3 or the SAS Data Integration Studio ) to import the crmb_etl_bridge.spk package file located in the above folder. Note: These package files are dependent on the metadata of the SAS Detail Data Store for Banking 4.7 Hot Fix, which must be installed before you begin the import process. For more information about how to install and schedule the jobs, see the section on "ETL Job Deployment" in Chapter 4 of the SAS Credit Risk Management for Banking Server: Administrator's Guide.

M31001  updates  SAS Risk Reporting Repository 2.2

NONE

This completes the installation of hot fix M33002 on HP-UX IPF.