BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
Desi2003
Calcite | Level 5
DATA Phy_Act1;
	SET	CoImpt.PhysicalActivity;
	RENAME	CT	= TRACT_NAME;
	RUN;

Above is code from a project. When I run this code, here is my log:

 

 80         %LET CourseRoot = /home/u63571562/BIOS6680_2023;
 81         LIBNAME CoImpt "&CourseRoot/CDPHE Study/Data/2_Import";
 NOTE: Libref COIMPT refers to the same physical library as _TEMP3.
 NOTE: Libref COIMPT was successfully assigned as follows: 
       Engine:        V9 
       Physical Name: /home/u63571562/BIOS6680_2023/CDPHE Study/Data/2_Import
 82         LIBNAME CoAnl "&CourseRoot/CDPHE Study/Data/4_Analysis";
 NOTE: Libref COANL was successfully assigned as follows: 
       Engine:        V9 
       Physical Name: /home/u63571562/BIOS6680_2023/CDPHE Study/Data/4_Analysis
 83         
 84         *Rename CT in physical activity to tract_name*;
 85         DATA Phy_Act1;
 86         SETCoImpt.PhysicalActivity;
 87         RENAMECT= TRACT_NAME;
 88         RUN;
 
 WARNING: The variable CT in the DROP, KEEP, or RENAME list has never been referenced.
 NOTE: There were 1249 observations read from the data set COIMPT.PHYSICALACTIVITY.
 NOTE: The data set WORK.PHY_ACT1 has 1249 observations and 6 variables.
 NOTE: DATA statement used (Total process time):
       real time           0.00 seconds
       user cpu time       0.00 seconds
       system cpu time     0.00 seconds
       memory              1198.81k
       OS Memory           26200.00k
       Timestamp           11/08/2023 06:14:15 PM
       Step Count                        413  Switch Count  2
       Page Faults                       0
       Page Reclaims                     154
       Page Swaps                        0
       Voluntary Context Switches        12
       Involuntary Context Switches      0
       Block Input Operations            0
       Block Output Operations           520
       
 
 89         
 90         OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 100        

Why I am I getting this error when it seems to be working fine, and how do I get rid of it?

1 ACCEPTED SOLUTION
1 REPLY 1

Ready to join fellow brilliant minds for the SAS Hackathon?

Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.

Register today!
Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 439 views
  • 0 likes
  • 2 in conversation