About stateworker

stateworker · ‎05-27-2011

Have to agree with SASKiwi - save your Excel spreadsheet as a delimited file (we prefer tab delimited, but obviously it will depend on the contents of your data as to what delimiter you choose). This is one example of when knowing what's available as a component of SAS but not having that feature makes one covetous 🙂

stateworker · ‎05-19-2011

Are you wanting to store Sex as "male" "female" or just have it so it displays as "male" "female" in SEX variable? See if this helps for whichever way you're wanting to do it. ***************** PROC FORMAT; VALUE $sexf 'F' = 'Female' 'M' = 'Male' ; RUN; **************** DATA TEST; INPUT NAME $8. SEX $1. ; DATALINES; ADAMS M LINCOLN F ROGERS M HILTON F SMITH X ; RUN; *** use X to show one that doesn't fit the format ***; PROC PRINT DATA=TEST; RUN; *** sex stored as M/F ***; PROC PRINT DATA=TEST; FORMAT SEX $SEXF.; RUN; *** sex still stored as M/F ***; PROC CONTENTS DATA=TEST; RUN; *** see no permanent format applied ***; DATA file02; SET TEST; format sex3 $sexf.; sex1=PUT(sex,$sexf.); *** stores as Male/Female ***; sex2=sex; *** stores as M/F ***; sex3=sex; *** stores as M/F, displays as Male/Female ***; RUN; PROC PRINT DATA=FILE02; RUN; PROC CONTENTS DATA=FILE02; RUN; *** permanent format applied to sex3 only ***; data file02; LENGTH sex $6; /*to change the length from 1 to 8 */ set file02; sex=put(sex, $sexf.); *** stores as Male/Female ***; run; PROC PRINT DATA=FILE02; RUN; PROC CONTENTS DATA=FILE02; RUN;

stateworker · ‎05-18-2011

I'm glad you asked this because I've needed to do this and didn't know how! Thanks!

stateworker · ‎05-18-2011

I'm glad you asked this because I've needed to do this and didn't know how! Thanks!

stateworker · ‎05-18-2011

If you decide to brute force it, format M $2. Y $4.; M=substr(var, 1,2); *** this will give you the 99 before the slash ***; Y=substr(var, 4,4); *** this will give you the 9999 after the slash ***; newdate=(M||Y); *** this will concantenate the two variables to give you 999999 ***;

stateworker · ‎05-18-2011

> If they are formatted dates, just change the format. > If they are character strings, there are several > character functions that will do it; SUBSTR and || > is sort of brute force, but will work. Brute Force - Love it. I have to put in a good word for this book that is well-worn along with my SAS course books I've collected... It's available in the SAS bookstore and other places. The Essential Guide to SAS Dates and Times By: Derek Morgan 176 pages ISBN: 978-1-59047-884-4 Publisher: SAS Press Copyright Date: June 2006 Description: Why does SAS use January 1, 1960, as its arbitrary reference date? How do you convert a value such as 27 January 2003 into SAS dates? You'll find the answers to these questions and much more in Derek Morgan's Essential Guide to SAS Dates and Times, which makes it easy to understand how to use and manipulate dates, times, and datetimes in SAS. Novice-to-intermediate users will find the clear, task-focused examples and explanations of formats and functions invaluable; experienced users will appreciate discussions of topics such as intervals and international date and time formats. Included is a bonus "Quick Reference Guide" listing all the formats (with examples) on one handy page.

stateworker · ‎05-17-2011

Thanks! I can use this!!!

stateworker · ‎05-17-2011

We don't have the ability to export directly to Excel, so I don't know about this, but I do know that Excel will often open a new workbook with multiple sheets - default tends to be three unless you change that. When you say you only get the sheets when spreadsheet already exists, does that mean when you originally create the spreadsheet via SAS, you don't get it, but then you Replace into it, it adds three blank sheets? Or do you mean you've created an workbook via Excel and then export into it?

stateworker · ‎05-17-2011

data set3; merge dataset1 (in=a) dataset2 (in=b keep=var1 var2); by var1; if a; run; This will make a new data set (never overwrite your original data set when testing out code!) by merging your first and second data sets by your common variable. If dataset1 has var1's that aren't in dataset2, then set3.var2 will be empty. But where dataset1's var1 equals dataset2's var1, then set3.var2 will be the same as dataset2.var2. However, if you need dataset2's var1's that aren't also in dataset1, then this won't work because it will only bring in those where the var1 is in common.

stateworker · ‎05-13-2011

