The SAS DATA step is an implied loop. You don't have to write a loop, in fact, writing a loop is wrong.   So the data step reads the first line of data from pumpkin.dat, computes the values of avgscore, dayentered and type for that line of data. Then it knows to read the second line of data, then it computes the values of those three variables from the second line of data;  and then keeps going like that on to the last line of data. ... View more

@ballardw wrote: How is this different than your other basically identical question in https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-deal-with-percentage-when-the-denominator-is-equal-to/m-p/972436#M46092     What sort of "solution" are you looking for? The DIVIDE function is possibly the easiest but if that doesn't meet your need then describe what is needed. I already asked in that other thread what solution was needed, but no answer was forthcoming. In my mind, it all depends on what you plan to do with this data where some of the percents have 0 in the denominator. In my mind, this isn't a coding problem, it is a problem where @alepage needs to figure out what the right answer is for his situation (possibly with help from us). Then coding is pretty simple. ... View more

I get a different error.   Please show us all of the log for this program ... not just the error messages. ... View more

percentage = (A - B) / B = A/B -1 But the division by zero give the infini. I belive that the good answer will be zero How to solve that issue   The answer really depends on what you are going to do with the percentage numbers after you compute percentage. Please tell us.   I don't see how zero is a better answer than the missing you will get when B=0, but maybe there are situations where zero is the best answer. PLEASE EXPLAIN. ... View more

For what its worth, PROC UNIVARIATE produces the same chart. I think that with just 4 data points, the quartile limits are not going to behave in any type of intuitive way. And I don't think your statement "With only 4 values, I would expect the median would divide the box evenly" is a correct statement.   Anyway, the PROC UNIVARIATE documentation explains exactly how the percentiles are computed. https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/procstat/procstat_univariate_details14.htm   I'm guessing your real data has a lot more than 4 data points. Am I correct? If so, does the boxplot on the real data look more intuitively correct? ... View more

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