topic Re: SAS EG - results lost after a run error in SAS Enterprise Guide

SAS EG - results lost after a run error

lai302120 — Wed, 01 Jun 2016 22:03:04 GMT

Hi,

i'm a new user to SAS EG but i've been using SAS Foundation for a few years now.

My issue:

I open and run sections of sas code in EG, but i find that whenever i run a section of code and get stopped due to errors, the results (i.e. macro variables created, libraries, temp datasets) from the previous sections of code i ran are all lost after and I need to rerun everything again.

am i using EG 'wrong'? i've never experienced something like this when i use SAS Foundation.

thanks

Re: SAS EG - results lost after a run error

SASKiwi — Thu, 02 Jun 2016 05:10:33 GMT

Submit in EG: proc options; run; and check in the log to see if the ERRORABEND SAS option is set. This may well explain the behaviour you are seeing - your session dropping if there is a SAS error. This option is not usually used for interactive SAS but it may be a default setting you are picking up from your SAS server.

Re: SAS EG - results lost after a run error

ChrisHemedinger — Thu, 02 Jun 2016 12:11:29 GMT

SAS Enterprise Guide works differently than SAS Foundation (Base SAS windowing environment). When you run a program/task, the log/output/results of that task are replaced in your process flow, not accumulated. Data sets and other files are not actually deleted (unless the code you run directs that to happen), but EG brings you back just the results of your latest "run". If you have an error in the program, then you might not see any results.

If you want to see the log output accumulate, turn on the Project Log feature (View->Project Log). That will keep track of all of the SAS logs for each iteration of code you run.

Your data sets are always available in their respective libraries -- look at the Server List, navigate to the libraries you want, and add the data you want to track to your project.

Unlike Base SAS, SAS Enterprise Guide doesn't offer a good method for interactive procedures: the line-by-line submission of code for certain PROCs like PROC REG or IML or GLM -- those procedures that stay "open" until you submit a QUIT statement. If you need that method of working in a client interface, SAS Studio (a web based programming interface for SAS) does offer a special interactive mode (but it's also not the default way of working).