An Idea Exchange for SAS software and services

Comments
by Respected Advisor
on ‎01-17-2013 09:27 PM
No. The work specification is a real mess. I have to correct my client's equations for calculating the CO2 ecosystem exchange from scratch (original articles). I'll continue tomorow.
Good night!
by Occasional Contributor temp233
on ‎04-10-2014 02:55 PM

I wrote this suggestion and then I said to myself "Self, what a great idea!"  I hope someone else thinks so too.  Even if you don't, thanks for looking and please share your thoughts on my suggestion, whatever they may be.

by Regular Contributor
on ‎04-10-2014 03:11 PM

Thank you. I know what your are doing but I never considered doing what you are doing.  If I'm running batch jobs with the macro, I can change the library name to a permanent library and view all the output if there is ever an error or bad data that needs to be tracked or if the report recipient has a complaint about their report.  I wonder if there is a way to output logs to different files during macro processing.  It would be easier it track errors if each macro could be manipulated to write to its own unique log file.

by Super User
on ‎04-10-2014 03:12 PM

How would you expect to see this implemented?

As your example shows, you can do this manually so what features would you expect to see or how would you expect to call it?

Also, how do you prevent giant datasets from being copied, I don't want to copy some of my files that are 30M rows.

by Super User
on ‎04-10-2014 03:14 PM

You can embed a proc printto to control the log destination.

by Occasional Contributor temp233
on ‎04-10-2014 03:19 PM

Thanks your your thoughts.  I think that PROC PRINTTO can be used to re-direct log messages to an external file and to re-direct again back to the default destination.

by Regular Contributor
on ‎04-10-2014 03:19 PM

Reeza,

Thank you for the memory jog. Good Idea. I haven't considered using Proc Printto since version 6 on the mainframe when I coded all my output files via JCL. Smiley Happy

by Occasional Contributor temp233
on ‎04-10-2014 03:21 PM

Ah, actually you can't do it manually.  Did you try running:

libname localMac type=temp:

?

It's pseudocode, and results in a libname error.

by Super User
on ‎04-10-2014 03:26 PM

No, but you can delete the library at the end.

Cleaning up after yourself in real life and coding is always best practice Smiley Happy

by Occasional Contributor temp233
on ‎04-10-2014 03:31 PM

"No, but you can delete the library at the end."

True, but in this case since the initial libname statement fails with an error, cleaning up is not really necessary.  The libname statement as written, by the way, is the functionality I'm asking for, and does not currently exist.

Idea Statuses
Top Liked Authors