58403 - Mid-tier and Risk Common Scenario Repository changes to support SAS® Model Implementation Platform 2.2 in Revision 16w26

Problem Note 58403: Mid-tier and Risk Common Scenario Repository changes to support SAS® Model Implementation Platform 2.2 in Revision 16w26

This SAS Note provides a summary of the changes and enhancements made for SAS^® High-Performance Risk 3.6 (Revision 16w17) via hot fix to support the SAS Model Implementation Platform 2.2 in Revision 16w26.

User Interface Changes

After you save a modified scenario, when you then attempt to create another scenario, a message occurs indicating that the first scenario has been modified. A prompt asks whether you would like to save the first modified scenario.
Column delimiters for scenarios have changed.
Users of SAS Model Implementation Platform, which uses SAS High-Performance Risk, are not allowed to delete their own scenarios that were created in SAS^® Risk Scenario Manager.
The storage of market states can require considerable disk space, and an option in the HPRISK procedure syntax is needed to prevent the storage of the market states. Other functionality, such as the Distribution Plot, needs to be adjusted so that if the market states are not stored, they still function properly.
Users of SAS Model Implementation Platform (which uses SAS High-Performance Risk) need a scenario version for their scenarios that were created using SAS Risk Scenario Manager.
When you open a scenario in View mode from the Risk Explorer window, and you then attempt to use the Save As functionality, the mode of the editor does not change correctly. The Save icon is not active, the result of which is that the user cannot save the scenario.
Scenario editor plots do not account for the scenario version.

Mid-tier Changes

In SAS Model Implementation Platform (which uses SAS High-Performance Risk), if you attempt to delete scenarios created by other users, a Java Runtime Exception occurs.
If a scenario name includes a special character, such as the underscore ( _ ), the scenario will not be encoded correctly.

Scenario Repository Mid-tier Changes

If one or more dependent scenarios use the same baseline scenario, then the scenarios should have the same set of horizons. Otherwise, a Repository Exception occurs.
Versioned scenarios are not found; the version is missing.
Users of SAS^® Risk Solutions that use SAS High-Performance Risk might encounter the error message reading No enum constant com.sas.risk.scenariorepo.beans.PerturbType.rel because the lookup method is case-sensitive.

Risk Common Mid-tier Changes

The REST application programming interface for importing scenarios might fail to properly access the logical workspace server as needed to fetch and process an internal scenario analysis data set.

Click the Hot Fix tab in this note to access the hot fixes for these issues.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
Product Family	Product	System	Reported	Fixed*	Reported	Fixed*
SAS System	SAS High-Performance Risk	Microsoft® Windows® for x64	3.6	3.7	9.4 TS1M3	9.4 TS1M3
		64-bit Enabled AIX	3.6	3.7	9.4 TS1M3	9.4 TS1M3
		64-bit Enabled Solaris	3.6	3.7	9.4 TS1M3	9.4 TS1M3
		Linux for x64	3.6	3.7	9.4 TS1M3	9.4 TS1M3
		Solaris for x64	3.6	3.7	9.4 TS1M3	9.4 TS1M3

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Type:	Problem Note
Priority:	alert
Topic:	Analytics ==> Financial Analysis

Date Modified:	2016-06-20 10:06:54
Date Created:	2016-06-15 08:19:04