<?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 2013 SAS Institute Inc. All Rights Reserved.</copyright>
 <dc:rights>Copyright 2013 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 - 49832: The SAS  Customer Intelligence Access Control Template must not be renamed </title>
<link> http://support.sas.com/kb/49832.html </link>
 <description>It is important that the SAS Customer Intelligence Access Control Template (ACT) is not renamed. The installed name of this ACT is &quot;Customer Intelligence Template,&quot; and this should not be changed.
 
 To define the S
</description>
<category>MKTAUTOOFR+SAS+Marketing+Automation </category>
<pubDate>Mon,  6 May 2013 12:17:19 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 31322: Using NOT in conjunction with the IN operator for the Macro facility </title>
<link> http://support.sas.com/kb/31322.html </link>
 <description>The NOT operator is used to negate the returned value of the IN operator.
</description>
<category>BASE+Base+SAS </category>
<pubDate>Tue,  7 May 2013 11:32:09 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 18389: IKernel.exe errors might occur when you install Base SAS  software on the Windows platform </title>
<link> http://support.sas.com/kb/18389.html </link>
 <description>When you install SAS on the Windows platform, you might receive one of the following errors related to the Flexera IKernel executable:
&lt;div class=&quot;fusionnote&quot;&gt;    &quot;Setup failed to launch installation engine: Error loadin
</description>
<category>BASE+Base+SAS </category>
<pubDate>Tue,  7 May 2013 13:31:42 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 49325: Long PUT statements in a DATA step might cause a truncation warning when you are writing to the _WEBOUT fileref </title>
<link> http://support.sas.com/kb/49325.html </link>
 <description>When SAS &amp;reg;  Stored Process code contains a DATA step that has a very long row of data for a PUT statement and the _WEBOUT fileref, the resulting PUT-statement string might be truncated.  In addition, the follo
</description>
<category>BASE+Base+SAS </category>
<pubDate>Fri, 10 May 2013 13:24:23 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 49273: A launch error occurs when you use the SAS  Object Spawner to start the SAS  Stored Process Server </title>
<link> http://support.sas.com/kb/49273.html </link>
 <description>
When the SAS Object Spawner attempts to start the SAS &amp;reg;  Stored Process Server, the following error message appears in the object-spawner log file if the launch time exceeds the SAS Stored Process Server &lt;st
</description>
<category>INTTECH+SAS+Integration+Technologies </category>
<pubDate>Mon, 13 May 2013 14:52:51 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 48833: Execute permission must be granted to a library in order for SAS  to determine whether it is bound to SAS  metadata </title>
<link> http://support.sas.com/kb/48833.html </link>
 <description>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 that Execute permission be gra
</description>
<category>BASE+Base+SAS </category>
<pubDate>Tue, 14 May 2013 10:17:51 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 49833: A SAS  Workspace Server connection failure occurs when the SAS Trusted User account is not specified in the trustedUsers.txt file </title>
<link> http://support.sas.com/kb/49833.html </link>
 <description>
An attempt to connect to a SAS Workspace server fails when the SAS Trusted User account is not specified in the trustedUsers.txt file. The following error is written to the SAS &amp;reg;  Object Spawner log when the
</description>
<category>  </category>
<pubDate>Tue, 14 May 2013 11:37:10 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 49663: Configuring the SAS  Stored Process Server to flush the log file during the execution of a SAS  Stored process </title>
<link> http://support.sas.com/kb/49663.html </link>
 <description>When the SAS  Stored Process Server executes a SAS  Stored process, the log is not flushed from the buffer to the physical log file until after the SAS Stored Process completes execution unless you turn on additional logging.
</description>
<category>INTTECH+SAS+Integration+Technologies </category>
<pubDate>Tue, 14 May 2013 12:00:33 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 20572: An unrestricted user account should not be used in SAS  Enterprise Guide </title>
<link> http://support.sas.com/kb/20572.html </link>
 <description>
An unrestricted SAS metadata user identity should not be used as the user ID credential in SAS Enterprise Guide to log on to a SAS &amp;reg;  Metadata Server. Unrestricted user accounts are intended for use solely a
</description>
<category>EGUIDE+SAS+Enterprise+Guide </category>
<pubDate>Tue, 14 May 2013 12:08:05 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 48525: SAS  Data Integration Studio performs a version check when you open a job </title>
<link> http://support.sas.com/kb/48525.html </link>
 <description>Starting with SAS Data Integration Studio 4.5, a version check occurs when you open a job. The behavior of the version check depends on the setting of the options: 

 
 Display an error on newer job version &lt;/l
</description>
<category>DATABUILDER+SAS+Data+Integration+Studio </category>
<pubDate>Tue, 14 May 2013 12:29:08 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 48780: How to troubleshoot SAS  Real-Time Decision Manager DS2 Activities by configuring trace-level logging in DataFlux  Federation Server </title>
<link> http://support.sas.com/kb/48780.html </link>
 <description>In order to troubleshoot SAS Real-Time Decision Manager DS2 Activities, you can change the logging configuration in the DataFlux Federation Server that executes the activities.  The instructions below describe the steps to
</description>
<category>POLICYOFR+SAS+Real-Time+Decision+Manager </category>
<pubDate>Thu, 16 May 2013 16:39:29 EST </pubDate>
</item>
<item>
<title>SAS Notes for SAS&#174;9 - 49953: Hot Fix 10 for SAS  Fraud Management 3.2_M2 has been released </title>
<link> http://support.sas.com/kb/49953.html </link>
 <description>The following have been addressed in Hot Fix 10.  An issue where the AGS was not waiting for Transaction Writers to be idle before start, AGS SAF code was not working as expected under very particular events, leading spaces for fraud tagging are now
</description>
<category>FRAUDMGTOFR+SAS+Fraud+Management </category>
<pubDate>Thu, 16 May 2013 16:42:20 EST </pubDate>
</item>
</channel>
</rss>
