<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
 <channel> <title>SAS Notes for SAS&#174;9 - </title>
 <link>http://support.sas.com/</link>
 <description>SAS Notes for SAS&#174;9 -  published to the web in the last 14 days.</description>
 <copyright>Copyright 2007 SAS Institute Inc. All Rights Reserved.</copyright>
 <dc:rights>Copyright 2007 SAS Institute Inc. All Rights Reserved.</dc:rights>
 <image>
   <title>SAS Institute Inc.</title>
   <url>http://support.sas.com/images/logo.gif</url>
   <link>http://support.sas.com/</link>
 </image>
<item>
<title>SAS Notes for SAS&#174;9 - 19864: Instructions for setting SAS  Financial Management logging level to DEBUG </title>
<link> http://support.sas.com/kb/19864.html </link>
 <description>If you encounter problems with SAS Financial Management, and you are asked to increase the logging level to DEBUG for &quot;finance&quot;, complete the following steps:  

1) Edit the &amp;ltlogging.xml&amp;gt file, which should be located
</description>
<category>FMOFR+SAS+Financial+Management </category>
<pubDate>Mon, 28 Apr 2008 13:42:59 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19005: Changing a DOUBLE INTEGER data type to a SHORT INTEGER data type when you create a Microsoft Access table </title>
<link> http://support.sas.com/kb/19005.html </link>
 <description>
When you create a Microsoft Access table, you can define a column that has a default data type of DOUBLE INTEGER as the type SHORT INTEGER by using the DBTYPE= option, as shown in this example:  
 
  cellpaddin
</description>
<category>PCFILE+SAS/ACCESS+Interface+to+PC+Files </category>
<pubDate>Tue, 29 Apr 2008 09:24:40 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19066: Forcing uncommitted reads using SAS/ACCESS  Interface to DB2 in the Windows environment </title>
<link> http://support.sas.com/kb/19066.html </link>
 <description>To force an uncommitted read using SAS/ACCESS Interface to DB2, you need to include the Read_Isolation_Level=UR option in the LIBNAME statement.

</description>
<category>DB2+SAS/ACCESS+Interface+to+DB2 </category>
<pubDate>Tue, 29 Apr 2008 13:28:18 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 14123: Requirements for SAS/ACCESS  Interface to MYSQL on Windows. </title>
<link> http://support.sas.com/kb/14123.html </link>
 <description>
SAS/ACCESS Interface to MySQL is available with SAS 9.1.2 and later
which allows you to access a MYSQL database from SAS. You must have
SAS/ACCESS Interface to MySQL licensed and installed.
To verify if you have thi
</description>
<category>MYSQL+SAS/ACCESS+Interface+to+MySQL </category>
<pubDate>Tue, 29 Apr 2008 16:19:46 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 11391: DATA Step HASH object does not support duplicate key values </title>
<link> http://support.sas.com/kb/11391.html </link>
 <description>
Prior to SAS 9.2, the DATA Step HASH object does not support duplicate key
values.  When the ADD method is used to add a duplicate key value to
the hash table, a non-zero return code is generated. If the DATASET
argument
</description>
<category>BASE+Base+SAS </category>
<pubDate>Tue, 29 Apr 2008 17:42:17 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31373: Documentation does not specify applicability rules for using the IF_EXISTS property </title>
<link> http://support.sas.com/kb/31373.html </link>
 <description>The IF_EXISTS property is only applicable to WebDAV subscribers or WebDAV persistent stores. This is not explicitly stated in the documentation.
</description>
<category>INTTECH+SAS+Integration+Technologies </category>
<pubDate>Wed, 30 Apr 2008 11:19:51 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31912: Internet Explorer 7 can now be used to interface with SAS  Performance Management Solutions </title>
<link> http://support.sas.com/kb/31912.html </link>
 <description>Internet Explorer 7 clients can now be used to interface with SAS Financial Management 4.4, SAS Human Capital Management 4.4 and SAS Strategic Performance Management 2.4.&lt;br&gt;     
&lt;br&gt;
For these Solutions to function with I
</description>
<category>FMOFR+SAS+Financial+Management </category>
<pubDate>Wed, 30 Apr 2008 14:13:51 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31830: Changes to SAS  Web Report Studio role memberships might not immediately be enforced </title>
<link> http://support.sas.com/kb/31830.html </link>
 <description>SAS Web Report Studio role memberships are analyzed every 30 minutes by default, so changes might not immediately be enforced.
</description>
<category>CITATIONWEB+SAS+Web+Report+Studio </category>
<pubDate>Wed, 30 Apr 2008 15:27:10 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 20058: Where to locate logs for SAS Financial Management on Windows/WebLogic </title>
<link> http://support.sas.com/kb/20058.html </link>
 <description>When debugging issues in SAS&amp;reg; Financial Management 4.x, there are a number of logs that you might be asked to check.  Below are the default locations for the most commonly-requested logs on Windows/WebLogic.  

  &lt;b
