You cannot use in-line data inside a macro.  Once the macro is compiled into the word token the concept of a LINE of data is gone.   But you don't need the datalines, you need the dataset.  So generate the data some other way. data _xtemp; do endrange =-100 ,-75 ,-50 ,-30 ,-20 ,-10 ,0 ,10 ,20 ,30 ,40 ,50 ,60 ,80 ,100 ,125 ,150 ,200 ,250 ,300 ,350 ,400 ,500 ,600 ; output; end; run; You could also use the TO and BY keywords to save some typing. data _xtemp; do endrange=-100,-75,-50 ,-30 to 60 by 10 ,80,100,125 ,150 to 400 by 50 ,500,600 ; output; end; run; ... View more

@karanfil wrote:   Thanks for the response. I would like to have the following data sets after merging. And run a paired T-test. (like between BSIZEP and DBSIZE) Data A has a YEARP observation during 2018-2019, and data B has a Year 2020-2021 observation.  I really appreciate the help.     DATA A AND DATA B MERGED       TICKER YEARP BSIZEP TICKER YEAR  DBSIZE ACGN 2019 8 ACGN 2020 7 . . . ACGN 2021 7 . . . ACMR 2021 5 ACRS 2019 8 ACRS 2020 9 ADAP 2018 10 ADAP 2020 9   That result does not make much sense.  How can you have two variables with the same name? Why did you eliminate the value of BSIZEP from one of the observations?   Did you mean you wanted this: If so then just just merge by TICKER. data want; merge a b ; by ticker; run; Note that both datasets will need to be sorted by TICKER before you can use the MERGE statement.   You can use PROC TTEST to run a paired t-test. proc ttest data=want; paired BSIZEP*DBSIZE; run; But note that will use only four of the observations since one of them does not have the BSIZEP value.  And t-test is is not the right statistic for that dataset since the same TICKER value can have multiple observations. And those observations all have the same value of BSIZEP. ... View more

Have the user tell the macro where to put the value. Say you make a macro like this: %macro MACRO_WITH_RETURN_VALUE (mvar=return_value /* Name of macro variable to store result */ ); %if not %symexist(&mvar) %then %global &mvar; %let &mvar=Value returned ; %mend; Now the user can call it like this: %* Create the macro variable ; %LET RETURN_VALUE =; %* Run the macro ; %MACRO_WITH_RETURN_VALUE(mvar=return_value) %* See what the result was ; %put &=return_value; ... View more

Looks like it is probably related to this issue with SAS Statistical Graphics settings. https://support.sas.com/kb/67/210.html   Either turn off Stat Graphics or fix the paths used by it. ... View more

You need to explain WHY that code works. ... View more

@dylanleong78 wrote: thanks a lot for this! sorry it took me awhile to respond. i wanted to make sure applying this logic in my full implementation works. Note that there is a lot of simplification in the code I posted.  When using UNTIL() there is no need for an extra test to insure the DO loop executes at least once. You can add an UNTIL() (or a WHILE()) clause to a normal iterative DO loop. So there is no need to increment your loop counter on your own. You can use CAT... series of functions to simplify building strings from other strings and even numbers.  And a comment on comments.  If you place the comments that explain the code BEFORE the code instead of after it then it is much easier to understand the code.  Plus it will keep you from making lines that are too long for humans to read.  With long lines in addition to scanning down the page you have to keep sweeping the field of focus left and right.   ... View more

@dylanleong78 wrote: thanks. i tried putting short_code=strip(upcase(substr(nam_1_s,1,2))); but it did not work. then i placed the strip in in_prev=index(last_tmp_cd, short_code); and that worked! The reason that putting the STRIP() function call in an ASSIGNMENT statement did not help is because the trailing spaces were added back when the value was stored into the fixed length character variable. ... View more

Read the documentation on the FIND() function, in particular look at the various modifiers that it offers.   Your first example does not work because of the lengths of your character variables.  Since you did not tell SAS explicitly what length to use for them it followed its internal rules for guessing what length to use.  So STRING is defined as $17 since the first value you assigned to it was 17 bytes long. And CHAR_SUBSTRING was defined as $12 since the default width for the BEST format is 12.  So that means FIND() was unable to located a 3 followed by 4 zeros and 7 spaces in "40000,80000,30000".   Here are some things you could try: Use the TRIM(), STRIP() or even CATS() function to removing leading/trailing spaces. Use the T modifier in the FIND() function call.   Note: Since you seem to be searching for words you might want to use the FINDW() function instead.   ... View more

So others know when they are at risk can you clarify what is the length that causes trouble?  For example is it names longer than 200 bytes?  Or some other limit? Is it the length of the fully qualified filename?  Or just the name of file itself?  That is could you not rename the file but just move it to a higher directory so that the total name is shorter. ... View more

You appear to be capturing the return code from the function calls rc = metadata_getattr(loginUri, "UserID", userIdValue); , but you are not testing the return code to check if the function succeeded before checking the value of the data set variable. if lowcase(userIdValue) = lowcase("&user_id") then do; Perhaps the call is failing and this is the cause of the false hits?   ... View more

Talk to Microsoft about changing the behavior of Windows? ... View more

If you have one observation per VISIT your SQL should work.    Otherwise if you have unique visit ID you could count the number of distinct visits where the condition is true by nesting a CASE clause inside the aggregate function. count(distinct case when cause_any_inj then visitid else null end ) as cause_inj_cnt   And using just BY group processing in a data step will not remove any observations, unless you have a DELETE statement, or a subsetting IF statement, or a conditional OUTPUT statement.   Can you share a simple example dataset (does not need to be the real data) and the expected result for that input. ... View more