Yes, the option binomial (p=__ ) must contain a numeric value and not a variable name. So if you want the value to change every run of the PROC, you will need to build a macro. Yes, if you have very big data sets, it will run slowly, but I am not aware of any other way to get the job done. ... View more

In SAS 9.4, you can create abbreviations. Type a few letters, and a large block of code (whatever you want) is inserted into your code. I use it because the databases here have some variable names that I often mis-spell, so now, for example, I type the 3 letter abbreviation cyc and press ENTER and SAS includes in my code a much longer variable name that is always spelled properly.   In the SAS 9.4 Enhanced Editor, select Tools->Add Abbreviations. From there, I leave it as a homework assignment for you to figure out what to do next. ... View more

@Anv_SAS wrote: Hi Paige Miller, I work on a study and I was instructed to generate Cartesian Product from 2 datasets applying 2 filter conditions, to ensure the respective records only needs to be used. Also I was instructed not to use direct Cartesianing techniques like PROC SQL or DATA step POINT statement. Okay. Thank your for the explanation. I feel sorry for you, that you have been told to do something but you can't use tools specifically designed to perform the desired task. Its like telling a carpenter that he can't use a saw or telling a plumber he can't use a wrench.   Still, it is highly recommended that you mention the goal at the beginning (for this thread and for all future threads) instead of not mentioning it. Perhaps if people knew you were trying to create Cartesian product with macro variables, a brilliant idea would pop into someone's head that would get you there quickly (and there are a lot of people who do have brilliant ideas in this forum).   Anyway, I will drop out of this discussion now, as I do not care to hurt my brain creating Cartesian products using macro variables. Best wishes and good luck. ... View more

@Cynthia_sas wrote: Hi:   I am not sure you'll ever see the change in the data viewer in EG. However, based on this example https://documentation.sas.com/doc/en/statug/15.2/statug_kaplan_sect045.htm in the documentation about how to get a large dash in PROC LIFETEST, I used the ODS ESCAPECHAR string (*ESC*){Unicode '2014'x} that they show and the results seemed to work for me in ODS output. Basically, I changed your code to use the ODS ESCAPECHAR string in the TRANWRD function and then used PROC PRINT to send the output to either the default destination or ODS PDF or ODS RTF.   Just pointing out that is an EM dash. Unicode 2013 is the EN dash. ... View more

Saying "none of the solutions worked" gives us no information to help figure out what the problem is. We need at least these items of information: What is your SAS interface? Show us the code you are using. Show us a screen capture of the result where the en dash has disappeared. What language do you have SAS set to? ... View more

En-dash is hex 96 (see https://www.ascii-code.com/CP1250) ... so you want   region_en_dash = tranwrd (region, "--", "96"x);   ... View more

My requirement is to pull pool of records into a single macro variable conditionally.   Data from several (many) records does not belong in a macro variable. It belongs in a SAS data set. Please explain your project in more global terms, do not talk about SAS code, but do talk about what the data is and how will you use of the data once you pull it. ... View more

Most likely this is an example of computers having limited numeric precision. See Machine Precision. Or perhaps two different programmers chose to handle the extreme case of SD=0 slightly differently.   It's nothing to worry about. I'm sure that in other cases, PROC UNIVARIATE and PROC TTEST will give matching results. ... View more

Macro variables created inside a macro can only be accessed within that macro (or by macros called by this macro). These macro variables do not have a value in open code (which is code outside of any macro).   You can fix this by adding a %GLOBAL statement into your macro.   %global age11;   By the way, I realize that this is probably just an example to learn macro code, but you really should never need to partition a data set this way by using macro loops, or extract information from a data set by using macro loops. There are better tools that are also easier to program with. Part of learning to use macros is learning when to NOT use macros. ... View more

@aamoen wrote: The goal is to add a prefix to the field names itself.  Not to alter the values of any given field.   WHY? What is the ultimate goal of this project/analysis/data manipulation? Please describe the project. ... View more

Your extremely brief problem description leaves me wondering if you want to add the prefix to the variable NAMES, or a prefix to the variable VALUES. You don't tell us. Which is it?   Also, if you are talking about variable NAMES, this could be a symptom of poor data layout or poor data arrangements, and it might be that re-arranging your data will eliminate the need to change variable names. Specifically, people create wide data sets with lots of somewhat repetitive variable names, except for a prefix or suffix; while a long data set eliminates the need for lots of variable names and eliminates the need for bulk renaming.   Which brings us to the main point I want to make. We need you to help us, which in turn helps you. We need much more detailed problem statement, and we need to know WHY you are doing this; once we know this we can come up with (possibly) a better approach that is easier to program, and get you to your final destination a lot faster than renaming would get you there. Please also take a few minutes and read up on the XY Problem as I think this is important and relevant in this case, and really in all cases; we need to know what you are doing and WHY you are doing it in all future posts as well. ... View more

In most (all?) SAS interfaces that I know of you can create an abbreviation, so if you type the abbreviation and press ENTER, whatever text you designated to go with that abbreviation will be inserted. So for example, I have the abbreviation ohc (just those three letters) and when I type ohc and press ENTER the text ods html close; appears in my code.   So you could create the abbreviation %sf, for example.   You can create abbreviation/alias for any code you want. ... View more

@NewUsrStat wrote: Thank you very much for your support but I need to do the following for each variable:    proc freq data = mydata; table Q17_test14 / out = stats_Q17_test14(drop = percent); run; Here only one variable is shown. As you can see the prefix is "Q17_" and the prefix of the output is "stats_".    I cannot put all the out tables together because I need to do additional calculation on a subset of them. I have to disagree. You can take the output data set from the code I provided and then perform tasks on just a part of the data set. ... View more

@NewUsrStat wrote: Hi guys,  suppose to have a sas dataset of 51 rows and 50 columns.  I would like to do a PROC FREQ of each of the 50 columns. No combinations or something like that but only PROC FREQ and out with the prefix "stats" and then the name of the variable (column).  Columns (variables) have different names but all starts with Q17_   Is there a way to not to do this variable by variable?  Better you should ask how to run PROC FREQ on each variable, rather than specifying a specific solution (in this case you specified you want a loop). No need for loop at all.   proc freq data=yourdatasetname; ods output onewayfreqs=onewayfreqs; tables q17_:; run;     Then this code will help re-arrange the output data set into something that might be more usable: Re: proc freq one way table for multiple vars- export to data set - SAS Support Communities ... View more