KSharp - what does the (+(-1) do? Does that remove the space between the variables where a delimiter would usually go? > [pre] > data _null_; > file "c:\wa.txt"; > t sashelp.class; > put (name sex age weight height) (+(-1)); > run; > [/pre] > > Ksharp

stateworker · ‎03-30-2011

What is the error message you get?

stateworker · ‎12-20-2010

Thanks for the tips and ideas. We recreated our formats on the new operating system / version of SAS on the server and that seems to have resolved part of our issues. We are attempting to PROC MIGRATE old data sets to see if that will work. However, we are still getting the Cross Environment Data Access notes even when we create new data sets from text files. Do we need to do anything with the text files? Seems like that shouldn't be an issue. I need to read more about CEDA - but mostly just wanted to say thanks for the help! Any other advice / suggestions / experiences / things to look out for would be greatly appreciated!

stateworker · ‎12-14-2010

Hi. We have just yesterday gotten a new server (Windows 64-Bit) and are having trouble getting things set for our clients to work with the server. We are able to remotely access our data, but our Catalogs / Formats apparently need to have something else done as well as our data sets - see the example from my log where I tried to run something - It will run successfully when I use the options nofmterr; Any tips for what we need to do for our data sets or catalogs or whatever would be greatly appreciated. I've looked in the help section and see info about PROC CPORT and PROC CIMPORT but didn't really understand how to do that - nor was I wanting to risk messing up the data set in my trial and error without asking first. If this is the wrong section of the forum, please let me know where a better place might be to ask. We'll likely be calling SAS in the next day or so for help but thought I'd check with you all too. NOTE: Remote submit to MYNODE commencing. 1 DATA CINDY.FELONS_DEC10; 2 SET CCH.JUD_D2101201 (KEEP=JUD_DLE_NBR JUD_DISP_CD JUD_DISP_DT JUD_CHG_LVL JUD_ADD_DATA ); NOTE: Data file CCH.JUD_D2101201.DATA is in a format that is native to another host, or the file encoding does not match the session encoding. Cross Environment Data Access will be used, which might require additional CPU resources and might reduce performance. 3 WHERE JUD_DISP_CD EQ 310 AND JUD_CHG_LVL=1; 4 YEAR=PUT(JUD_DISP_DT, YEAR4.); 5 BYTE27=SUBSTR(JUD_ADD_DATA,27,1); 6 RUN; ERROR: File FORMATS.CCHFORM.CATALOG was created for a different operating system. ERROR: File FORMATS.ORI.CATALOG was created for a different operating system. ERROR: File FORMATS.OFF.CATALOG was created for a different operating system. ERROR: The format CDISP was not found or could not be loaded. NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set CINDY.FELONS_DEC10 may be incomplete. When this step was stopped there were 0 observations and 7 variables. WARNING: Data set CINDY.FELONS_DEC10 was not replaced because this step was stopped. NOTE: DATA statement used (Total process time): real time 14.33 seconds cpu time 0.03 seconds NOTE: Remote submit to MYNODE complete. Thanks.

stateworker · ‎11-15-2010

If I understand what you're looking for correctly, you want to end up with a data set that has records that var2 is the same in your contributing data sets but var1 is not? Is that right? If so, this could work for you. PROC SORT the two data sets by var2. Then do a DATA / MERGE / BY / IF. DATA DSET3; MERGE DSET1 (IN=A) DSET2 (IN=B RENAME=(VAR1=DSET2VAR1)); BY VAR2; IF A AND B; IF VAR1=DSET2VAR1 THEN DELETE; This puts all the records into DSET3 where they have the same VAR2 and then takes out those where the VAR1 is the same. SAS doesn't care how many records you have - only issue would be your processor / storage / work space.

stateworker · ‎09-30-2010

Could you use CREATE TABLE lib.dataset AS for your second line of code after the PROC SQL;?

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: How to read Excel to SAS without DDE or SAS /Access Interface to ...

Re: PROC FORMAT

Re: move a column to be the first one

Re: move a column to be the first one

Re: date-remove slash

Re: date-remove slash

Re: how to export data without delimiters?

Re: Proc Export to Excel: Extra Sheets?

Re: looking to create a new var based on the values of a second datase...

Re: how to export data without delimiters?

Re: Saving Frequency Tables in Excel

Re: How to read Excel to SAS without DDE or SAS /Access Interface to ...

Re: PROC FORMAT

Re: move a column to be the first one

Re: move a column to be the first one

Re: date-remove slash

Re: date-remove slash

Re: how to export data without delimiters?

Re: Proc Export to Excel: Extra Sheets?

Re: looking to create a new var based on the values of a second datase...

Re: how to export data without delimiters?

Re: I NEED URGENT HELP With Date Format!

Re: moved to a new server, getting errors and need ideas, please.

moved to a new server, getting errors and need ideas, please.

Re: To identify the un-matching records

Re: Creating data set from query