topic Re: Log Path in SAS Programming

Log Path

Ditza1 — Sun, 22 Oct 2017 11:45:35 GMT

Hi,

Can I get the current path of the log file?

in other word:

proc printto log='c:\em\log1.log';
run;

%let log_path = command to get log path

Re: Log Path

Shmuel — Sun, 22 Oct 2017 14:02:51 GMT

You can change your code to get what you want:

%let log_path =c:\em;
proc printto log="&log_path.\log1.log";
run;

Pay attention - use double quotes instead single quotes.

Re: Log Path

Ditza1 — Sun, 22 Oct 2017 14:16:57 GMT

Some other code set the path or leave it the default value. I am looking
for a way to get it without knowing what happened there

Re: Log Path

Shmuel — Sun, 22 Oct 2017 14:44:04 GMT

@You wrote:

@Ditza1 wrote:
Some other code set the path or leave it the default value. I am looking
for a way to get it without knowing what happened there

As much as I know, there is no deault path for log.

You use FILENAME staetment to link symbolic name - the fileref - to a path,

or define the path directly in your step - as you have done with PROC PRINTTO in your post.

The PROC PRINTO LOG= defines where to save next sas code lines, until it reaches the:

PROC PRINTTO; RUN; - that closes the saved log file.

If there is a predefined path, it should be in a mcro variabe.

Online session log (window) is held in SAS utility catalog.

I'm not sure you have approach to it.

Re: Log Path

Shmuel — Sun, 22 Oct 2017 14:52:19 GMT

Just to be more clear, assuming the program is:

<code part 1>
proc printto log=<path and name.log>; run;

<code part 2>

proc pritto; run;

<code part 3>

the saved log will hold only part 2.

Re: Log Path

Ditza1 — Mon, 23 Oct 2017 06:24:57 GMT

I am not sure l used the right terms.

I wrote a macro that can be used in a lot of other macros. The macro
redirect the log to file and needs to redirect it back to where it was at
the end of the macro. So l am looking for a way to get the log path before
I change it, so i can redirect back at the end of the macro

Re: Log Path

andreas_lds — Mon, 23 Oct 2017 07:33:16 GMT

Check the macro-variable SYSPRINTTOLOG and the option LOG, depending on how the sas-session was started one of them is non-missing if the log is already written to a file.

Re: Log Path

Ditza1 — Mon, 23 Oct 2017 08:00:57 GMT

This seems really what I was looking for, but I am getting
WARNING: Apparent symbolic reference SYSPRINTTOLOG not resolved.

Re: Log Path

Kurt_Bremser — Mon, 23 Oct 2017 08:32:24 GMT

Use %symexist() first to check if a variable exists; if it exists, inspect its contents.

Re: Log Path

Ditza1 — Mon, 23 Oct 2017 09:09:50 GMT

But If It doesn't exist It brings me back to the problem of how to get log path

SYSPRINTTOLOG doesn't exist in neither of the stages of the following code

%put %symexist(SYSPRINTTOLOG);
filename logfile "Y:\log1.txt";
proc printto log= logfile new ; run;
%put %symexist(SYSPRINTTOLOG);
proc printto;run;
%put %symexist(SYSPRINTTOLOG);

Re: Log Path

Kurt_Bremser — Mon, 23 Oct 2017 10:41:34 GMT

You are right. I tested it in 9.4, both with a workspace server and display manager SAS, and in both cases SYSPRINTTOLOG is never set, although the log is successfully redirected.

This runs contrary to what is written in https://support.sas.com/resources/papers/proceedings15/SAS1575-2015.pdf, and in the relevant parts of the SAS documentation:

http://documentation.sas.com/?docsetId=proc&docsetTarget=p1hwvc03z4tqlkn1owzhzo8e7ulu.htm&docsetVersion=3.1&locale=en

http://documentation.sas.com/?docsetId=proc&docsetTarget=p182p6h2jd0qr2n1hjoj0kp2q03a.htm&docsetVersion=3.2&locale=en

Re: Log Path

andreas_lds — Mon, 23 Oct 2017 11:28:08 GMT

Strange. New session started with eg 7.12 on sas 9.4m3. Same result with display manager on the workspace server.

