Date: Fri, 5 Aug 2005 14:25:32 -0400
Reply-To: "Fehd, Ronald J" <rjf2@CDC.GOV>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Fehd, Ronald J" <rjf2@CDC.GOV>
Subject: Re: reading LOG file of the currently running program
Content-Type: text/plain; charset="us-ascii"
well all those data sets are in either of work or
<insert libref here>
PROC SQL;describe table Dictionary.Tables;quit;
%Let In_Libref = Library;
PROC SQL;select MemName, Nobs
where LibName in ('WORK',"&In_Libref." )
Ron Fehd the SQL into:macro maven CDC Atlanta GA USA RJF2 at cdc dot
Efficiency is intelligent laziness. -David Dunham
> -----Original Message-----
> From: Philip Primak [mailto:firstname.lastname@example.org]
> Sent: Friday, August 05, 2005 2:17 PM
> To: Fehd, Ronald J
> Subject: Re: reading LOG file of the currently running program
> Hi Ron
> As the matter of fact my message is not a kind of joke. I need to
> retrieve all data sets that were used (to read data from) in the
> program. In SAS V9 there is a message after each step with the
> information of how many observations were read from the input
> data sets
> etc. I meant to use this information to get what I need. My idea is
> that the macro call, which would included the reading of the
> LOG should
> be placed in the very end of the program, and by "reading its own
> log" I meant to read the portion of the log just before the macro
> "Fehd, Ronald J" wrote:
> > > From: Philip Primak
> > >
> > > Another problem I ran into is: how to read (I mean assign
> filename and
> > > read in using data _null_) LOG file of the currently
> running program.
> > uh, consider whether you can participate in the party
> > while looking in the mirror
> > or whether you want to pay someone to videotape the party
> > and look at the video,
> > afterward.
> > A SAS program that reads its own log?
> > this is either a self-referencing program
> > or a Friday-referencing program.
> > yes, you can use proc printto
> > to write the log of a step
> > close that printto log
> > and then read it in the next step.
> > why bother?
> > run ProgramA.sas
> > which produces ProgramA.log
> > then run LogParse on ProgramA.log
> > conceptually, much simpler
> > and having the camera on a tripid
> > makes for less obfuscation.
> > Ron Fehd the Friday maven CDC Atlanta GA USA RJF2 at cdc dot gov
> > > In another words I have to include to my "nowrun.sas"
> something like
> > >
> > > filename readme "nowrun.log";
> > >
> > > data _null_;
> > > infile readme;
> > > length ln $200;
> > > input ln $200.;
> > > ...
> > > run;
> > >
> > > Is there a trick to do this?
> > >
> > > Thank you
> > > Philip Primak
> > > Genzyme corp.
> > >