Not technically correct you can reference a file with the full path.   data want; set '/home/fkhurshed/Demo1/class.sas7bdat'; run; @GN0001 wrote: Hello, Actually the data exists in SAS but without libname, I can't read from that dataset. Regards, Blue Blue   ... View more

This response saved me. Thanks 🙏 Blue blue ... View more

@GN0001 wrote: Hello, What do we need to do when we see this message in the log: Sometimes but not always you may see a note about "some text is longer than XXX characters you may have unbalanced quotes" but not always.? I can't say all but majority of the posts I made here the other day were all resolved once I started a new SAS session and editor. Regards, Blue Blue SAS is an interpreted language.   Unlike C or FORTRAN you don't compile your program into an executable and then run it.  Instead you run SAS itself and it then interprets and executes the code you give it.  Until you exit from SAS.   Your issue here was you submitted code with unbalanced quotes.  So SAS is still waiting for your to finish that string (and then finish the statement it was in and the procedure that the statement was in )  before it starts trying to run your code.   By closing Enterprise Guide you shut down the SAS session that it was using to run your SAS code.  The same if someone that was using SAS directly had exited SAS.  Then when you start a new Enterprise Guide session it started a new SAS session. Since it is a new session it knows nothing about the unbalanced quotes (or any of the code) you used in the previous session.   You should not have to close Enterprise Guide itself to get a new SAS session.  There should be a menu item in the Enterprise Guide menus to allow you to restart your SAS session without leaving Enterprise Guide, and probably without closing the project you are currently working on it Enterprise Guide.  SAS/Studio (which is another way to use and external interface to edit and submit code to run in SAS) has a way to restart the session. ... View more

@GN0001 wrote: what you explained suffice what I am looking for. Thanks, Blue Blue Great, but what is the goal? What are you trying to do with a macro variable here? Why did you put a CALL SYMPUT at the end of that data step? ... View more

@GN0001 wrote: SASKiwi, Does this take care of stacking data on top of each other? Does this return all duplicated observations? Regards, Blue Blue It stacks all of the data including duplicate observations. ... View more

Hi: My paper https://support.sas.com/resources/papers/proceedings13/120-2013.pdf (page 10-11 Figure 18) has an example of indirect reference and we cover the topic in our Macro Language 1 class. Cynthia ... View more

@GN0001 wrote: Hello team, I have this code from SAS support white paper. I can send it to you if you want. The original code has used this select " ' " || diagcode || " ' ". It gave errors with a red line under ||, that is why I changed it to &. Regards, Blue Blue If  a paper used syntax and that syntax generates an error then you should run the syntax as originally written and if you get an error copy the text from the LOG with code and errors and all messages for the data or proc step and paste the copied text into a text box opened on the forum with the </> icon.   Pretty much guarantee that if you randomly attempt to use other language syntax that it will fail OR do something that you do not expect. & is either a logical operator for 'and' or part of a macro variable reference in general with SAS code. ... View more