LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (September 2008, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Sat, 20 Sep 2008 10:25:24 +0200
Reply-To:     Rune Runnestø <rune@FASTLANE.NO>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Rune Runnestø <rune@FASTLANE.NO>
Subject:      Re: Displaying information in the log file about which file is
              being processed
Comments: To: sas-l@uga.edu

What I am aiming at is getting the name of the .sas-file being submitted at the moment. That is - the file where the sas-code are written. There may be faults in the code, and i want to localize which .sas-file(s) the errors are located in. Where the errors have their origin. Is SAS able to catch information about which .sas-file is being processed at any time?

Rune

It's not entirely clear what you're aiming at. In the example you give, no file is being processed at the moment - you're in a DATA _NULL_ step without an INFILE or FILE statement. And no DATA step process, macro-ized or not, is going to tell you what file is being processed by a PROC - PROC IMPORT for example.

If you're trying to display external files being processed (input or output) by a DATA step, the FILEVAR option of the INFILE and FILE statements already provides this information - there's no need to write something new.

Frankly, I don't think making the physical name of the file displayed at the bottom of the DATA step "more conspicuous" is going to help much - it's just more clutter on the LOG, and makes the program more complicated.


Back to: Top of message | Previous page | Main SAS-L page