topic How to avoid an epg jungle? in SAS Enterprise Guide

How to avoid an epg jungle?

Gregor — Thu, 27 Feb 2014 14:20:34 GMT

I have a structured suite of sas codelet in my EPG work flow. Each of them consists of many data steps and proc sqls. The execution of each of these steps gives me all the results up to 50 tables for each codelet. I would like sas to calculate the tables without showing the calculated tables. Is that possible? Maybe a trivial option? Wasn't able to google any solution.

Thanks

Gregor

Re: How to avoid an epg jungle?

railfan1975 — Thu, 27 Feb 2014 18:35:06 GMT

Hey Gregor,

I have the same issue and find it very irritating. I've found three ways to deal with the jungle. They all have their pluses and minuses.

1) In EG 5.1, if you go to File->Project Properties->Output Data Sets and change the Maximum Number of output data sets to 0 then EG will not show them after the run. You can also change this setting by going to Tools->Options->Results General. Unfortunately, EG will still put a note after the codelet runs that "indicates that the data set limit was reached and specifies the total number of output data sets that were created". Better than the jungle, but still annoying.

2) Use PROC DATASETS; Delete; to delete any datasets that you do not need after the code has run.

3) Clear the library name in which the datasets are stored as mentioned here: http://stackoverflow.com/questions/10979058/how-can-i-stop-tables-appearing-in-enterprise-guide

I hope this helps!

Jonathan

Re: How to avoid an epg jungle?

f_rederik — Sat, 01 Mar 2014 16:41:05 GMT

Hey Gregor

Have you tried the 'NO PRINT' option?

Cheers

Fred

Re: How to avoid an epg jungle?

Gregor — Mon, 03 Mar 2014 07:33:28 GMT

Hi Fred,

thanks, but how is the syntax in order to achieve the change?

SAS accepts the statements to be like that

proc sql noprint;

create table lib.file as

.....

but the created tables are still in the output.

Best,

Gregor

Re: How to avoid an epg jungle?

f_rederik — Mon, 03 Mar 2014 08:09:09 GMT

Sorry Gregor I was a bit quick off the mark there.

Cannot get this to work for neither DATA or PROC SQL the way I thought it would..