<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>TechnologyTales.com &#187; SAS</title>
	<atom:link href="http://technologytales.com/tag/sas/feed/" rel="self" type="application/rss+xml" />
	<link>http://technologytales.com</link>
	<description>Adventures in the world of digital and computer technology</description>
	<lastBuildDate>Sat, 24 Jul 2010 10:20:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<atom:link rel='hub' href='http://technologytales.com/?pushpress=hub'/>
		<item>
		<title>ERROR 22-322: Syntax error, expecting one of the following: a name, *.</title>
		<link>http://technologytales.com/2010/06/14/error-22-322-syntax-error-expecting-one-of-the-following-a-name/</link>
		<comments>http://technologytales.com/2010/06/14/error-22-322-syntax-error-expecting-one-of-the-following-a-name/#comments</comments>
		<pubDate>Mon, 14 Jun 2010 10:53:20 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[data step]]></category>
		<category><![CDATA[ERROR]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[syntax]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=1434</guid>
		<description><![CDATA[This is one of the classic SAS errors that you can get from PROC SQL and it can be thrown by a number of things. Missing out a comma in a list of variables on a SELECT statement is one situation that will do it, as will having an extraneous one. As I discovered recently, an [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2010/06/14/error-22-322-syntax-error-expecting-one-of-the-following-a-name/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ERROR: Invalid value for width specified &#8211; width out of range</title>
		<link>http://technologytales.com/2010/06/08/error-invalid-value-for-width-specified-width-out-of-range/</link>
		<comments>http://technologytales.com/2010/06/08/error-invalid-value-for-width-specified-width-out-of-range/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 11:48:22 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[data step]]></category>
		<category><![CDATA[dictionary tables]]></category>
		<category><![CDATA[error message]]></category>
		<category><![CDATA[program]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[tables]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=1425</guid>
		<description><![CDATA[This could be the beginning of a series on error messages from PROC SQL that may appear unclear to a programmer more familiar with Data Step. The cause of my getting the message that heads this posting is that there was a numeric variable with a length less that the default of 8, not the best of [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2010/06/08/error-invalid-value-for-width-specified-width-out-of-range/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reading data into SAS using the EXCEL and PCFILES library engines</title>
		<link>http://technologytales.com/2010/03/04/reading-data-into-sas-using-the-excel-and-pcfiles-library-engines/</link>
		<comments>http://technologytales.com/2010/03/04/reading-data-into-sas-using-the-excel-and-pcfiles-library-engines/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 17:09:20 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Access]]></category>
		<category><![CDATA[date]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Excel]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[spreadsheet]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=1296</guid>
		<description><![CDATA[Recently, I had the opportunity to have a look at the Excel library engine again because I need to read Excel data into SAS. You need SAS Access for PC Files licensed for it to but it does simplify the process of getting data from spreadsheets into SAS. It all revolves around setting up a library pointing [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2010/03/04/reading-data-into-sas-using-the-excel-and-pcfiles-library-engines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A few more SAS functions to know</title>
		<link>http://technologytales.com/2010/01/22/a-few-more-sas-functions-to-know/</link>
		<comments>http://technologytales.com/2010/01/22/a-few-more-sas-functions-to-know/#comments</comments>
		<pubDate>Fri, 22 Jan 2010 07:38:09 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[alphabet]]></category>
		<category><![CDATA[alphabetic character]]></category>
		<category><![CDATA[alphanumeric character]]></category>
		<category><![CDATA[ANYALNUM]]></category>
		<category><![CDATA[ANYALPHA]]></category>
		<category><![CDATA[ANYCNTRL]]></category>
		<category><![CDATA[ANYDIGIT]]></category>
		<category><![CDATA[ANYFIRST]]></category>
		<category><![CDATA[ANYGRAPH]]></category>
		<category><![CDATA[ANYLOWER]]></category>
		<category><![CDATA[ANYNAME]]></category>
		<category><![CDATA[ANYPRINT]]></category>
		<category><![CDATA[ANYPUNCT]]></category>
		<category><![CDATA[ANYSPACE]]></category>
		<category><![CDATA[ANYUPPER]]></category>
		<category><![CDATA[ANYXDIGIT]]></category>
		<category><![CDATA[carriage returns]]></category>
		<category><![CDATA[control character]]></category>
		<category><![CDATA[first position]]></category>
		<category><![CDATA[INDEX]]></category>
		<category><![CDATA[letter]]></category>
		<category><![CDATA[letter of the alphabet]]></category>
		<category><![CDATA[lowercase]]></category>
		<category><![CDATA[lowercase letter]]></category>
		<category><![CDATA[NOTALNUM]]></category>
		<category><![CDATA[NOTALPHA]]></category>
		<category><![CDATA[NOTCNTRL]]></category>
		<category><![CDATA[NOTDIGIT]]></category>
		<category><![CDATA[NOTFIRST]]></category>
		<category><![CDATA[NOTGRAPH]]></category>
		<category><![CDATA[NOTLOWER]]></category>
		<category><![CDATA[NOTNAME]]></category>
		<category><![CDATA[NOTPRINT]]></category>
		<category><![CDATA[NOTPUNCT]]></category>
		<category><![CDATA[NOTSPACE]]></category>
		<category><![CDATA[NOTUPPER]]></category>
		<category><![CDATA[NOTXDIGIT]]></category>
		<category><![CDATA[position]]></category>
		<category><![CDATA[program]]></category>
		<category><![CDATA[PRXMATCH]]></category>
		<category><![CDATA[punctuation]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SAS functions]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[text strings]]></category>
		<category><![CDATA[uppercase]]></category>
		<category><![CDATA[uppercase letter]]></category>
		<category><![CDATA[VALIDVARNAME]]></category>
		<category><![CDATA[variable name]]></category>
		<category><![CDATA[white space]]></category>
		<category><![CDATA[whitespace]]></category>
		<category><![CDATA[whitespace character]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=1262</guid>
		<description><![CDATA[There are whole pile of SAS functions for testing text strings that hadn&#8217;t come to my attention until this week. Until then, I&#8217;d have gone about using functions like INDEX and PRXMATCH functions for the same sort of ends but it&#8217;s never any load to have a few different ways of doing things and to [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2010/01/22/a-few-more-sas-functions-to-know/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>%sysfunc and missing spaces</title>
		<link>http://technologytales.com/2009/06/10/sysfunc-and-missing-spaces/</link>
		<comments>http://technologytales.com/2009/06/10/sysfunc-and-missing-spaces/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 11:22:18 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Command Line]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[windows batch file]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=931</guid>
		<description><![CDATA[Recently, I was trying something like this and noted some odd behaviour: data _null_; file fileref; put &#8220;text %sysfunc(pathname(work)) more text&#8221;; run; This is the kind of thing that I was getting: text c:\sasworkmore text In other words, the space after %sysfunc was being ignored and, since I was creating and executing a Windows batch file [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2009/06/10/sysfunc-and-missing-spaces/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AND &amp; OR, a cautionary tale</title>
		<link>http://technologytales.com/2009/03/27/and-or-a-cautionary-tale/</link>
		<comments>http://technologytales.com/2009/03/27/and-or-a-cautionary-tale/#comments</comments>
		<pubDate>Fri, 27 Mar 2009 11:21:13 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[infinite loop]]></category>
		<category><![CDATA[log]]></category>
		<category><![CDATA[macro]]></category>
		<category><![CDATA[macro code]]></category>
		<category><![CDATA[macro processor]]></category>
		<category><![CDATA[NRSTR]]></category>
		<category><![CDATA[quoting]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SAS Macro]]></category>
		<category><![CDATA[SUPERQ]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=795</guid>
		<description><![CDATA[The inspiration for this post is a situation where having the string &#8220;OR&#8221; or &#8220;AND&#8221; as an input to a piece of SAS Macro code breaking a program that I had written. Here is a simplified example of what I was doing: %macro test; %let doms=GE GT NE LT LE AND OR; %let lv_count=1; %do %while [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2009/03/27/and-or-a-cautionary-tale/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Working with the ODS templates and styles when batch processing</title>
		<link>http://technologytales.com/2008/12/08/working-with-the-ods-templates-and-styles-when-batch-processing/</link>
		<comments>http://technologytales.com/2008/12/08/working-with-the-ods-templates-and-styles-when-batch-processing/#comments</comments>
		<pubDate>Mon, 08 Dec 2008 16:34:36 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[batch mode]]></category>
		<category><![CDATA[batch processing]]></category>
		<category><![CDATA[ODS]]></category>
		<category><![CDATA[RSASUSER]]></category>
		<category><![CDATA[SAS]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=691</guid>
		<description><![CDATA[I ran into some trouble with creating new templates and styles while running a SAS job in batch mode. The cause was the user of the RSASUSER switch on the SAS command. This sets the SASUSER library to be read-only and that is what is used to store new templates and styles by default. The [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2008/12/08/working-with-the-ods-templates-and-styles-when-batch-processing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SAS Macro and Dataline/Cards Statements in Data Step</title>
		<link>http://technologytales.com/2008/10/28/sas-macro-and-datalinecards-statements-in-data-step/</link>
		<comments>http://technologytales.com/2008/10/28/sas-macro-and-datalinecards-statements-in-data-step/#comments</comments>
		<pubDate>Tue, 28 Oct 2008 12:56:05 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[data step]]></category>
		<category><![CDATA[macro]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SAS Macro]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=650</guid>
		<description><![CDATA[I recently tried code like this in a SAS macro: data sections;         infile datalines dlm=&#8221;,&#8221;;         input graph_table_number $15. text_line @1 @;         datalines;         &#8220;11.1           ,Section 11.1&#8243;,         &#8220;11.2           ,Section 11.2&#8243;,         &#8220;11.3           ,Section 11.3&#8243;         ; run; While it works in its own right, including it as part of a macro yielded this type [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2008/10/28/sas-macro-and-datalinecards-statements-in-data-step/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Error: User does not have appropriate authorization level for library xxxx</title>
		<link>http://technologytales.com/2008/06/25/error-user-does-not-have-appropriate-authorization-level-for-library-xxxx/</link>
		<comments>http://technologytales.com/2008/06/25/error-user-does-not-have-appropriate-authorization-level-for-library-xxxx/#comments</comments>
		<pubDate>Wed, 25 Jun 2008 09:06:04 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Explorer]]></category>
		<category><![CDATA[log]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Operating System]]></category>
		<category><![CDATA[permission]]></category>
		<category><![CDATA[permission settings]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SAS data set]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=357</guid>
		<description><![CDATA[In a world where write access to a folder or directory is controlled by permission settings at the operating system level, a ready answer for when you get the above message in your log&#160;when creating a SAS data set would be to check your access. However, if you are working in Windows and your access [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2008/06/25/error-user-does-not-have-appropriate-authorization-level-for-library-xxxx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Transferring data between SAS and R</title>
		<link>http://technologytales.com/2008/06/05/transferring-data-between-sas-and-r/</link>
		<comments>http://technologytales.com/2008/06/05/transferring-data-between-sas-and-r/#comments</comments>
		<pubDate>Thu, 05 Jun 2008 08:49:20 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[data transfer]]></category>
		<category><![CDATA[export data]]></category>
		<category><![CDATA[import data]]></category>
		<category><![CDATA[R]]></category>
		<category><![CDATA[SAS]]></category>

		<guid isPermaLink="false">http://technologytales.com/?p=322</guid>
		<description><![CDATA[A question regarding the ability to transfer of data between SAS and R set me off on a spot of investigation a while back and I have always planned to share the results of my labours. Once I managed to locate the required documentation, things became clearer with further inspection. Functions from the foreign package [...]]]></description>
		<wfw:commentRss>http://technologytales.com/2008/06/05/transferring-data-between-sas-and-r/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
