@Tom, thanks for the tip on PROC SCAPROC. Sounds very interesting. ... View more

Thanks @SASKiwi, this was it! Thanks for the explanation of the two options. ... View more

Thanks @SASKiwi , this sees to have solved it. I used ODS listing close; instead of ODS listing off;. ... View more

Here is a snippet from the program and corresponding log where the error happens: proc sql; create table something as select a.stuff from work.location as a ;quit; /**===================================**/ /** Print reports to excel **/ /**===================================**/ %let run_date = %sysfunc(today(), yymmdd10.); %put &run_date.; options nonotes nosource; filename out "/location/of/excel/file/excel.xlsx"; ods results off; ods excel close; ods excel file=out style=excel options( ....   NOTE: PROCEDURE SQL used (Total process time): real time 0.06 seconds user cpu time 0.06 seconds system cpu time 0.04 seconds memory 18609.67k OS Memory 47840.00k Timestamp 10/31/2019 10:43:21 AM Step Count 61 Switch Count 0 Page Faults 0 Page Reclaims 4000 Page Swaps 0 Voluntary Context Switches 466 Involuntary Context Switches 38 Block Input Operations 0 Block Output Operations 384 2019-10-31 ERROR: Insufficient authorization to access /location/not/referenced/in/program/work_flow_name.lst. ==> User code completed. The error happens right after the put statement for &run_date. The excel file gets created, just no data in it. The program runs fine for me in Enterprise Guide. ... View more

Thanks @SASKiwi . The prevailing thought is if the account doesn't have access then the SAS program shouldn't be writing to the location. To clarify, the location that is in the error message is not a location I am explicitly trying to write to in my program. The location of the ODS destination doesn't seem to be a problem. Despite the error the program does create the excel file, but with no data.   I ran into a very similar issue once when my code had a "PROC SQL" step to create a macro variable. I had to add a "NOPRINT" to the step for it to work. Without the "NOPRINT" the program seemed to want to write the value of the macro variable to the location for which the program does not have access. It seems to me that the ODS statement is attempting to write something behind the scenes, giving me the error. Just my guess. If so, then if could there be a way to suppress this output? ... View more

@Tom, thanks for the assist. Indeed I did not submit a valid SAS code. ... View more

Thanks @FriedEgg. In fact the Jupyter notebook and the SAS Grid are not on the same machine. So this was another problem. Both your solutions worked. ... View more