"Edging in" program b whilst program a is running

Sinistrum — Fri, 19 Aug 2016 07:25:54 GMT

Dear community,

I would be glad if you could comment on this "rather exotic" issue of mine.

The scenario is the following:

I started a program yesterday evening in order to let it run overnight.

proc printto log="c:\directory-name\filename.log"; run;

Clumsy as I am, I had the following added to the program:

options nonotes nosource nosource2 errors=0;

So you can imagine, how informative my log is.

The program is still running and I suspect something suspicious is going on.

But looking at the "log" will not help.

Can I somehow "edge in"

options notes source source2 errors=20;

to fill the log with life again?

I do not want to terminate the program, for I do not have a "feeling" at which point the program is.

Maybe, something is really wrong and it is e.g. at 7%, or, I terminate at 99% and everything is lost.

I see, this is a very "special" constellation, having come into existence due to my sheer idioty.

But still, maybe there is some hope for me.

If not, I learn something about how SAS-program-processing works (hey, it is something).

Yours sincerely,

Sinistrum

Re: "Edging in" program b whilst program a is running

Kurt_Bremser — Fri, 19 Aug 2016 07:35:15 GMT

I guess you ran it from EG?

But anyway, the only option you have is stopping/terminating the job.

Another reason why one should never reduce the information going to the log.

Sinistrum — Fri, 19 Aug 2016 09:13:14 GMT

Thank you for your reply.

I guess, "EG" means "Enterprise Guide"?

Then no, I have run it with base SAS (yes, there is a base SAS users as stupid as me out there).

I will terminate the program.