Introduction

In SAS Infrastructure for Risk Management 3.4, each federated area contains a libnames.txt configuration file. This file is used to define mappings to libraries that are used in job flows. SAS Infrastructure for Risk Management resolves library names using the mappings that are defined in the libnames.txt file.

Enhancements have been introduced in SAS Infrastructure for Risk Management that enable more dynamic mapping configurations in the libnames.txt file. Below is the description of those enhancements.

Defining the Inputs and Outputs for SAS Infrastructure for Risk Management Tasks

The inputs and outputs for SAS Infrastructure for Risk Management tasks and subflows can be defined by using a three-part name.

For example, irm_cfg.byn_configuration.sas7bdat is the input data set that is used in the following example:

where:

• irm_cfg is the library name in which the input is located. (This location must be mapped in the libnames.txt file.)
• byn_configuration is the file name of the input data set.
• sas7bdat is the file extension of the input data set.

When a job flow instance is created, SAS Infrastructure for Risk Management resolves the library name irm_cfg by using the mappings that are defined in the libnames.txt file.

Here is an example of mapping in a libnames.txt file:

where the configuration variable:

• %la references the Landing Area in the resolved federated area.
• %bd references the Base Date that is selected by the user when they create a job flow instance.
• %cs references the Configuration Set that is selected by the user when they create a job flow instance.

Defining a Mapping That Uses the Entity Configuration Variable

You can now define mappings that use an "Entity" configuration variable (%et). When used in a mapping, SAS Infrastructure for Risk Management replaces the %et configuration variable with the entity that the user selected when creating the job flow instance.

Example

Assume that you want to create a job flow instance that is based on the following parameters:

• Job flow location = /config/Lev1/AppData/SASIRM/fa.id
• Selected entity = ENTITY_BE
• Input data set = static.run_options.sas7bdat
• Libnames.txt defined mapping = STATIC=%la/base/%et

When you create the job flow instance, SAS Infrastructure for Risk Management resolves the path to the run_options.sas7bdat input data set to the following:

config/Lev1/AppData/SASIRM/fa.id/landing_area/base/entity_be/run_options.sas7bdat

Extending Your Mapping Definitions by Using a Custom Substitution Configuration Variable

A new macro variable is a substitution configuration variable that enables you to extend mapping definitions for SAS data sets that contain name/value pairs that use  your own configuration variables. These configurable data sets must be declared in the macrovarload.txt file that is in the config folder of a federated area.

Here is an example:

%mv(libname.data_set_name.config_name)

where:

• libname is the name of the library in which the input is located. (You must map this location in the libnames.txt file.)
• data_set_name is the name of the file that contains the config_name and config_value set, without the file extension.
• config_name is the value of the macro variable.

Note: To ensure data integrity once a job flow instance has been created, the following restrictions apply to the configurable data sets taht are declared in the macrovarload.txt file:

• The data set cannot be modified from the Edit instance window in the SAS Infrastructure for Risk Management web application.
• The data set cannot be modified by using the Download and Upload feature in the SAS Infrastructure for Risk Management web application.
• All paths must resolve to lowercase characters on disk.

Example

Assume that you want to create a job flow instance that is based on the following parameters:

• Job flow location = /config/Lev1/AppData/SASIRM/fa.id
• Input data set for a task = ACT.QUOTE_FX.SAS7BDAT
• Selected configuration set = 03312017
• Libnames.txt defined mapping:

ACT=%la/%bd/%mv(STATIC.ANALYTICS_OPTION.ACT_SCHEME) STATIC=%la/base/%cs/static

When you create the job flow instance, SAS Infrastructure for Risk Management resolves the path to the STATIC.ANALYTICS_OPTIONS input data set to the following:

/Config/Lev1/AppData/SASIRM/fa.id/landing_area/base/03312017/static/analytics_options.sas7bdat

The data set contains the following entries:

Once SAS Infrastructure for Risk Management resolves the path to the STATIC.ANALYTICS_OPTIONS data set, it resolves the path to the ACT.QUOTE_FX.SAS7BDAT input data set to the following:

/config/Lev1/AppData/SASIRM/fa.id/landing_area/03312017/ifrs/quote_fx.sas7bdat

Warning: When you use an existing configuration table for one of the dynamic library configurations that is described in this document, the table can no longer be edited for that job flow instance. Therefore, you might want to consider creating a custom table that contains the pointer to the dynamic library. You can create this table anywhere in the landing area.

Operating System and Release Information

A fix for this issue for SAS Infrastructure for Risk Management 3.4 is available at: