topic NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release in SAS Enterprise Guide

NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release

Harish2 — Wed, 07 Jun 2017 04:12:51 GMT

Hi team,

I am facing an issue in SAS EG like as mentioned in the subject line. I am posting again in the below.

NOTE 49-169: 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.

Please help me to resolve this issue asap.

Thanks for your help.

Harish

Re: NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS rel

kiranv_ — Wed, 07 Jun 2017 04:22:39 GMT

if you can show the code or give some more info then someone will help you. This is a very common error and reason for the same is discussed in below link

https://communities.sas.com/t5/Base-SAS-Programming/quot-NOTE-49-169-The-meaning-of-an-identifier-after-a-quoted/td-p/121796

Re: NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS rel

Kurt_Bremser — Wed, 07 Jun 2017 07:12:11 GMT

Since strings like

'01jan1960'd
'08:30't
'01jan1960:08:30'dt
'0d0a'x

have special meaning (date, time, datetime, hex-code literals), SAS alerts you that a string immediately followed by other non-blank characters might also get some special meaning in the future (like '664'o), and could pose a danger. Closing quotes should therefore be followed by blank space.