Log with source2 option looks fine for me, see below, but still no success. %includes normally work fine, it only happens with PROC SQL Joins (at least thats my impression so far). I just tried to replace the "=" by "eq" within the PROC SQL step, but without success. I could replicate the problem on another computer. Can you replicate it as well or does it work for you? 5597 5598 options source2; 5599 5600 DATA table; 5601 INPUT KEY $ JUST_SOMETHING; 5602 CARDS ; NOTE: The data set WORK.TABLE has 7 observations and 2 variables. NOTE: Compressing data set WORK.TABLE increased size by 100.00 percent. Compressed is 2 pages; un-compressed would require 1 pages. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.01 seconds 5610 RUN; 5611 5612 %include "G:\temp\TEST.SAS"; NOTE: %INCLUDE (level 1) file G:\temp\TEST.SAS is file G:\temp\TEST.SAS. 5613 + 5614 +DATA joinTable; 5615 + INPUT KEY $ COL; 5616 + CARDS ; NOTE: The data set WORK.JOINTABLE has 58 observations and 2 variables. NOTE: Compressing data set WORK.JOINTABLE increased size by 100.00 percent. Compressed is 2 pages; un-compressed would require 1 pages. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.01 seconds 5675 +RUN; 5676 + 5677 +PROC SQL; 5678 + CREATE Table resultTable as 5679 + SELECT tab.*, joi.COL FROM table as tab 5680 + LEFT JOIN joinTable as joi 5681 + ON tab.KEY = joi.KEY; NOTE: Compressing data set WORK.RESULTTABLE increased size by 100.00 percent. Compressed is 2 pages; un-compressed would require 1 pages. NOTE: Table WORK.RESULTTABLE created, with 7 rows and 3 columns. 5682 +QUIT; NOTE: PROCEDURE SQL used (Total process time): real time 0.01 seconds cpu time 0.01 seconds NOTE: %INCLUDE (level 1) ending.
... View more