topic Re: PROC DATASET WARNING: No output destinations active in SAS Programming

PROC DATASET WARNING: No output destinations active

SASAna — Fri, 10 Feb 2017 16:28:32 GMT

Hi SAS Team,

I am getting "WARNING: No output destinations active" for PROC DATASET DELETE.

I tried nowarn & nolist options but still getting the error.

proc datasets nowarn;
delete output_process;
run;

Any help would be appreciated.

Thanks,

Ana

Re: PROC DATASET WARNING: No output destinations active

Tom — Fri, 10 Feb 2017 16:32:37 GMT

Not sure how to prevent the warning in general. But if you are just deleting dataset then use PROC DELETE. They tried to hide it for awhile but it is back now with added functionality.

proc delete data=output_process;
run;

Re: PROC DATASET WARNING: No output destinations active

ballardw — Fri, 10 Feb 2017 16:47:53 GMT

You likely ran some code with either:

ODS _all_ close;

ODS HTML Close; with no other ODS destinations active.

Try

ODS HTML;

add a PATH="operating system path" to control where your html output goes.

Re: PROC DATASET WARNING: No output destinations active

Astounding — Fri, 10 Feb 2017 16:54:47 GMT

PROC DATASETS will require that you supply the location of the data set. This could be done in your program by adding to the PROC statement:

library=work

If you were to switch methods, as Tom suggested, you would then be supplying a data set name using DATA=. In that case, single level data set names are assumed to be in the work folder.

Re: PROC DATASET WARNING: No output destinations active

SASAna — Fri, 10 Feb 2017 19:57:04 GMT

Hi,

One thing i want to mention is - Output_process dataset is being used in different SAS program's macro & referenced it as Global variable , as this program goes in loop. I am clearing out the older data by proc dataset delete .

Toms suggestion of PROC DELETE did not work for me.

Thanks,

Ana

Re: PROC DATASET WARNING: No output destinations active

Astounding — Fri, 10 Feb 2017 20:29:17 GMT

%GLOBAL operates within the context of a single program. There is no way to make a macro variable available across programs.

That being said, there is a process that applies to interacting platforms, %SYSLPUT but it is not applicable to the majority of cases where multiple programs run.