NOTE: PROZEDUR PRINTTO used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      

25         
26         %put &=SYSVLONG;
SYSVLONG=9.04.01M3P062415
27         %put &=SYSPRINTTOLOG;
SYSPRINTTOLOG="############\extlog.log"
28         
29         proc printto;run;

Re: Log Path

PSNn — Mon, 23 Oct 2017 11:38:30 GMT

This is what you need:

%LET LOG = %SYSFUNC(getoption(LOG));

Re: Log Path

Ditza1 — Mon, 23 Oct 2017 11:48:00 GMT

my version is older then yours

SYSVLONG4=9.04.01M1P12042013

So I guess it works only in the newer versions

( And we have in my company older versions of sas)

Any other Ideas of getting log path without using

SYSPRINTTOLOG

Re: Log Path

PSNn — Mon, 23 Oct 2017 11:55:22 GMT

No... This should work With Your Version too. This functionality is VERY old.

You will get a "balnk" value when running interactively and the full pathname of the log file when running in batch mode (where there is a log file).

... I think you replied to another aswer than mine....

TRY IT!

Re: Log Path

Ditza1 — Mon, 23 Oct 2017 11:55:10 GMT

I tried this but I get zero in all LOG macro variables:

filename logfile "C:\log1.txt";
proc printto log= logfile new ; run;
%LET LOG1 = %SYSFUNC(getoption(LOG));
proc printto;run;
%LET LOG2 = %SYSFUNC(getoption(LOG));
%put &LOG0;
%put &LOG1;
%put &LOG2;

Re: Log Path

Kurt_Bremser — Mon, 23 Oct 2017 11:57:59 GMT

If these macro variables only exist in batch mode, then that fact should be part of the documentation.

Re: Log Path

Kurt_Bremser — Mon, 23 Oct 2017 12:10:20 GMT

Ran this:

%put %symexist(SYSPRINTTOLOG);
proc printto log='$HOME/log1.txt' new;run;
%put %symexist(SYSPRINTTOLOG);
%put &SYSPRINTTOLOG;
proc printto log='$HOME/log2.txt' new;run;
%put %symexist(SYSPRINTTOLOG);
%put &SYSPRINTTOLOG;
proc printto;run;
%put %symexist(SYSPRINTTOLOG);
%put &SYSPRINTTOLOG;
%put &=sysvlong;

And got this log in EG:

24         %put %symexist(SYSPRINTTOLOG);
0
25         proc printto log='$HOME/log1.txt' new;run;

NOTE: PROZEDUR PRINTTO used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      

32         %put %symexist(SYSPRINTTOLOG);
0
33         %put &SYSPRINTTOLOG;
WARNING: Apparent symbolic reference SYSPRINTTOLOG not resolved.
&SYSPRINTTOLOG
34         %put &=sysvlong;
SYSVLONG=9.04.01M2P072314

log1.txt:

NOTE: PROZEDUR PRINTTO used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      

26         %put %symexist(SYSPRINTTOLOG);
0
27         %put &SYSPRINTTOLOG;
WARNING: Apparent symbolic reference SYSPRINTTOLOG not resolved.
&SYSPRINTTOLOG
28         proc printto log='$HOME/log2.txt' new;run;

log2.txt:

NOTE: PROZEDUR PRINTTO used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      

29         %put %symexist(SYSPRINTTOLOG);
0
30         %put &SYSPRINTTOLOG;
WARNING: Apparent symbolic reference SYSPRINTTOLOG not resolved.
&SYSPRINTTOLOG
31         proc printto;run;

SAS on AIX, so this might be specific to the OS.

Edit:

Ran the same in batch mode, identical result. Maybe there's an option that disables this?

Re: Log Path

PSNn — Mon, 23 Oct 2017 12:09:34 GMT

Yes, this is batch things...

Re: Log Path

Kurt_Bremser — Mon, 23 Oct 2017 12:12:09 GMT

@PSNn wrote:

Yes, this is batch things...

See my other post. Tested it in workspace server, display manager and batch. Same result everywhere.

I'm considering opening a track with SAS TS. Either the documentation is incomplete, or something else is fishy.