D1Y005 for Linux for x64 |
SAS High-Performance Risk 4.1 |
Issue(s) Addressed: | Introduced: |
62862 | Middle-tier and server component changes for SAS® High-Performance Risk 4.1 (Revision 18w25) |
D1Y001 |
64858 | Adds functionality to allow alongside (parallel) writes of simulation values data set in SAS® High-Performance Risk 3.9 |
D1Y001 |
62476 | The RSKRPT_PRINT_LIBRARIES.SAS macro file is not copied during a migration from the SAS® Model Implementation Platform 2.4 release to the 3.1 release |
D1Y001 |
62484 | The content_packages directory structure is missing after you migrate the SAS® Model Implementation Platform 2.3 release to the 3.1 release |
D1Y001 |
63648 | "ERROR: Parsing error generating code" occurs or the SAS® system stops responding when you use the STATESDATA= option in Delta-Normal analyses |
D1Y002 |
64668 | SAS® High-Performance Risk might issue a warning message when the session encoding differs from the encoding of the cube |
D1Y002 |
63469 | The selected font size is not used in the display rules in the SAS® High-Performance Risk user interface |
D1Y002 |
64634 | Scenario runs fail in SAS® High-Performance Risk 3.9 |
D1Y002 |
64635 | SAS® High-Performance Risk 4.1 now supports the migration of risk explorations from the 3.9 release |
D1Y002 |
64823 | ALERT - When opening a risk exploration you might encounter the error "There was a problem displaying the crosstab. No items are available." |
D1Y002 |
65044 | Changes and enhancements for SAS® High-Performance Risk 4.2 and SAS® Risk Scenario Manager 4.2 (Revision 19w25) |
D1Y002 |
65118 | SAS® High-Performance Risk returns incorrect results for joined stress cubes |
D1Y003 |
65844 | STRESS task fails with "Fatal error in PMPI_Bcast: Other MPI error, error stack: PMPI_Bcast(1478)" |
D1Y004 |
64915 | Cubes created using SAS® Event Stream Processing are recognized by SAS® High-Performance Risk as UTF-8 encoded in sessions with a different encoding |
D1Y005 |
NOTE: If you install this hot fix and have SAS Risk Dimensions Server Component 6.11 installed, you must also install hot fix D2A002. |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |