Another Question for n?

[ybz12003]

Hello:

I have the following codes.   I found out the proc content didn't work when I remove the n behind the "18RSV".   Could someone let me know why?  Thanks.

LIBNAME RSV OLEDB 
		provider="sqloledb" 
		properties=("Data Source"="SQL\2018"
					"Persist Security Info"="True" 
					"User ID"="test" 
					"Password"="&pin" 
					"Initial Catalog"="RSV")
		schema=dbo;

PROC CONTENTS DATA=RSV."18RSV"n OUT=RSV18 NOPRINT;RUN;

[novinosrin]

The section 

SAS Name Literals

Definition of SAS Name Literals in the following link may help

https://support.sas.com/documentation/cdl/en/lrcon/62955/HTML/default/viewer.htm#a000998953.htm

[Reeza]

Because otherwise SAS reads that as a string not as a data set name. The letters after denote different things. An n means a name literal, a d means a date, dt means datetime, and t means time. The data set is not a valid name because it starts with a number.

[RW9 · Accepted solution]

The n means the string is a named literal.  It is used for strings which are not SAS compatible, often used with sources like Excel which have no rules.  In your given example dataset names cannot start with a number, so you need to use named literal.  This:

OUT=18RSV

Will not work, should give you an error as name cannot star with number.  Also avoid coding all in uppercase, its really hard to read. 

[ybz12003]

The code wasn't created by me, but someone else.  I am trying to figure out why he wrote this.   So from your feedback, the n is used because the dataset "18RSV" starting with number? 

[mkeintz]

Yes.

If your data source wants, he could prefix the name with an underscore, which might preserve the naming properties he/she wants while allowing you to dispense with the N and the quotes.

[SuryaKiran]

For any of the SAS names that are not valid have to be in this way(string within quotation marks, followed by the upper- or lowercase letter n). 

[ybz12003]

Thank you so much for all of your input.