A6D005 for Linux for x64 |
SAS Infrastructure for Risk Management 3.3 |
Issue(s) Addressed: | Introduced: |
59991 | When a job flow is modified and re-run, the original input is used instead of the modified version |
A6D001 |
60000 | Folder contents are unexpectedly removed when you delete a job flow instance in SAS® Infrastructure for Risk Management |
A6D001 |
60002 | ALERT - After they are reloaded, flow instances become corrupted |
A6D001 |
60004 | ALERT - In SAS® Infrastructure for Risk Management, tasks that use REST API calls and that attempt to access the metadata server might fail |
A6D001 |
60484 | ALERT - Live ETL methods fail and return "java.lang.NullPointerException: CORBA does not allow a null string to be used as a parameter..." |
A6D002 |
60490 | ALERT - Users can download unfiltered Federated Area (FA) data and unfiltered Persistent Area (PA) data from an unshared flow instance |
A6D002 |
60984 | ALERT - After changing a parameter value in SAS® Infrastructure for Risk Management, you will notice very slow performance in uploading the table |
A6D003 |
61181 | SAS® Infrastructure for Risk Management 3.4 job flows used in earlier releases of SAS® Infrastructure for Risk Management are not displayed correctly |
A6D004 |
61503 | ALERT - New instance results that you see are the existing published results, which can be outdated or from the previously published run |
A6D005 |
61715 | ALERT - Incorrect input staging data is used when you create one or more flows (instances) and there are two or more base dates |
A6D005 |
61787 | When you try to load task data into a subflow that has a root flow that is overridden in a higher federated area, it fails with "No URL Provided" |
A6D005 |
62012 | Attempts to modify flow input data fail with "ERROR...I/O processing did not complete" when you use a libref to access a WebDAV server |
A6D005 |
63162 | Partitioning is now available for SAS® Regulatory Risk Management flows in SAS® Infrastructure for Risk Management |
A6D005 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |