Hi,   Thanks for posting the log. When posting, there are icons above the text box, you can select the icon as below when posting the log:       You don't need the parenthesis around the value when calling the macro. Change the line of code from:   pstn = &pstn_value;   so that it has double quotes around the argument as it contains an alphanumeric value:   pstn = "&pstn_value";     Thanks & kind regards, Amir. ... View more

Hi,   Please post the full log using the Insert Code icon "</>".   Also your invocation looks like it has an extra "(":   %create_ipay_pct9(ipay_pct9&year.&month, ipay_pct9_2&year.&month, (PCT.2);     Thanks & kind regards, Amir. ... View more

Hi,   Please share the code you have tried using the "Insert SAS Code" icon, and also share the log using the "Insert Code" icon ("</>").   I tried the following which appeared to work:   71 %macro test(arg); 72 %put The argument was &arg; 73 %mend test; 74 75 %test(PST.2); The argument was PST.2     Thanks & kind regards, Amir. ... View more

Hi,   You can try using the ALTLOG System Option; from the documentation:    Specifies a location to write a copy of the SAS log. Valid in: Configuration file, SAS command, SASV9_OPTIONS environment variable Category: Environment Control: Files PROC OPTIONS GROUP= ENVFILES, LOGCONTROL Default: None Note: This option cannot be restricted by a site administrator. For more information, see Restricted Options.       Thanks & kind regards, Amir. ... View more

Hi,   Also, try using a different output file name and see if it appears in the same file location. If it doesn't then there might be a mix up with the location you're looking at.     Thanks & kind regards, Amir.   Edit: Typo. ... View more

Hi,   Thanks for sharing the code and listing what you have tried.   I know you said no error messages appear in the log, but please also post the log as there might be other clues in it.   Does the modified date of the output file match the time you ran the proc export?     Thanks & kind regards, Amir.   Edit: Grammar. ... View more

Hi,   Please provide more context as to what is happening, by "failing to open" do you mean some csv file records are not appearing in an output data set?   As well as what has already been said, what code have you used and what does your log show? Please use the "Insert SAS Code" and "Insert Code" icons, respectively.   Also how many records were you expecting and how many did you get?   If appropriate, are you able to provide a small example with data?   Notepad++ can be used to show non-printable characters in files, including end-of-line (EOL) characters, via pulldown menu View > Show Symbol > Show End of Line.     Thanks & kind regards, Amir. ... View more

Hi,   Part of the subject says "I am unable to execute merge...", but the log shows the merge has been executed. Another part of the subject says "SAS is not able to detect data set A and B...", but the log shows data set A and B were detected when they were used in the merge.   Are you happy with the results of the final data set? If yes, then what is your question? If no, then what result did you expect to get instead - please supply a data step with datalines showing the output you expect.     Thanks & kind regards, Amir. ... View more

Hi,   I'm not sure if your subject line has been truncated; was there more to it?   Please provide a data step with datalines to show what output data set you are expecting, along with a brief explanation of the logic rules that generate your output.     Thanks & kind regards, Amir. ... View more

Hi,   Are you looking for something like the following? If not please clarify what should be different.   /* sort in required order */ proc sort data = have out = have_sorted; by id year result dt; run; /* obtain last record per id & year */ data want; set have_sorted; by id year result dt; if last.year; run;     Thanks & kind regards, Amir. ... View more

Hi,   Please share what you have tried, if you have code to share then post it using the "Insert SAS Code" icon (running man), and please post your log using the "Insert Code" icon ("</>").     Thanks & kind regards, Amir. ... View more

Hi,   A few questions so that more information is shared:   How much space are you expecting the output table to occupy and is this based on the input table? How long is the process taking and how long were you expecting it to take? Have you run this before without time and space issues? Please share the log by using the Insert Code icon "</>".   I have in the past worked at a site where compress = yes was the default system option, and based upon the log, the size would not necessarily always be reduced. So, perhaps try without the compress = yes option. You can test out various settings with a smaller amount of observations by using the obs= data set option, to reduce your testing time.     Thanks & kind regards, Amir. ... View more

Hi,   Have you tried the options in the SAS page Suppressing Information to the SAS Log ?    Alternatively, proc printto can be used to redirect the log to an external file.     Thanks & kind regards, Amir. ... View more

Hi,   Part of the title of your post says "confusing that both are true". By "true" do you mean "equal"? Do you think they should be different? If yes, what do you think the difference should be and why? Basically, what is the confusion?   You might already be aware, but in case you are not, the do until condition is only checked to see if the loop should be repeated after the code in the loop is executed. Whereas the do while condition is checked before the code in the loop to see if any looping is required.   If you tried running the code as advised by others and still cannot understand your results, then try using a debugger if you have one.     Thanks & kind regards, Amir. ... View more

Hi   If this is still an issue, then as well as what @Tom has said (which I think is the most likely cause), please share the log by using the Insert Code icon "</>" as there might be other clues as to why it "all of sudden no longer work".   Also, if you haven't already, check to see if the library has allocated successfully. The message you have reported might have always been in your log when you previously ran the code.   Lastly, in answer to your question "What does this mean?": a quoted string immediately followed by an identifier can give the string a special meaning, e.g., '09may2025'd is a way of specifying a date value, by using "d" immediately after the quoted date text. So SAS is displaying this note (not error or warning) message to inform you of potential future SAS changes that might cause the quoted string to have new meaning, based on the identifier that immediately follows it. Hence the recommendation of using a space after the closing quote.   HTH.     Thanks & kind regards, Amir. ... View more