</description>
<category>FMOFR+SAS+Financial+Management </category>
<pubDate>Wed, 30 Apr 2008 16:05:11 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 30933: \&quot;Error 404--Not Found From RFC 2068 Hypertext Transfer Protocol\&quot; when accessing a SAS  Information Delivery Portal report </title>
<link> http://support.sas.com/kb/30933.html </link>
 <description>When you are logged on to the SAS Information Delivery Portal and try to access a report from a Collection portlet using SAS Web Report Viewer, you may encounter the error:

 
   Error 404--Not Found From RFC 2068 Hype
</description>
<category>SPMOFR+SAS+Strategic+Performance+Managem </category>
<pubDate>Wed, 30 Apr 2008 16:50:58 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31956: Using the MSOffice2k destination with Microsoft Excel 2007 generates a dialog box </title>
<link> http://support.sas.com/kb/31956.html </link>
 <description>When you use the MSOffice2K destination to generate output that will be opened in   
 Microsoft Excel 2007, a dialog box is generated when using the .XLS extension so that this 
 HTML file is opened directly into Excel.
</description>
<category>BASE+Base+SAS </category>
<pubDate>Thu,  1 May 2008 13:29:48 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 16515: Database client requirements when you run SAS/ACCESS  Interface to Sybase in the Windows environment </title>
<link> http://support.sas.com/kb/16515.html </link>
 <description>
Running SAS/ACCESS Interface to Sybase 9.1.3 in the Windows environment involves the following database client requirements:
 
 
 On a Win32 platform, SAS &amp;reg;  9.1.3 is a 32-bit installation and, t
</description>
<category>SYBASE+SAS/ACCESS+Interface+to+Sybase </category>
<pubDate>Thu,  1 May 2008 15:15:25 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 21034: Questions to ask SAS Risk Dimensions users during primary contact </title>
<link> http://support.sas.com/kb/21034.html </link>
 <description>
1. What version of Risk Dimensions?

2. What operating system?

3. What is the latest hot fix that you have applied?

4. Problem with GUI, or problem running in batch? Next sets of questions
are divided between the two:
</description>
<category>RISK+SAS+Risk+Dimensions+Enterprise+Edit </category>
<pubDate>Fri,  2 May 2008 11:31:06 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 30692: SAS Profitability Management 1.2 Enhancements </title>
<link> http://support.sas.com/kb/30692.html </link>
 <description>SAS    Profitability Management 1.2 is being enhanced with the 
release of hot fix 12PRF03. The goals for the&amp;nbsp;hot fix include performance 
improvements and enhancements to improve SAS Profitability Manageme
</description>
<category>ABMPROFOFR+SAS+Profitability+Management </category>
<pubDate>Fri,  2 May 2008 12:31:48 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19070: Deleting data from a Microsoft Excel spreadsheet using SAS/ACCESS  software </title>
<link> http://support.sas.com/kb/19070.html </link>
 <description>
Data cannot be deleted from a Microsoft Excel spreadsheet using SAS/ACCESS &amp;reg;  Interface to OLE DB, SAS/ACCESS &amp;reg;  Interface to PC Files, and SAS/ACCESS &amp;reg;  Interface to ODBC. Although
</description>
<category>PCFILE+SAS/ACCESS+Interface+to+PC+Files </category>
<pubDate>Fri,  2 May 2008 15:45:47 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19072: Accessing an Oracle Virtual Private Database </title>
<link> http://support.sas.com/kb/19072.html </link>
 <description>
Some sites are using the Oracle Virtual Private Database (VPD)
as a way to provide Row Security.
 
 
The VPD will automatically alter a query, based on the user ID
and password specified at connection, and retu
</description>
<category>ORACLE+SAS/ACCESS+Interface+to+Oracle </category>
<pubDate>Mon,  5 May 2008 10:27:03 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19205: Specifying Oracle Comments/Hints Using SAS/ACCESS  Interface to
Oracle </title>
<link> http://support.sas.com/kb/19205.html </link>
 <description>
Oracle Hints/Comments can be specified, using SAS/ACCESS
Interface to Oracle -  Proc SQL PassThrough facility.
 
The Oracle Hint/Comment is specified &apos;as is&apos; using the comment syntax show here:
  cellpadding=
</description>
<category>ORACLE+SAS/ACCESS+Interface+to+Oracle </category>
<pubDate>Mon,  5 May 2008 10:32:36 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19292: An error occurs when you use SAS/ACCESS  Interface to ODBC to access
SPSS </title>
<link> http://support.sas.com/kb/19292.html </link>
 <description>
The following code works when you access SPSS with SAS/ACCESS Interface to ODBC 8.2. However, when you use this same code in SAS/ACCESS Interface to ODBC 9.1.3, you might receive the error message shown in this example:
</description>
<category>ODBC+SAS/ACCESS+Interface+to+ODBC </category>
<pubDate>Mon,  5 May 2008 10:50:54 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19293: An error occurs when you submit the IMPORT procedure with the DBMS=EXCEL2000 option </title>
<link> http://support.sas.com/kb/19293.html </link>
 <description>
An error occurs when you submit the following IMPORT procedure with the DBMS=EXCEL2000 option: 
 
  cellpadding=&quot;5&quot; cellspacing=&quot;2&quot; border=&quot;0&quot;&gt;
 &lt;td bgcolor=&quot;#EEEEEE&quot;&gt;
 &lt;span style=&quot;font
</description>
<category>PCFILE+SAS/ACCESS+Interface+to+PC+Files </category>
<pubDate>Mon,  5 May 2008 11:06:17 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19713: Garbage characters display in table names when you use SAS/ACCESS  Interface to Microsoft SQL Server in the UNIX environment </title>
<link> http://support.sas.com/kb/19713.html </link>
 <description>
Table names are displayed using garbage characters when you use SAS/ACCESS Interface to Microsoft  SQL Server under Unix versus when you use SAS/ACCESS &amp;reg;  Interface to ODBC in the Windows environment.
 
</description>
<category>ODBC+SAS/ACCESS+Interface+to+ODBC </category>
<pubDate>Mon,  5 May 2008 15:03:28 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 20082: Sybase tables cannot be viewed in the explorer window when you use SAS/ACCESS  Interface to Sybase in a Sybase 12.0 server </title>
<link> http://support.sas.com/kb/20082.html </link>
 <description>
When you use SAS/ACCESS Interface to Sybase in a Sybase 12.0 server, you cannot view Sybase tables from the explorer window or by running a DATASETS procedure on the library. If you use PROC DATASETS, you might receive t
</description>
<category>SYBASE+SAS/ACCESS+Interface+to+Sybase </category>
<pubDate>Mon,  5 May 2008 15:31:23 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 16976: Blank page generated when ODS RTF file is opened in MS Word </title>
<link> http://support.sas.com/kb/16976.html </link>
 <description>
When using ODS to create RTF files, SAS creates one or more tables in
RTF, then hands those tables off to MS Word to paginate.  In some cases,
a table is just close enough to the bottom margin that MS Word thinks
ther
</description>
<category>BASE+Base+SAS </category>
<pubDate>Mon,  5 May 2008 15:36:19 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31506: SAS/GRAPH 256 color support for SAS 9.2 </title>
<link> http://support.sas.com/kb/31506.html </link>
 <description>
The following device drivers now support more than 256 colors in SAS 9.2: 

 
ACTIVEX, ACTXIMG, BMP, BMP20, EMF, JAVA, JAVAIMG, PNG 
PNGT, PNG300, SASPRTC, SASPRTG, SASPRTM, SVG, SVGT, 
SVGVIEW, SVGZ, UEPS, UEPSC,
</description>
<category>GRAPH+SAS/GRAPH </category>
<pubDate>Mon,  5 May 2008 16:22:30 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31760: English data sets generate Cross Environment Data Access (CEDA) note with SAS for Double-Byte Character set (DBCS) </title>
<link> http://support.sas.com/kb/31760.html </link>
 <description>Five indexed SAS data files with Western encoding appear 
in &quot;!SASROOT/nls/en/sascfg&quot; on Unix, and correspondingly, in &quot;C:\Program Files\SAS\SAS 9.1\nls\1d\sascfg&quot; on Windows, and they generate CEDA notes if you are querying the
</description>
<category>BASE+Base+SAS </category>
<pubDate>Mon,  5 May 2008 16:29:05 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 16927: A stored process with a pre-assigned library might fail and generate an error </title>
<link> http://support.sas.com/kb/16927.html </link>
 <description>
A stored process with a pre-assigned DBMS library might fail if the METAAUTOINIT parameter is not assigned. The failure generates the following error message:
 
 
&lt;blockquote&gt;&lt;span style=&quot;font-family:monospace;&quot;&gt;
</description>
<category>MGMTCONSOLE+SAS+Management+Console </category>
<pubDate>Mon,  5 May 2008 16:59:51 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 16986: Using a LIBNAME statement and a DATA step to create an index on a MySQL table at the time the table is created </title>
<link> http://support.sas.com/kb/16986.html </link>
 <description>
You can use a LIBNAME statement and a DATA step to create an index on a MySQL table at the time the table is create. 
 
 
To do this, you need to use the Dthe DBTYPE= option in the DATA step. You use this DBTYPE=
</description>
<category>MYSQL+SAS/ACCESS+Interface+to+MySQL </category>
<pubDate>Mon,  5 May 2008 17:10:41 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 17749: An error occurs when you attempt to access an SQL Server column with an XML data type using the OLEDB engine </title>
<link> http://support.sas.com/kb/17749.html </link>
 <description>
The following error occurs when you attempt to access an SQL Server column with an XML data type using the OLEDB engine:
  
&lt;blockquote&gt;&lt;span style=&quot;font-family:monospace;&quot;&gt;
NOTE: The following 1 column(s) in xxx
</description>
<category>OLEDB+SAS/ACCESS+Interface+to+OLE+DB </category>
<pubDate>Tue,  6 May 2008 09:34:59 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 20733: Control files and data files might still exist  after you bulk load an Oracle table </title>
<link> http://support.sas.com/kb/20733.html </link>
 <description>
Control (.CTL) files and data (.DAT) files are created when you bulk
load an Oracle table.  By default, the .DAT file is deleted
after the bulk loading is completed. The files are deleted because they
are usually larg
</description>
<category>ORACLE+SAS/ACCESS+Interface+to+Oracle </category>
<pubDate>Tue,  6 May 2008 11:59:44 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 13878: Forcing the installation procedure to request an SID file or to use a new one when installing from admin install </title>
<link> http://support.sas.com/kb/13878.html </link>
 <description>
The SAS installation does not automatically request the location of the SAS Installation Data file in 
installations after the admin/personal image has been created. This is because the SID file is stored 
in the adm
</description>
<category>BASE+Base+SAS </category>
<pubDate>Wed,  7 May 2008 10:45:56 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31989: SAS  Information Map Studio will not start </title>
<link> http://support.sas.com/kb/31989.html </link>
 <description>Usually, when SAS Information Map Studio does not start, lowering the memory allocation will address the problem.
</description>
<category>MAPCENTER+SAS+Information+Map+Studio </category>
<pubDate>Wed,  7 May 2008 11:30:59 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 32040: New options available for the SCAN FUNCTION in SAS 9.2 </title>
<link> http://support.sas.com/kb/32040.html </link>
 <description>
There are two new options that can be used with the SCAN FUNCTION beginning in SAS 9.2.
 
 
They are charlist and modifier.  The details are below.
 
 
 charlist  
 
 
Charlist specifies an o
</description>
<category>BASE+Base+SAS </category>
<pubDate>Thu,  8 May 2008 13:07:54 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 19460: Display of totals for rows and columns depends on data  in SAS  Web Report Studio </title>
<link> http://support.sas.com/kb/19460.html </link>
 <description>
Even though you can select both the row-total and the column-total options in SAS Web Report Studio, the display or application of the totals depends on the data. Totals are calculated and displayed only &lt;i&gt;within&lt;/I&gt; a
</description>
<category>CITATIONWEB+SAS+Web+Report+Studio </category>
<pubDate>Fri,  9 May 2008 10:36:50 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31723: NullPointerException when adding more than 10 business structure entries at the same level </title>
<link> http://support.sas.com/kb/31723.html </link>
 <description>If you add business structure in SAS&amp;reg; OpRisk Monitor 3.4.x and you add more than 10 items at the same level, you might encounter the following exception:  

 
&lt;blockquote&gt;&lt;span style=&quot;font-family:monospace;&quot;&gt;
   (
</description>
<category>ORMONITOROFR+SAS+OpRisk+Monitor </category>
<pubDate>Fri,  9 May 2008 10:39:31 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 30416: SAS  jobs abend with SEC6 reason code 0F01C008 </title>
<link> http://support.sas.com/kb/30416.html </link>
 <description>SAS jobs terminate with SEC6 abend for reason code 0F01C008 meaning calling process can not be dubbed. This along with the message: ICH409I 30A-014 ABEND DURING IRRSIU00 PROCESSING.
Indicative of a FREEMAIN failure within RACF. Symptom dump output w
</description>
<category>BASE+Base+SAS </category>
<pubDate>Fri,  9 May 2008 11:18:06 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 20198: SAS  Data Integration Studio 3.4 returns a StackOverflowError exception error when you deploy a large number of jobs </title>
<link> http://support.sas.com/kb/20198.html </link>
 <description>
When you try to deploy a large number of jobs in SAS Data Integration
Studio, sometimes only a subset of the jobs is deployed. The only
indication that this has occurred is the message stating how many jobs
actually d
</description>
<category>DATABUILDER+SAS+Data+Integration+Studio </category>
<pubDate>Fri,  9 May 2008 13:32:56 EST </pubDate>
</item>
</channel>
</rss>
