topic Re: Export SAS log to external files in SAS Enterprise Guide

Export SAS log to external files

Qing_End — Thu, 28 Jul 2016 15:06:22 GMT

Hi, All.

My working environment transfered from SAS Base to SAS EG in last week. In my working environment, we need to export LOG and analysis log and get a overall summary. In SAS Base environment, I use following statement to export log file.

DM "log;file filename;"

But in EG, the DM command is not supported.

Does anyonce know any statement or functions in EG equal to above statement?

Proc printto statement not work in my situation as the proc printto does not export log already exists .

Thank you.

Re: Export SAS log to external files

RW9 — Thu, 28 Jul 2016 15:14:21 GMT

Sorry, why does:

proc printto log="c:\alogfile.txt";

run;

Not work? Just need to specify the filename, and put that before code you need to run, per:

http://support.sas.com/documentation/cdl/en/basess/58133/HTML/default/viewer.htm#a001330273.htm

Re: Export SAS log to external files

gravity2726 — Thu, 28 Jul 2016 20:13:21 GMT

Click on the Log Tab(Next to Program) , Under Log you see the options export , Sent to ...............Click on export ---> Export as ....Then you save the file to desired destination

Re: Export SAS log to external files

Qing_End — Fri, 29 Jul 2016 00:45:59 GMT

The situation is that I can't just simply put the proc printto code before SAS code.

I need another way to put log which exsist before my code to external file.

Thanks.

Re: Export SAS log to external files

Qing_End — Fri, 29 Jul 2016 00:56:11 GMT

Yeah, this is actually a way. But in this way I have to click this button every time, It is time-consuming.

Re: Export SAS log to external files

RW9 — Fri, 29 Jul 2016 08:10:55 GMT

Sorry, your process isn't clear. You can't run code? Do the files already exist then? If so you would need some sort of OS scripting to copy them across. What is the clear and concise process you are doing, indicate at what point you need to redirect the log (if indeed redirecting the log is what we are talking about). Can't remember about EG setup, but SAS has autoexec. You could also create a run_all program separate from what you have, e.g.:
%inc (file=);

proc printto log="&file..txt";

run;

%inc "&file..sas";

proc printto;

run;

%mend inc;

%inc "c:\file1";

%inc "c:\file2";

Re: Export SAS log to external files

Qing_End — Fri, 29 Jul 2016 08:18:18 GMT

Thanks man. What I need is to redirect the log file after I run my program. but I can't add proc printto to statement before my program. The real picture is that I need to check my log after my run my program. This can be easily achieved in SAS BASE through DM command. But I don't find any sort of ways in EG.

Re: Export SAS log to external files

RW9 — Fri, 29 Jul 2016 09:04:50 GMT

Ok, I thnk I see. You run a program (can't run anything else other than that), then once that is run you want to take a copy of the log. In which case you will need to know where the default log is stored, it should be a text file somewhere (unless EG keeps it in memory). You can also re-direct the log in the autoexec - as EG starts up, to a file you want, then you can copy paste that file as you want and it will not interfere with your other program.

Re: Export SAS log to external files

Qing_End — Fri, 29 Jul 2016 09:49:43 GMT

Yeah, exactly. You gave me some hints. I think I need to find where the temporary log file is, then I can use SAS program to analysis it. Thanks man.

Re: Export SAS log to external files

CaseySmith — Fri, 29 Jul 2016 13:16:19 GMT

EG stores the log files temporarily on disk in the Windows %temp% directory in a path with this format:

%temp%\SEG<uniqueID>\<uniqueID>\result.log

For example:

C:\Users\cassmi\AppData\Local\Temp\SEG65492\dd40c683fece4362b2d3e17463b91689\result.log

You could write a script to copy them from here if redirecting the log in autoexec or via proc printto will not meet your needs.

Note: EG's project log is also stored in the same path format and file name, so you'd probably want your script to differentiate somehow.

Casey

Re: Export SAS log to external files

CaseySmith — Fri, 29 Jul 2016 13:43:10 GMT

Another way you could accomplish is with EG's automation interface. For example, add the following to the EGScript1.vbs file that gets created when you schedule an EG project:

    '-----
    ' export the log for each program
    '-----
    Dim code
    For Each code in prjObject.CodeCollection
        'MsgBox code.Log.Text
        code.Log.SaveAs "c:\temp\" & code.Name & ".log"
    Next

Here is an example of the full VBS file (I commented out the running and saving of the project. Up to you to decide what you want the script to do.):

Option Explicit
Dim app

Call dowork

'shut down the app
If not (app Is Nothing) Then
    app.Quit
    Set app = Nothing
End If


Sub dowork()
    On Error Resume Next
    '----
    ' Start up Enterprise Guide using the project name
    '----
    Dim prjName
    Dim prjObject

    prjName = "C:\Users\cassmi\Desktop\ExportAllLogs.egp"    'Project Name
      
    Set app = CreateObject("SASEGObjectModel.Application.7.1")
    If Checkerror("CreateObject") = True Then
        Exit Sub
    End If
    
    '-----
    ' open the project
    '-----
    Set prjObject = app.Open(prjName,"")
    If Checkerror("app.Open") = True Then
        Exit Sub
    End If
    
        
    '-----
    ' run the project
    '-----
    'prjObject.run
    'If Checkerror("Project.run") = True Then
    '    Exit Sub
    'End If
    
	
    '-----
    ' export the log for each program
    '-----
    Dim code
    For Each code in prjObject.CodeCollection
        'MsgBox code.Log.Text
        code.Log.SaveAs "c:\temp\" & code.Name & ".log"
    Next
            
    '-----
    ' Save the new project
    '-----
    'prjObject.Save
    'If Checkerror("Project.Save") = True Then
    '    Exit Sub
    'End If
    
    '-----
    ' Close the project
    '-----
    prjObject.Close
    If Checkerror("Project.Close") = True Then
        Exit Sub
    End If
       
End Sub

Function Checkerror(fnName)
    Checkerror = False
    
    Dim strmsg
    Dim errNum
    
    If Err.Number <> 0 Then
        strmsg = "Error #" & Hex(Err.Number) & vbCrLf & "In Function " & fnName & vbCrLf & Err.Description
        'MsgBox strmsg  'Uncomment this line if you want to be notified via MessageBox of Errors in the script.
        Checkerror = True
    End If
         
End Function

Re: Export SAS log to external files

Qing_End — Fri, 29 Jul 2016 13:56:08 GMT

Thank you Casey. Through I have limited knowledge in VBS, will try to figure out the code you provided. Thanks

Re: Export SAS log to external files

Tom — Fri, 29 Jul 2016 14:44:04 GMT

I am sorry, but WHY would you want to replicate that process? It is not a process you should normally use in Display Manger anyway.

When you run code in an EG project doesn't it already save the log in the project file? If for some reason you want to see it later perhaps you can just treat the EG project file like the ZIP file that it is and extract the log from there?

Re: Export SAS log to external files

Quentin — Fri, 29 Jul 2016 15:09:52 GMT

Just wanted to say I had this same question/problem about trying to access the log programmitally. Like you, in interactive PC SAS, I used DM commands to save the current log to a file and then post-process it.

Helpful to know that the EG log file is stored in a temp file on the PC. But my guess is this still wouldn't work for my use case. That is, in interactive PC SAS (and batch SAS) I can submit all together:

*data step;
*proc step;
*blah blah blah;
%logPostProcess()

And %LogPostProcess will process the log from steps submitted before it. In EG connected to a remote SAS session, I would assume the code has to complete executing before the log file gets back to the local PC. And as I type I realize even if the log file came back to my local PC in real time, it wouldn't matter, because my %logPostProcess executing on the remote server couldn't read it.

I have ended up using the PROC PRINTTO approach when I want to do log scanning in EG. It's a bid of a hassle, but works okay. You can set up pre-code and post-code to run the PROC PRINTTO before and after every EG submission (or on EG conection to server). So you don't necessarily need to revise the main code. My process is like:

PROC PRINTTO redirects log to a file.
Main code runs.
PROC PRINTTO redirects log back to log window.
Post process log file.
Read the log file and stream in back to log window (so I can see log in EG log window).

That said, I'm only using EG for development work. It was important to me to keep an approach that works for EG and Interactive PC SAS and batch jobs and stored process jobs.

I think this would be easier to manage if it were possible to specify ALTLOG option during a SAS session. So you could just turn ALTLOG on and off any time you want to get a file copy of the log. If you agree, please vote up:

https://communities.sas.com/t5/SASware-Ballot-Ideas/Allow-ALTLOG-to-be-specified-on-OPTIONS-statement/idi-p/219628

--Q.

Re: Export SAS log to external files

Qing_End — Mon, 01 Aug 2016 01:15:49 GMT

Hi Tom. I'd like to replicate the DM statement because I need to check the log after I run my program since the Error and Warning is not enough for me. Some special Note need to be checked, such as Note: Missing valued be generated.

I need to check every log after I run my program, So I want find a more convenient way to do this. Not just Zip and Unzip, It's time consuming.

BTY,In SAS Base environment, I used to do this by using SAS/SCL. Then I can check my log just push some keys.

Thanks.

Re: Export SAS log to external files

Qing_End — Mon, 01 Aug 2016 01:24:01 GMT

Hi, Quentin. Thank you.
I think we met the same issue.
I appreciated the way you provided. I think it's a good solution.
But I am a little confused "You can set up pre-code and post-code to run the PROC PRINTTO before and after every EG submission" as i'm a newbee in SAS EG.

Could you please explain how to achieve this task?

Thank you.

Re: Export SAS log to external files

Quentin — Mon, 01 Aug 2016 12:50:56 GMT

Hi,

Warning: I haven't played with this approach, but I think it should work.

In recent versions of EG (I'm using 6.1) if you go to tools->Options->SAS Program there are options where you can specify

Submit SAS Code when server is connected
Insert custom SAS code before submitted code
Insert custom SAS code after submitted code

You can think of Submit SAS Code when server is connected as similar to an autoexec. When EG starts, it connects to a server, and that code will run automatically. In general, when you submit code in EG, EG adds a bunch of wrapper code to communicate with the server etc. The insert custom SAS code before/after submitted code allows you to specify additional SAS code that should be added to that wrapper. That code would be executed every time you submit code in EG.

So my thought is set Submit SAS Code when server is connected to be:

filename mylog "%sysfunc(pathname(work))/MyLog.log";

Set Insert custom SAS code before submitted code to be:

proc printto log=mylog new;
run;

Set Insert custom SAS code after submitted code to be:

proc printto log=log;
run;

data _null_;
  infile mylog;
  input;
  *log scanning etc;

  putlog _infile_;  *send contents of mylog back to log window;
run;

When you have a setup like that, any time you submit code from EG it would:

Start a proc printto block.
Execute the submitted code
Close the proc printto block, scan the log, and write the log file to the log window.

So instead of taking the PC SAS approach of using DM commands to copy the content of log window to a file when you want to log scan, you take the opposite approach of always writing the log to a file. I think something like that could work.

Re: Export SAS log to external files

Qing_End — Mon, 01 Aug 2016 15:07:30 GMT

Thank you so much Quentin.

The solution you provided is very creative and useful.

I think it will work and I will post this in this post once I have finished my experiment.