Ah the beauty of standards! that was an entertaining thread! Even Microsoft has varying standards for its EOL delimiter. Good stuff! We'll never know why CP/M used both the 0D and 0A as if they used a teletypewriter. Actually, just got me curious: it is all explained at http://en.wikipedia.org/wiki/Line_feed ASCII was developed simultaneously by the ISO and the ASA, the predecessor organization to ANSI. During the period of 1963–1968, the ISO draft standards supported the use of either CR+LF or LF alone as a newline, while the ASA drafts supported only CR+LF. Nothing like competing standards to enhance the life of users... >Perhaps I'm dense or inexperienced lol Cynthia! 🙂 Jerry, as Cynthia explained, the reason EOL characters are normally not stored in sas is the same reason css was invented for html: to separate data from presentation, and the exceptions (as always, there are exceptions) are the split= option in some reporting procedures, and the ods escapechar. ... View more

Have you tried reorganising your data to use [pre]define month /across[/pre] so that the values of [pre]column &&mname&zz [/pre] now come from one variable ? There is no girl aged 16, and the column 16 does not appear for girls in: [pre] proc sort data=SASHELP.CLASS out=CLASS; by SEX; proc report data=CLASS nowd; define AGE /across; define WEIGHT /mean; column AGE,WEIGHT; by SEX; run; quit; [/pre] If you force the column name in the column statement, then that column will be shown. ... View more

My code (as well as others') should work, unless the issue was misunderstood. Pls explain what is not right. ... View more

See http://support.sas.com/rnd/scalability/procs/index.html ... View more

Values (not "labels") are exactly centered on the tick marks with: goptions reset=ALL gunit=pct colors=(black) ftext=hwcgm001 ftitle=hwcgm009 htext=3 noborder maxcolors=255 device=CGMOFML hsize=10 in vsize=8 ; axis1 value=(a=90 h=3pct) /*order=(0 to 800 by 200)*/ minor=none label=(a=90 color=black "Mean, (ng/mL)") offset=(1); axis2 /*order=(0 to 80 by 20)*/ minor=none label=(color=black "Time (hr)") offset=(1); proc gplot data=sashelp.air; plot air*date / vaxis=axis1 haxis=axis2; run; quit; If you add format air 8.0;, a shift can be seen. I reckon that may be the reason you see that "buffer": you request a long format, and sas provides it. ... View more

what procedure and device is this used with? More code needed imho. ... View more

Better to make one's logic explicit imho: proc sort data=FirstVisit; by UserID DATE RecordNo; run; data FirstVisit set FirstVisit ; by UserID; if first.UserID; run; ... View more

Scott, I think you misread the question. Does STAMP=time(); do what you want? Don't forget to add format STAMP time.; If you want the time be be constant throughout the table: retain STAMP; if _N_=1 then STAMP=time(); ... View more

>if a customer purchase at company A, how much ... they spend there. This is not what you are showing: A 4+6+5(R1+R5+R10) is for all customers. In any case, here is how to obtain the same numbers you are showing. Efficient is not how I would describe it, but it works. Loading the table in memory speeds things up when making the successive passes (You might want to drop unnecessary columns if you have many). If the amount of memory you have is too small, the code will still work, but an index on CID and maybe another on COMPANY will help speed. [pre] data T; * sample data; input R CID COMPANY $1. AMT ; cards; 1 111 A 4 2 111 D 2 3 111 G 3 4 111 X 4 5 112 A 6 6 112 D 2 7 112 G 8 8 113 G 4 9 113 X 2 10 114 A 5 11 115 X 5 run; data FINAL; * prepare output table; delete; run; sasfile T load; * load data in memory; proc sort data=T(keep=COMPANY) out=COLIST nodupkey; * get list of companies; by COMPANY; run; %macro t; %let dsid=%sysfunc(open(COLIST)); %let rc=%sysfunc(fetch(&dsid)); %do %while(&rc=0); * loop thru companies; %let coname=%sysfunc(getvarc(&dsid,1)); proc sql; * derive figures for 1 company; create table CO_&coname as select sum(AMT) as &coname ,COMPANY from T where CID in (select unique CID from T where COMPANY="&coname") group by COMPANY; quit; proc transpose data=CO_&coname out=CO_&coname; * put figures in 1 row; id COMPANY ; run; data FINAL; * add to output table; set FINAL CO_&coname; run; %let rc=%sysfunc(fetch(&dsid)); %end; %let rc=%sysfunc(close(&dsid)); %mend;%t sasfile T close; * unload data from memory; ... View more

Thanks for your input guys, much appreciated. Nice machine you have,Daniel! ... View more

Just putting this in the fore once as a last attempt for a comment. Has anyone replicated this behaviour? No idea why views would be faster? 2 explanations I can think of: - When using views, input tables are read sequentially. When using tables, all tables are read concurrently one record at a time (which would thrash the disks). But then where is the data stored? Much higher memory usage with views is in no way sufficient to store all the data. Maybe tables are just read in much larger blocks when using views? - The keep statement is not used as efficiently when using tables, and full observations are read, even if not stored in the limited PDV. I added the option bufno=1k when reading tables T&i and times decreased dramatically (but memory usage stayed the same somehow). So it looks like the 1st idea might be right: views use larger blocks. Any comment? ... View more

You can even do Patrick's suggestion in one go: data x_update; merge x(drop=x) x(keep=id x where=(x ne .)); by id; run; ... View more

Seeing that the columns total is 8+7=15, and the line total is 6+4+4=14, you have no chance. ... View more

use option NOFRAME ? ... View more

Your code should either be PROC SQL; Connect to oracle..... create table WORK.xx as select * from connection to oracle ( SELECT "xyz" as File_name, Count(*) AS members, sum(yy_AMT) as yy_AMT FROM WORK.zzz ); quit; or PROC SQL; create table WORK.xx as SELECT "xyz" as File_name, Count(*) AS members, sum(yy_AMT) as yy_AMT FROM WORK.zzz ; quit; The ANSI part of the syntax is the same, but there can be differences on "extensions" like sas dataset options or oracle partitions. In the 1st case you must use oracle syntax (and functions like to_number()) inside the connection brackets. You must use sas syntax outside (where the select * is). In the 2nd case you must use sas syntax (and functions like input() that Scott suggested). This works: data T; X='1';output; X='2';output; proc sql; select sum(input(X,1.)) from T; quit; This works too: proc sql; connect to ORACLE ... select * from connection to oracle ( select sum(to_number(APPLNT_LOCL_ID)) from ... where ROWNUM ≤ 10); disconnect from oracle; quit; ... View more