BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Obsidian | Level 7

Hii kurt,


If you want full Proc contents output.



Diamond | Level 26

So you show us part of PROC CONTENTS, but not all of it. How do we know this is the same data set LCS_I that you were using in your code? Show us ALL of PROC CONTENTS so we can see what data set the results are for.


Also, as I said, if you run your original code TWICE, you will get that error even if the variable was present originally. Are you running that code twice?????

Paige Miller
Super User

@NiravC wrote:

Hii Kurt,


Thanks for answering, But I tried this thing :

Data LCS_i_new;
set LCS_i;

It's not working.

And I run  the Proc Contents, Both the variable available with same name which is available in my early post.



"Not working" is awful vague.

Are there errors in the log?: Post the code and log in a code box opened with the "<>" to maintain formatting of error messages.

No output? Post any log in a code box.

Unexpected output? Provide input data in the form of data step code pasted into a code box, the actual results and the expected results. Instructions here: will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the "<>" icon or attached as text to show exactly what you have and that we can test code against.




Available on demand!

Missed SAS Innovate Las Vegas? Watch all the action for free! View the keynotes, general sessions and 22 breakouts on demand.


Register now!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 17 replies
  • 4 in conversation