Did you submit the SAS commands in libname.sas in the EPG1V2 folder??   What are the commands in libname.sas? ... View more

Most of us (including me) will not download attachments of Microsoft Office documents as they are security threats. And furthermore, I will not download any document attachments.   Whatever you want us to see in the MS Word document, paste it into your message as text (or if it is a graphic, paste it into your message as a graphic).   Also, please run this command   options mprint;   and then run your code again, and see if you can figure out what is wrong by checking the log. If you're still stuck, show us the ENTIRE log (down to and including the first ERROR message) for this macro by clicking on the </> icon and pasting the log as text into the window that appears. DO NOT SKIP THIS STEP. ... View more

I don't know what is okay, that isn't clear. However, it is not okay, in my opinion, to ask questions about how to use macro variables in this thread, they belong in their own thread, and people (including me) will be happy to help. ... View more

%IF cannot access values of a data step variable such as response.   Maybe like this:   /* UNTESTED CODE */ %let response = %sysfunc(libref(data)); %put &=response; %if &response ne 0 %then %do; %PUT Creating the libname data; options dlcreatedir; LIBNAME data "&path1/data"; %end;   Which brings up the question ... why bother testing? If DATA is a currently assigned libname, or if it NOT a currently assigned libname, the LIBNAME statement should execute without problems. No conditional branching is needed here.   Is this related to your earlier thread? If so, the problem I think you are having is that you never identified the cause of this error. And so that will continue to be a problem until you identify the cause and fix it. Marking the answer correct doesn't mean you have found the cause. ... View more

I would be happy to discuss these macro questions in their own thread. I will not discuss them in this thread, as they have deviated far from the topic of "Running a program for different populations" ... View more

Is this what you are looking for? https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.3/statug/statug_mixed_examples05.htm ... View more

You don't need to know what LIBNAMEs exist, the command from @Ksharp will clear whichever ones exist. Of course, I consider that command dangerous in the sense that it will clear LIBNAMEs that you do NOT want to clear.   But even that command fails if, as I said earlier, you have an open data set in one of the libraries, then the command will not clear the LIBNAME. So do you find yourself in this situation? Can we see the contents of the %INCLUDE file as I requested?   You can query to find out what LIBNAMEs exist   proc sql noprint; select distinct libname into :libnames separated by ' ' from sashelp.vlibnam; quit; %put &=libnames;    ... View more

@dxiao2017 wrote:  @nsns I have another question for you: why there is a period (or dot) behind your macro variable &pop (,please see the picture, I marked it out with a red circle)? @PaigeMiller , I am not sure whether the %local statement in my second macro write correctly, could you help confirm it? Thanks! Please start a new thread with these questions, as they are not really on topic in this thread. ... View more

Double-ampersands are not necesssary here, unless there are things going on in your code that you haven't mentioned. ... View more

Perhaps you have opened a SAS data set in the DATA library, and it is still open. If so, just close the data set(s) in DATA that are open.   If that's not it, show us the %INCLUDE code ... View more

I feel uneasy recommending code after seeing an obviously contrived program. However, this is the outline of what you would do.     %macro do_this(pop); data a; set b(where=(&pop="Y")); ... run; /* the rest of your code goes here */ %mend; %do_this(ITT) %do_this(PP)   ... View more

Without seeing your program, its nearly impossible to advise.   Is ITT the name of a variable, or is it the value of a variable?   ... View more

@quickbluefish wrote: Yes, I'll just add one bit to what @PaigeMiller said, which is that the only place you'd sensibly use either one and expect to get the same results is if the argument is a string literal as opposed to a variable name. data test; x=%lowcase("Here is a STRING"); y=lowcase("Here is a STRING"); run; But I said you should not  use %LOWCASE with data step variables or data step expressions. Yes, it works the way you said for this particular string, but don't use %LOWCASE here, it is simply a very bad habit to get into, as there are many cases where it will not produce the same answer. ... View more

@dxiao2017 wrote: Base on your answer, my version (for creating dataset with days) is like this (the proc sort and proc report steps and the results are the same). Although I used more steps and statements, I think the logic is easier to understand for new users, especially who is not good at math, do not remember many functions, and not get used to more advanced techniques such as array and nested loops.   I disagree that the logic you used is easier to understand than what @Tom showed. In my work, I see people all the time trying to do something the hard way, they put a huge amount of effort into it (like I assume you did) and they write a lot of code, when this isn't necessary, and there are much easier ways to get the desired output.   And so in this case, @Tom has shown how to get the output with a lot less code. He even gave good advice to people who have this or similar problems, he said "Easier if you make a TALL dataset instead." Also, Tom has not used arrays or nested loops, and he has shown very useful methods (like use TALL data sets and PROC REPORT) that SAS programmers ought to learn early in their career. SAS has done the hard work for you, so you don't have to work hard.   By the way, @dxiao2017 , maybe you were replying to the code from @quickbluefish, but your actual post says you are replying to @Tom . ... View more