Problem Notes for SAS®9 -

There is a syntax error in the example ODM driver program that is bundled with the SAS &reg Clinical Standards Toolkit 1.6. The program extract_domaindata_all.sas line number 153 is:&nbsp&

In SAS Clinical Standards Toolkit 1.6, the cstcheck_notunique.sas validation check macro can produce incorrect results. This error can be seen when running the cstcheck_notunique.sas SAS &reg Clini

When you edit the properties of an ASP type of broadcast in SAS Digital Marketing Studio, the Parameters and Administrative tabs might show no values. You encounter the problem when you perform the following st

Saving a new ASP Definition in SAS Digital Marketing Studio might result in the following error message being displayed:

Only one address variable parameter can be specified

The SAS ® Revenue Optimization Load_STG2DM_Geo_prod_cost_fact job might generate the following errors in the <DDMONYYYY_HH_MM_SS>Load_STG2DM_Geo_prod_cost_fact..etl_exec_job.<n>.log file:

If you double-click the ASP Definition Properties in SAS Digital Marketing Studio, the values might be set to false . This problem occurs when you edit the valu

When you open an executed broadcast in SAS Customer Intelligence Studio, the broadcast might fail to show the Export definition that is used for the recipient list. This problem occurs only

In SAS ® Forecast Analyst Workbench, the smart object name in the SAS ® Management Console might not be correct for a forecast plan. This issue occurs for forecast plans that are created from

Starting with the third maintenance release of SAS ® 9.4, PROC HTTP might time out, resulting in the following note to appear in a SAS log:

NOTE: The PROCEDURE HTTP used 0.50 CP

A metadata-bound library that is pre-assigned in SAS ® Management Console can be accessed from SAS Studio. If a table in this library is left open in the SAS Studio Table Viewer when you sign off, the syst

In SAS Forecast Analyst Workbench, you might be taken to the Table view instead of the Hierarchy view after filtering in the Model Management view. This issue occurs when you filter a plan that contains more time series t

In SAS Forecast Analyst Workbench, there is no configuration parameter available for the actionType parameter in the etlldfct macro. A hot fix is planned for this issue. After the fix is available, a

Adding the LIBNAME option PRESERVE_TAB_NAMES=YES when using SAS/ACCESS Interface to PostgreSQL might result in the following error when you try to access a table in PostgreSQL:

POSTGRES:

Specify the sendStringParametersAsUnicode=false property for the SAS Shared Services JDBC DataSource.

In SAS ® Forecast Analyst Workbench, the collaboration planning process might run slowly. This issue occurs when you select Initiate Collaboration Planning process box in the Collaboration Fl

In SAS ® Forecast Analyst Workbench, the faw_0201_load_stage_to_sdl job runs slowly. This is the job that loads data from the stage library into SDL tables. There is no workaround for this issue.

If you attempt to partition Hive tables by the DATE column in SAS/ACCESS Interface to Hadoop, the partition might fail and an error might result. For example, these errors might occur when you attempt to partition a DATE

When you invoke SAS 9.4 on a Windows 10 machine, a value in the log window indicates that the operating system is Windows 8 Pro rather than Windows 10. Here are two examples. In this example,

A long quoted string used within the SAS macro facility incorrectly generates one of the following warning messages:

WARNING: The quoted string currently being processed has become m

Fit statistics displayed by SAS Factory Miner models might be scaled too large

Problem Notes for SAS®9 - 57403: SAS Clinical Standards Toolkit 1.6 - Syntax error in the example ODM driver program

Problem Notes for SAS®9 - 57171: SAS Clinical Standards Toolkit 1.6 - cstcheck_notunique.sas validation check macro can produce incorrect results

Problem Notes for SAS®9 - 57541: Editing the properties of an ASP type of broadcast in SAS Digital Marketing Studio shows no values on the Parameters and Administrative tabs

Problem Notes for SAS®9 - 57540: Saving a new ASP Definition in SAS Digital Marketing Studio results in the error \"Only one address variable parameter can be specified\"

Problem Notes for SAS®9 - 57564: The Load_STG2DM_Geo_prod_cost_fact job generates \"ERROR: Invalid DO loop control information...\"

Problem Notes for SAS®9 - 57545: Double-clicking ASP Definition Properties entries in SAS Digital Marketing Studio causes the values to be false

Problem Notes for SAS®9 - 57538: When you open a broadcast in SAS Customer Intelligence Studio, the broadcast fails to show the Export definition that is used for the recipient list

Problem Notes for SAS®9 - 57575: The smart object name for a forecast plan created from a copy is not updated when the forecast plan is given a new name

Problem Notes for SAS®9 - 57551: The HHTP procedure might not complete a transfer, causing a time out to occur

Problem Notes for SAS®9 - 57593: Leaving a metadata-bound table open when you exit a client like SAS Studio might cause the client to hang when restarting

Problem Notes for SAS®9 - 57594: You might be taken to the Table view instead of the Hierarchy view after filtering in the Model Management view SAS Forecast Analyst Workbench

Problem Notes for SAS®9 - 57591: There is no configuration parameter for the actionType parameter in the etlldfct macro in SAS Forecast Analyst Workbench

Problem Notes for SAS®9 - 57569: Using PRESERVE_TAB_NAMES=YES with SAS/ACCESS Interface to PostgreSQL might result in a CLI describe error

Problem Notes for SAS®9 - 57583: A deadlock or poor performance occurs in SAS Workflow Services when you use Microsoft SQL Server for your SAS Shared Services database

Problem Notes for SAS®9 - 57589: The collaboration planning process might run slowly

Problem Notes for SAS®9 - 57588: The faw_0201_load_stage_to_sdl job runs slowly

Problem Notes for SAS®9 - 57051: Partitioning a Hive table by the DATE column in SAS/ACCESS Interface to Hadoop fails and returns \"Error attempting to CREATE a DBMS table\"

Problem Notes for SAS®9 - 57528: An incorrect operating system value appears in the SAS log window in SAS 9.4 installed in a Windows 10 operating environment

Problem Notes for SAS®9 - 57574: A long quoted string within the SAS Macro facility incorrectly generates a warning when it should be a note

Problem Notes for SAS®9 - 57585: Fit statistics might be displayed with an incorrect scale that is caused by an incorrect decimal location