You define SAS^® Infrastructure for Risk Management library mapping in the libnames.txt file. If you use the entity (%et) macro variable in both a static mapping and a dynamic custom mapping, an issue with entity IDs can occur. For example, when you create a job flow instance based on an entity (Entity A) and a second job flow instance based on another entity (Entity B), the second job flow incorrectly resolves paths to the first entity (Entity A) and not to the second (Entity B).

In this example, the libnames.txt file contains the following information:

The first job flow instance, where the entity (%et) is WW_INSURANCE, correctly references WW_INSURANCE.

The second job flow instance, where the entity (%et) is WW_INSURANCE_QTR, incorrectly references WW_INSURANCE.

When this problem occurs, an error similar to the following can appear:

A different symptom for this problem is seen when a new record is added in the ANALYTICS_OPTION table. The output table INSTANCE_PARAM_TABLES that is generated from the macro irm_rest_get_instance_parms still keeps the value of the entity from previous runs.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

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