Problem Note 59760: When SAS® High-Performance Risk is used in solo mode with ESPMODE=ON, PROC HPRISK might stop responding
When you are using SAS High-Performance Risk in solo mode with ESPMODE=ON, the HPRISK procedure might not function properly. The issue occurs because the threaded kernel library used by SAS® Event Stream Processing is different from the threaded kernel library that is used by SAS High-Performance Risk. When the problem occurs, messages like the following are generated.
DEBUG: Sending schema information to the HPRisk Engine.
DEBUG: ESP - receiving normal positions and sending to the HPRisk Engine.
DEBUG: ESP - successfully received project info.
DEBUG: ESP - subscriberStart successful.
DEBUG: ESP - pubsubConnect successful.
NOTE: There were 300 positions sent to the HPRisk Engine.
NOTE: There were 600 positions sent to the HPRisk Engine.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS High-Performance Risk | Solaris for x64 | 3.6 | 3.8 | 9.4 TS1M3 | 9.4 TS1M4 |
Linux for x64 | 3.6 | 3.8 | 9.4 TS1M3 | 9.4 TS1M4 |
64-bit Enabled Solaris | 3.6 | 3.8 | 9.4 TS1M3 | 9.4 TS1M4 |
64-bit Enabled AIX | 3.6 | 3.8 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft® Windows® for x64 | 3.6 | 3.8 | 9.4 TS1M3 | 9.4 TS1M4 |
*
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.
The HPRISK procedure might hang if you are using in solo mode and ESPMODE=ON. The issue occurs because the threaded kernel library used by SAS® Event Stream Processing is different from the threaded kernel library that is used by SAS High-Performance Risk.
Type: | Problem Note |
Priority: | high |
Topic: | Analytics ==> Financial Analysis
|
Date Modified: | 2017-02-06 16:16:53 |
Date Created: | 2017-01-20 15:05:39 |