Providing software solutions since 1976
38930 - Applying a DBCS hot fix in the UNIX environment results in incorrect search path to the executables- Installation Note
Installing a DBCS hot fix on UNIX does not correctly update the !SASROOT/nls/<language>/sasv9.cfg files, resulting in an incorrect search path to the executables.
39379 - Documentation and frequently asked questions for the SASŪ Software Depot- Installation Note
This SAS note addresses frequently asked questions about the SAS Software Depot in SAS 9.2 and SAS 9.3. Lists of documentation resources are also provided.
If you execute a stored process from the SAS Information Delivery Portal using a URL Display Portlet and specify a URL that uses the SASStoredProcess servlet, you will be prompted again for user authentication unless ...
5055 - Administrator of the machine versus being part of the administrator group- Usage Note
When you perform an installation of the SAS System, SAS recommends that you have administrator privileges when you perform the installation. You can be logged in as part of the administrator group or logged in as the ...
The new metadata-bound library functionality that is introduced in SASŪ 9.3 TS1M2 now causes the SAS process to check all Base SASŪ libraries to see whether they are bound to SAS metadata. This additional check requires ...
Prior to Platform Suite for SASŪ 2.1, the Platform Computing Job Scheduler only provides a single-day grace period and the GRACE= option is ignored.
42197 - A list of papers useful for troubleshooting system performance problems- Usage Note
General Papers: Guidelines for Preparing your Computer Systems for SAS Guidelines about important aspects of hardware architecture, configuration, and setup. How to Maintain Happy SASŪ9 Users This is a good basic ...
When you are installing the SAS Foundation 9.1.3 and SAS Enterprise Guide 4.1 DVD, the installation for SAS Enterprise Guide might not start automatically. This can occur when you click "Step 3: Install SAS Enterprise ...
After a new installation of SAS Activity-Based Management, launching the Administrator produces an error (might have various manifestations). The Event Viewer, however, shows the following error: DCOM got error
A hot fix is available for this problem.
39049 - Identity value substitutions might return an error in the Build Formula window- Problem Note
In some cases, using identity values in a permission condition results in an error. Here is an example expression that uses the identity value SAS.PersonName. {[Organization].[All Organization], [Organization].[All ...
24546 - How do I obtain a license file for Platform Computing software?- Usage Note
Your SAS installation data file (SID file) must be updated when the license period for Platform Computing software has expired, or when there has been a change in the SAS software product bundle that is covered by the ...
When running SASŪ Stored Processes on the SASŪ Stored Process Server using the Stored Process Web Application and you encounter problems, these troubleshooting tips should help.
SAS Web Report Studio schedules must be managed from within SAS Web Report Studio. If you attempt to create or modify schedules using the Schedule Manager plug-in to SAS Management Console, you will experience ...
8365 - Entry point names have changed between SASŪ8 and SASŪ9- Usage Note
The modules that can be used as entry point names on a z/OS system changed between SAS 8 and SAS 9: In SASŪ8In SASŪ9 SASHOSTSAS SASXA1SASB (Non-LPA bundle configuration) SASXA1SASLPA (LPA bundle configuration) ...
43982 - Potential security vulnerability on Linux systems in SASŪ 9.3- Problem Note
A hot fix is available for a potential security vulnerability on Linux systems (both Linux for Intel and Linux for x64).
45578 - Testing throughput rates in a UNIX environment- Usage Note
In order to troubleshoot a performance problem, you might need to determine the I/O throughput rates on any file systems that a SASŪ application is accessing. For your convenience, the iotest.sh script (which you ...
41656 - SASŪ Scalable Performance Data Server WHERE constraints not honored in Viewtable window- Problem Note
The example code found in the Full Code tab in this note demonstrates how WHERE constraints are not honored in the Viewtable window. This behavior is incorrect. Note that the example code assumes that you have users ...
A SASŪ Scalable Performance Data ServerŪ data cluster can potentially contain thousands of member tables. When you attempt to use PROC CONTENTS to display the contents of a large cluster, the following error might occur ...
45446 - DBIDIRECTEXEC option causes SASŪ Scalable Performance Data ServerŪ table partitions to be written in the metadata path- Problem Note
There is a hot fix for this problem.
If the length of a concatenated string exceeds 200 characters, the string is truncated and the following error occurs: SPDS_WARNING: Concatenated strings can be at most 32767 characters. Select the Hot Fix tab in ...
45497 - PROC SPDO CLUSTER CREATE or CLUSTER ADD might fail due to incompatible IDXSEGSIZE- Problem Note
A hot fix is available for this problem.
A hot fix is available for this problem.
45457 - Index names are truncated to 8 characters with SASŪ Scalable Performance Data ServerŪ- Problem Note
If you use PROC SQL to connect to SASŪ Scalable Performance Data ServerŪ, and you use a SELECT statement to select an index whose name is longer than 8 characters, the name of the index is truncated to 8 characters.
45456 - "SPDS_ERROR: Parse Failure" when using LENGTH column attribute in SQL pass-through- Problem Note
If you attempt to use the LENGTH column attribute in SQL pass-through, an error message that is similar to the following might occur: SPDS_ERROR: Parse Failure: create table x1 as select x length#=5 from x; SPDS_ ...
