Thanks everyone who responded. I wasn't able to reproduce the issue using the suggestions provided. My best guess is it was a one off resulting from weekend maintenance on SAS, Teradata or somewhere else. I've got into the habit of using the macro below when writing new code or where I can easily include it with code updates. I think I got it from a paper on lexjansen.com so thanks to the author. It first checks whether a table or file exists, and only drops it, if it does exist. This avoids generating unnecessary warning messages and presumably would have avoided the error message in my original post. You can use this as accept as solution. I don't seem to be able to do this for my own posts. /* Drop table macro to avoid warning message if table does not exist. Warning message will cause autosys run to fail */ %macro checkDrop(tmpData); %if %SYSFUNC(exist(&tmpData)) %then %do; proc sql; drop table &tmpData; quit; %end; %mend checkDrop; %checkDrop(mydb.mytable)
... View more