You topic sentence said you have a character variable.   Your code is assuming RIGHT_HOURS is character because it is comparing the value to character strings.   If that is not your question the please restate it.   Also pay close attention to the NOTEs that the SAS data step will generate when it has to convert numbers to character strings or the reverse.   Not sure what you mean by "decimal".  SAS datasets only store two types of variables. Fixed length character strings and binary floating point numbers. ... View more

See if it is possible to save the two version as separate files and compare them using some other tool to see if in fact there are differences in those lines. ... View more

Copy and paste from where?   One annoying thing that SAS introduced with the "Enhanced" editor is that it preserves trailing spaces on the ends of lines.  The old editor they had in Display Manager was better suited for code editing.   PS  Don't place physical tab characters inside of program files.  The bytes saved are not worth it.  And ironically they make aligning the text harder.  It you do want to include them then make sure they only appear at the beginning of the lines. ... View more

Assuming it is not a bug in EG then I suspect in those cases there are white space differences between the two versions.  Perhaps one version had trailing spaces removed.  Perhaps one version used CR+LF and the other just used LF as the end of line marker.   I have not used this EG feature, but based on other difference displays I have used check if EG has an option to ignore white space differences. ... View more

No need to "convert" it.  Just change its name.  SAS/Studio has a RENAME option.   For some reason SAS/Studio makes a big deal of the extension used on the filename.  Not sure why. ... View more

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