SAS Support Communities

OldTimer is right. Unquoting is sometimes hit and miss. The only way I could make this work is by using proc sql noprint; select distinct trim(&attrib) into :&attrib._1 - :&attrib._4 from test; quit; and then %unquote(&lefty.ratio_&&&attrib._1&lefty.n)=N/195; I am unsure why you'd want to carry these hideous names in the data step instead of calling the new variables INFO1-4 and RATIO1-4 though. This would also allow you to write RATIO[CLASS_N]=N/195; instead of doing successive tests. ... View more

Use Scott's links to understand the following: [pre]data OUT; input PAT_ID MONTH1 MONTH2 MONTH3; * can be written input PAT_ID (MONTH1-MONTH3)(:); if MONTH1 then do; MONTH1=sum(of MONTH1-MONTH3); call missing(MONTH2, MONTH3); end; else if MONTH2 then do; MONTH2=sum(of MONTH1-MONTH3); call missing(MONTH1, MONTH3); end; else if MONTH3 then do; MONTH3=sum(of MONTH1-MONTH3); call missing(MONTH1, MONTH2); end; else call missing(of MONTH1-MONTH3); cards; 1 0 1 2 2 1 1 2 3 2 0 1 4 0 0 3 5 3 0 0 6 0 0 2 7 0 2 0 8 0 2 2 ; run; [/pre] If you had many months, you'd loop thru them using an array, as Scott said, rather than adding tests. One step at a time though. ... View more

Have you read the CEDA pages? Particularly:http://support.sas.com/documentation/cdl/en/lrcon/61722/HTML/default/a002143983.htm Also about data migration: http://support.sas.com/rnd/migration/planning/files/crossplatform.html Why CEDA Is Invoked for a SAS®9 File in a SAS®9 Session Character encoding: CEDA is invoked when you share a file with users in another locale who have an incompatible encoding. For more information, see the topic about national language support or see Processing Data Using Cross-Environment Data Access (CEDA) in SAS Language Reference: Concepts. Operating environment family: In a SAS®9 session, you can run the CONTENTS procedure on any SAS®9 file to determine the operating environment where it was created. To learn the operating environment of your current SAS®9 session, create a quick data set and run PROC CONTENTS on it. If the data representation of the file matches that of your current operating environment, then the file is native on that operating environment. If you're running under AIX, Solaris, or HP-UX, you'll notice all of those operating environments are listed in the log, because those operating environments comprise an operating environment family. To know when CEDA is being used, set the SAS system option MSGLEVEL=I. That is: options msglevel=i; Here's an example of the message that displays in the log: INFO: Data file MYFILES.GRADES.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. Beginning with SAS 9.1.3 Service Pack 4, you get this behavior even if you do not specify MSGLEVEL=I. Run proc contents, and use the OUTREP= option if needed. ... View more

The code above does not work. Please check before posting. I want ALL records for EACH gender whose maximum value for age is in the interval [16,17]: select * from sashelp.class group by sex having 16 le max(age) le 17 ; ... View more

How about you use the description and : 1- replace F10.3 by 10.3 2- replace I5 by 5. to create the input statement. On the data side (in the file): 1- replace StarSpace with SpaceDot Would that work? ... View more

It'd be good that you post code that anyone can run. For eg, replace your data with sashelp samples. ... View more

You'll need something like this: [pre] data OUT; set SASHELP.CITIDAY(keep=DATE SNYDJCM); DSID=open('SASHELP.CITIDAY(keep=DATE SNYSECM where=(DATE > "10jan1988"d and (DATE between ' || put(DATE-1,5.)||' and '||put(DATE+1,5.)||')))'); RC=fetch(DSID); if RC=0 then do while(RC=0); SNYSECM=getvarn(DSID,varnum(DSID,'SNYSECM')); *replace varnum() by the number to speed up a wee bit; output; RC=fetch(DSID); end; else output; RC=close(DSID); run; [/pre] (I left join the table to itself within 1 day here). Also, you'll need an index on the secondary table of course. If you have version 9.2, you might want to look at hash tables as this version allows hash tables with non-unique keys. 2 dates + cusid + w/off + interest occupy 4+4+8+8+8=32 bytes. That's 33 million rows per GB of RAM. Otherwise, the logic above with the secondary table loaded in memory using a sasfile statement is another option. Message was edited by: Chris@NewZealand ... View more

Merci André! ... View more

Thanks Curtis. Rows are read only once (if applicable) and retained (and potentially over-written), not read over and over as SQL does. It makes perfect sense now. A cartesian product is probably more useful (as well as more resource-intensive) than this behaviour, but as long as we are aware of what takes place ... ... View more

How about sas sql: select unique EMPNO into :EMPNOS separated by ',' from EMPLIST; db2 passthough sql: Select emp_name, emp_status from EMPLOYEE WHERE Employee_NO in (&EMPNOS) ; Limitation: &EMPNOS is limited to 64k ... but you can always use several lists if db2 supports longer sql statements. ... View more

Weird. Try playing with the number of records: proc gplot data=test(obs=100); plot v1*v2; run; to see whether: 1- a specific record throws sas off 2- the volume of data plays a role ... View more

Try using a stylesheet name without the $ sign to export. ... View more

How does this differ from using proc gchart's subgroup= option? ... View more

If you only want the top 5, the outobs= option is your friend. If you have group by, you probably need 2 steps as in: [pre] proc sql; * find best selling products by region; create view SUM as select REGION, PRODUCT, sum(SALES) as SALES from SASHELP.SHOES group by REGION, PRODUCT order by REGION, SALES desc ; quit; data TOP3; * keep the top 3 for each region; set SUM; by REGION ; if first.REGION or lag(first.REGION) or lag2(first.REGION); run; data TOP3; * keep the top 3 for each region, alternative method; set SUM; by region ; if first.REGION then N=0; N+1; if N <= 3; drop N; run; ... View more