libname problem: "The meaning of an identifier after a quoted string..."

[dk333]

Help! The libename statements in all of the programs that I have used previously (and that worked) all of sudden no longer work.  I have not changed SAS versions, or any directories. I have not changed the liberef to a new name and the semicolons are still present.  In the log, I get the following message, "The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended." What does this mean?  Why is this happening now? What can I do to fix it? Thank you. 

[Tom]

The most likely situation is SAS is still trying to find matches for previous quotes you submitted.

There is some "magic" series of comments with embedded quotes you can type submitting to close the unbalanced quotes.

But I find the quickest fix is to start a new SAS session.  If you are running SAS directly just end your session and open a new one.  If you are using SAS/Studio or Enterprise Guide you probably leave those running and just ask them to re-connect to the SAS server so you get a new session.

Then be careful about code you submit to make sure the quotes are balanced.

[Amir]

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.

[mharding]

Hi,

It does appear to be a quoting or macro quoting issue, however given it is happening in ALL your programs it would appear that something has changed in your SAS Environment.  If you are using SAS EG, did you or someone add custom code in SAS Enterprise Guide inserted before code submission?  Perhaps an autoexec program has changed, but this would generally impact only the first program.  What SAS Environment are you using?

Did you change from a windows environment to a UNIX environment and some unusual characters where inserted when moving to the different O/S?

By the way use this code to correct possible unbalanced quotes  '*;"*;run;

Note: It may not correct all macro quoting issues, which would need a SAS reset.

Mary