Installation Instructions for Hot Fix I73002

64-bit Enabled AIX

Hot fix I73002 addresses the issue(s) in Risk Management for Banking 3.11 as documented in the Issue(s) Addressed section of the hot fix download page:

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

R04001  updates  SAS Asset and Liability Management for Banking Server 3.11
R62001  updates  SAS Firmwide Risk for Banking Server 3.11
I72002  updates  SAS Risk Management for Banking Mid-Tier 3.11
I71002  updates  SAS Risk Management for Banking Server 3.11

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

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,, 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 on each machine or save it in a network location that is accessible to all machines.

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


  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.


Hot Fix I73002 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of Risk Management for Banking 3.11 require updating on the machine. See SAS Note 44810 for more details.

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, 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

for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

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.


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

R04001  updates  SAS Asset and Liability Management for Banking Server 3.11
R62001  updates  SAS Firmwide Risk for Banking Server 3.11
I72002  updates  SAS Risk Management for Banking Mid-Tier 3.11
I71002  updates  SAS Risk Management for Banking Server 3.11

R04001  updates  SAS Asset and Liability Management for Banking Server 3.11


R62001  updates  SAS Firmwide Risk for Banking Server 3.11


I72002  updates  SAS Risk Management for Banking Mid-Tier 3.11

Re-build and Re-deploy Web Application

This hot fix requires that the WebApp be rebuilt and redeployed. Use the following steps to perform this post-installation task:

Step 1: Re-build Web Application

In order for this step to execute correctly, the Metadata Server must be running.

1.1 Invoke the SAS Deployment Manager 9.3

From the SASDeploymentManager directory launch
SAS Deployment Manager is installed in the following default location:


1.2 Select a language in the Choose Language box

1.3 Select Rebuild Web Applications

1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

1.5 Specify Connection Information, including the sasadm User ID and Password

1.6 Select Risk Management for Banking 3.1 as the Web Application to Rebuild

1.7 Verify the information on the Summary screen and select Start

1.8 Select Finish when the deployment is complete

This process will update the Risk Management for Banking ear in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear file will be placed in the directory below:


Step 2: Re-deploy Web Applications

Re-deploy the web applications based on the instructions for the web application server you are using.

I71002  updates  SAS Risk Management for Banking Server 3.11

NOTE: If you have already applied hot fix I73001, skip to the section " update the metadata for the stored processes" below.

Follow the steps below to regenerate the Solution Data Mart (SDM):

  1. Locate the file in your install: in a typical install, the macro resides under SASHOME/misc/rmbcomnsvr/solution_data_mart
  2. Open the file in a BASE SAS session on the installation server (where the SAS code resides)
  3. Scroll to the bottom of the macro file and comment out the following line:
  4. Compile the macro in the SAS session by clicking the Submit button on the menu
  5. After successful compilation, execute the following macro below:
    %create_solution_data_mart(soln_data_mart_dir=<complete path to indata directory in your install>);
    Example of indata path: <CONFIGDIR>/AppData/SASRiskManagementForBanking/3.1/indata
  6. Check the SAS log for successful execution of the preceeding macro.

    In addition, complete the following for any existing playpens that use private entity data marts, or for any shared entity data marts.

  7. Login to Risk Management for Banking 3.11
  8. Select File > Select Entity, choose an entity from the list, and click OK.
  9. Re-create any private playpens or the shared data mart for that entity.
    If you are re-creating a playpen that uses a private entity data mart, select File > Manage Playpens from the menu, and for each playpen you are re-creating, follow instructions for creating a playpen that uses a private entity data mart. Any private playpens created prior to the re-creation of the solution data mart cannot receive updates that have been applied to the solution data mart.

    If you are re-creating a shared entity data mart, select File > Manage Shared Data Mart from the menu, and click Change to update the existing shared data mart. (Playpens that use the shared data mart do not require re-creation.)
  10. Repeat steps 8 and 9 for each Entity

    The following steps update sample data in SAS Risk Reporting Repository - RRR:

  11. Back up the location where current RRR data reside
  12. Follow the instruction of sample reporting data creation in the Create SAS Risk Reporting Repository Sample Data section on page 63 of the SAS Risk Management for Banking 3.1 Administrator’s Guide. Note user can now specify location and mode (OVERWRITE or APPEND) directly in the call of the "rmb_batch_create_rrr_sample_data" instead of the steps 3 and 4 in the original instruction.
Follow the steps below to update the metadata for stored processes:
  1. Locate reports.spk under
  2. You can import the stored process metadata using the Import Wizard in SAS Data Integration Studio or SAS Management Console. In this example, SAS Management Console is used.
    1. Login to SMC as sasadm user
    2. Navigate to Folders -> System -> Applications -> SAS Risk Management for Banking -> Firmwide Risk Server 3.1
    3. Right click on "Firmwide Risk Server 3.1" and select "Import SAS Package"
    4. Provide the path and SAS package filename. For e.g. <SASHOME>/SASFoundation/9.3/misc/rmbfirmmva/Config/Deployment/Packages/reports.spk
    5. Click Next. Ensure that the objects are being imported under the correct metadata tree (Folder structure)
    6. Provide the SAS Application Server that you want to associate the metadata with. The application server name should be the same as the one associated with Risk Management for Banking
    7. Provide the stored process code location to be associated with metadata to be imported. For SAS Risk Management for Banking, this should be the corresponding component STP location under <SASConfig>
    8. Click Next and Finish to complete the import process

Follow the steps below to update the ETLs (for populating data from Banking DDS to RMB Solution data mart)

  1. Locate the modified spk files under <SASHOME>/SASRiskManagementForBankingMidTier/3.1/ETL directory
  2. For importing the updated ETLs, follow the instructions outlined in Section "Import the ETL Flows" under Chapter 5 "Data Management" in SAS Risk Management for Banking 3.1: Administrator's Guide

This completes the installation of hot fix I73002 on 64-bit Enabled AIX.