NOMINOPERATOR ... View more

  Minor syntax issues aside, you need the "minoperator" option. option minoperator; %let testid = A967; %let allids = A967 A980 A982; %put &testid; %put &allids; %macro johntest(inTestid, inallids); %if &inTestid in (&inallids) %then %do; %put yes; %end; %else %do; %put no; %end; %mend; %johntest(&testid, &allids); ... View more

You're welcome. This is just the tip of the iceberg in terms of what you can do with ODS, so keep at it.  ... View more

Put the "sandwich" around whatever output you want to send the file.   Every output generated between the "ods rtf..." and "ods rtf close;" will end up in the specified file. So if you put the opening of the sandwich at the the top of the code and the ods close at the bottom, all generated output will go into that RTF. That might be more than what you want, of course. Also note that you'll also get the default output, too, unless you close other ods destinations. ... View more

Without seeing the data, it's difficult to help, but if rowpct or colpct won't do what you want, this is likely a case where you're going to have to use a custom denominator for calculating percentages.   https://support.sas.com/resources/papers/proceedings13/134-2013.pdf ... View more

Here's a simple example:   ods rtf file = "c:\my_sas_output.rtf";   proc print data = sashelp.class; run;   ods rtf close;   You'd then go to Windows explorer to your C drive and open the file. Change the path and file name to reflect what you really want, of course. ... View more

I would send my output to an RTF using the appropriate ODS statements. Then that file should have output that is far easier to put into Word.   For example:   ods rtf file = "YourPath\YourFileName.rtf";   Your SAS code to create output...   ods rtf close;   There's a lot you can do to customize your output to minimize how much you need to do manually after creating it, but that's another topic. ... View more

Given what you want, PGStats approach is the right way to go. ... View more

And you don't care which rows they are, as long as there are only 50, for example, in the first query?   I don't know what all the other queries look like, but for what you've shown, try adding the following to the where statement:   PROC SQL; create table CombinedSample as (select account_number, 'Cell1' as seed from Dataset1 where age between 16 and 34 AND monotonic() <= 50) union ... View more

The documentation says that width is "specifies the width of the annotation. Specify a positive number greater than zero. You can use the WIDTHUNIT variable to specify the unit of measurement." That seems straightforward and I'm sure you've looked at that as well, so my question is what happens to the resulting graph when you change value from 75 to, say, 100? Or 50? Does it not affect the annotation? What if you omit it altogether? I would think its effect as you alter its value in the code would give you some indication of what it's doing, no? ... View more