Since a DATA _NULL_ step will not create a dataset, OUTPUT is useless.
data _null_;
set sashelp.class;
where sex = 'M' ;
group_seq + 1;
do i = 1 to 5 ;
put @5 name @20 sex @28 group_seq;
end;
run;
The SUM statement implies a RETAIN, and the variable is initialized to zero.
... View more
As a consultant, it is your duty to educate your client about the utter stupidity of storing date values as character (no calculations possible, do not sort correctly, ...).
As soon as you have intelligent data, sorting by outward_postcode and mon_year with a following PROC TRANSPOSE or PROC REPORT (without prior sorting!) will solve your issue quite nicely, with simple code, and no further action needed if there's an additional prodgrp.
... View more
Since you have your %PUT statement before the end of the DATA step code boundary (which is established by the CARDS/DATALINES block), SAS will resolve it before the DATA step is compiled and runs, so the macro variables won't exist yet. If you resubmit the step, you'll display the values coming from the previous execution.
... View more
DON'T.
Patient ID's are codes, not numbers, and should always be stored as character. You will never do calculations with them, but numeric might lead to imprecisions or loss of information (like leading zeroes).
... View more
The ERROR does not come from SAS. It originates in the MS SQL server, so it seems someone managed to create an illegal column name there. Or the column isn't even there in the first place; you may have mistaken a label for a name.
PS run PROC CONTENTS on CONN.&TBLNM
... View more
Let's call your first dataset "patients", and the second "have".
data reference;
set patients;
do date = stat_date to end_date;
output;
end;
keep patient date;
run;
data want;
merge
have (in=h)
reference (in=r)
;
by patient date;
oor = (h and not r);
miss = (r and not h);
run;
You can now use the two boolean variables for further analysis.
... View more
If you want to use PROC PRINT, use the OBS= dataset option to reduce the amount of rows, and a VAR statement to select only some of this mass of variables.
... View more
I made a mistake in my earlier post, and so it failed to reveal your issue.
data test (read=xxx);
set sashelp.class;
run;
proc print data=test (read=xxx);
run;
Now I get the same pop-up because of the failure of the viewer to open the dataset, but the PROC PRINT output works.
So it is now confirmed that On Demand can work with password protected files, but (IMO) the dataset/table viewer should ask the user for a password instead of just failing.
... View more
You must place the stylesheet and scriptfile in a location from where the web server (apache/httpd, not the web application server) can serve them, and use the corresponding web path as your href. Keep in mind that the browser is the place where everything has to come together.
... View more
I ran this short test:
data test;
set sashelp.class (read=xxx);
run;
proc print data=test (read=xxx);
run;
and could verify that password protection is working on SAS On Demand.
So it's either the dataset itself or the password which does not work.
Since there's no longer a direct link to SAS technical support on the ODA site, I'm calling out to @ChrisHemedinger if he can find us someone who can deal with this specific kind of issue.
... View more
