Date: Fri, 15 Dec 2006 09:26:42 -0800
Reply-To: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
Subject: Re: a question of the ODS and log window
In-Reply-To: <BAY123-F24A76742497E0EA4FADC8FDED10@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
toby dunn wrote:
> I am a little confused by your post. ODS changes your output destination
> not your log destination.
In general, but not always.
Some (perhaps all) PROC DATASETS information, for example, is sent to
the log but can be controlled by ODS.
=====
ods listing select all;
proc datasets library=sasuser;
run; quit;
ods listing select none;
ods output base.datasets.members=members;
proc datasets library=sasuser;
run; quit;
ods output close;
=====
creates the following log:
=====
822 ods listing select all;
823
824 proc datasets library=sasuser;
Directory
Libref SASUSER
Engine V9
Access READONLY
Physical Name p:\My SAS Files\9.1
File Name p:\My SAS Files\9.1
Member File
# Name Type Size Last Modified
1 PROFILE CATALOG 70656 14Dec06:09:10:18
2 PROFILE2 CATALOG 17408 14Dec06:08:51:00
3 REGSTRY ITEMSTOR 17408 14Dec06:09:10:28
825 run;
825! quit;
NOTE: PROCEDURE DATASETS used (Total process time):
real time 0.07 seconds
cpu time 0.00 seconds
826
827 ods listing select none;
828
829 ods output base.datasets.members=members;
830
831 proc datasets library=sasuser;
832 run;
832! quit;
NOTE: The data set WORK.MEMBERS has 3 observations and 5 variables.
NOTE: PROCEDURE DATASETS used (Total process time):
real time 0.07 seconds
cpu time 0.03 seconds
833
834 ods output close;
=====