Typically, in a relational database management system (RDBMS), nulls represent the absence of data. That is, RDBMS nulls do not sort or compare because there is no data on which to operate. However, in SAS, there is the c
↧
Problem Notes for SAS®9 - 56256: Querying a relational DBMS table using the IN clause operator might return unexpected results
↧
Problem Notes for SAS®9 - 56274: Data source changes might not be immediately available in SAS Visual Analytics Viewer
If you are logged on to SAS Visual Analytics when a SAS ® LASR™ Analytic Server table is updated, the updated data items might not be available in SAS ® Visual Analytics Viewer. This i
↧
↧
Problem Notes for SAS®9 - 56273: SAS Enterprise Guide might display an invalid GIT Repository error when opening a project
When you attempt to open a project that uses program history, SAS Enterprise Guide might instead open a blank project or display an exception such as the following:
-------------------![]()
↧
Problem Notes for SAS®9 - 55520: Running the Terms section in SAS Contextual Analysis gives \"TERMS ERROR: The submitted line exceeds maximum line length 32768 bytes\"
SAS Contextual Analysis with a long "ignore" list returns TERMS ERROR: The submitted line exceeds maximum line length - 32768 bytes.
↧
Problem Notes for SAS®9 - 56141: PROC EXPORT produces a comma for the first variable name on only the first row even if the first variable name is specified in the DROP= option
The EXPORT procedure writes out a comma for the first variable name on the first row of the external file even though the first variable name is listed in the DROP= data set option. The erroneous comma is written out onl
↧
↧
Problem Notes for SAS®9 - 56282: No data is returned when using the SASEFRED LIBNAME engine to access Federal Reserve Economic Data (FRED)
No XML data is returned when you use the SASEFRED LIBNAME engine to access Federal Reserve Economic Data (FRED). This occurs because the FRED web site has changed access from HTTP to HTTPS.
A hot fix is planne
↧
Problem Notes for SAS®9 - 55540: An error might occur in when you execute the hostsetup command for Platform Suite for SAS in the AIX operating environment
When you execute the IBM Platform LSF 9.1 hostsetup command in SAS under AIX 7.1, the following error might occur while the script is running:
↧
Problem Notes for SAS®9 - 56266: PROC EXPORT returns an error when a user-defined format name exceeds 30 characters
The EXPORT procedure returns error messages like the following when you use a user-defined format name that exceeds 30 characters in length:
ERROR 22-322: Expecting a format name.
ERRO![]()
↧
Problem Notes for SAS®9 - 56151: The value of &SYSNOBS is incorrect after running PROC EXPORT
The &SYSNOBS macro variable returns the number of observations read from the last data set that was closed by the previous procedure or DATA step. If a %PUT of &SYSNOBS is issued after running the EXPORT procedure, a val
↧
↧
Problem Notes for SAS®9 - 56104: Delta-Normal analysis fails with \"ERROR: Write Access Violation RISK\"
In SAS ® Risk Dimensions ® , when you run a Delta-Normal analysis, an error message like the following might occur:
ERROR: An exception has been encountered.
Ple![]()
↧
Problem Notes for SAS®9 - 56112: Spawned risk analysis project fails with \"ERROR: A lock is not available for ENV_NAME.RD_DS_INSTRUMENT.DATA.\"
In SAS ® Risk Dimensions ® , when you attempt to spawn a risk analysis project, messages like the following might be generated:
ERROR: A lock is not available for![]()
↧
Problem Notes for SAS®9 - 56252: Clicking a tracked link with a variable fails when you manually add the URL to the HTML source code of a SAS Digital Marketing broadcast
In a SAS Digital Marketing broadcast, a tracked link might not resolve properly when an email recipient clicks the link. This problem occurs when you manually add a URL for a tracked link to the HTML source code and that
↧
Problem Notes for SAS®9 - 56294: The scripts that are used for migrating the SAS Customer Intelligence Common Data Model take a long time to execute
The scripts that are used for migrating the SAS Customer Intelligence Common Data Model to release 6.1_M1, take a long time to execute. Migration to release 6.1_M1 is required when you migrate from release 5.41 or earlie
↧
↧
Problem Notes for SAS®9 - 56198: Incorrect p-values produced by the ORPVALUE and CLODDS= options with effects parameterization in PROC LOGISTIC
PROC LOGISTIC reports incorrect p-values in the Odds Ratio Estimates table produced by the ORPVALUE and CLODDS= options in a model using the default parameterization.
↧
Problem Notes for SAS®9 - 56148: Downstream processing errors occur when input data tables are empty
In SAS ® Credit Risk Management for Banking, if various input data tables are empty, downstream processing errors and notes occur.
Here are some examples of the errors:
↧
Problem Notes for SAS®9 - 56256: Querying a relational DBMS table using the IN clause operator might return unexpected results
Typically, in a relational database management system (RDBMS), nulls represent the absence of data. That is, RDBMS nulls do not sort or compare because there is no data on which to operate. However, in SAS, there is the c
↧
Problem Notes for SAS®9 - 56311: The SAS Digital Marketing Server log file shows repeated instances of PlatformServicesUtility error messages
The following PlatformServicesUtility error message might appear repeatedly in the SAS Digital Marketing Server log file (SASDigitalMarketingServer6.4.log):
ERROR [] [] [] Platfor![]()
↧
↧
Problem Notes for SAS®9 - 56326: IBM Security AppScan might return a high-priority report \"Reflected XSS method GET\" in SAS Workflow Administrator 1.4 and 1.4_M1
Escape characters and active JavaScript might potentially be passed and processed on the server without sufficient control and filtering when you access the SAS Workflow Administrator web application.
↧
Problem Notes for SAS®9 - 56309: PROC HPCDM processes very slowly or fails to complete or produces incorrect perturbed parameter estimates
PROC HPCDM might seem to hang when a perturbation analysis is requested using either a COUNTSTORE= input data set or a SEVERITYEST= input data set that contains covariance parameters. If the procedure completes under these conditions, the perturbed p
↧
Problem Notes for SAS®9 - 56066: You cannot save a filter in SAS Marketing Optimization when you have special characters in filter values
SAS Marketing Optimization does not allow the use of special characters in a filter. If you use special characters when you try to create a filter, the following error occurs:
Character![]()
↧