Discussion:
Where is the NOPRINT option for PROC REPORT?
(too old to reply)
Jack Clark
2009-10-13 12:48:04 UTC
Permalink
Hello,

=20

I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to make
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC REPORT
statement generates an error.

=20

I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.

=20

Does anyone have a good solution for suppressing the PROC REPORT output,
while avoiding the pesky warning messages in the log?

=20

I am using SAS 9.1 on Windows, remote submitting for processing on UNIX.
Thank you.

=20

=20

=20



Jack Clark
Senior Research Analyst=20
phone: 410-455-6256
fax: 410-455-6850
***@hilltop.umbc.edu=20

University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250




Confidentiality Notice: This e-mail may contain information that is =
legally privileged and that is intended only for the use of the =
addressee(s) named above. If you are not the intended recipient, you are =
hereby notified that any disclosure, copying of this e-mail, =
distribution, or action taken in reliance on the contents of this e-mail =
and/or documents attributed to this e-mail is strictly prohibited. If =
you have received this information in error, please notify the sender =
immediately by phone and delete this entire e-mail. Thank you.
inason
2009-10-13 13:31:22 UTC
Permalink
Use the Option NOWD
Data _null_;
2009-10-13 13:29:01 UTC
Permalink
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to make
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC REPORT
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT output,
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on UNIX.
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is legally privileged and that is intended only for the use of the addressee(s) named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying of this e-mail, distribution, or action taken in reliance on the contents of this e-mail and/or documents attributed to this e-mail is strictly prohibited. If you have received this information in error, please notify the sender immediately by phone and delete this entire e-mail. Thank you.
Data _null_;
2009-10-13 13:30:08 UTC
Permalink
But that don't work because then the data set will have no data.
Post by Data _null_;
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to make
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC REPORT
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT output,
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on UNIX.
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is legally privileged and that is intended only for the use of the addressee(s) named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying of this e-mail, distribution, or action taken in reliance on the contents of this e-mail and/or documents attributed to this e-mail is strictly prohibited. If you have received this information in error, please notify the sender immediately by phone and delete this entire e-mail. Thank you.
Data _null_;
2009-10-13 13:33:14 UTC
Permalink
Sounds like a job for good old proc printto.

filename FT16F001 dummy;
proc printto print=FT16F001;
run;


Or I reckon you could use

ods listing file=FT16F001;
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to make
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC REPORT
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT output,
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on UNIX.
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is legally privileged and that is intended only for the use of the addressee(s) named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying of this e-mail, distribution, or action taken in reliance on the contents of this e-mail and/or documents attributed to this e-mail is strictly prohibited. If you have received this information in error, please notify the sender immediately by phone and delete this entire e-mail. Thank you.
Data _null_;
2009-10-13 13:38:27 UTC
Permalink
It didn't for me. I got zero obs and zero vars. What version of SAS?

I have

NOTE: This session is executing on the WIN_PRO platform.
NOTE: SAS 9.1.3 Service Pack 4
_null_,
The dataset does still have data.
Jack
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:30 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
But that don't work because then the data set will have no data.
Post by Data _null_;
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs
to
Post by Data _null_;
Post by Jack Clark
generate output data sets (I know, I know, there are better ways to
make
Post by Data _null_;
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Data _null_;
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Data _null_;
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Data _null_;
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Jack Clark
2009-10-13 13:34:57 UTC
Permalink
_null_,

The dataset does still have data.


Jack



Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
***@hilltop.umbc.edu

University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250


-----Original Message-----
From: Data _null_; [mailto:***@gmail.com]
Sent: Tuesday, October 13, 2009 9:30 AM
To: Jack Clark
Cc: SAS-***@listserv.uga.edu
Subject: Re: Where is the NOPRINT option for PROC REPORT?

But that don't work because then the data set will have no data.
Post by Data _null_;
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs
to
Post by Data _null_;
Post by Jack Clark
generate output data sets (I know, I know, there are better ways to
make
Post by Data _null_;
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Data _null_;
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Data _null_;
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Data _null_;
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Jack Clark
2009-10-13 13:55:47 UTC
Permalink
_null_,

This seems to solve the problem. Thank you.


Jack





Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
***@hilltop.umbc.edu

University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250


-----Original Message-----
From: Data _null_; [mailto:***@gmail.com]
Sent: Tuesday, October 13, 2009 9:33 AM
To: Jack Clark
Cc: SAS-***@listserv.uga.edu
Subject: Re: Where is the NOPRINT option for PROC REPORT?

Sounds like a job for good old proc printto.

filename FT16F001 dummy;
proc printto print=FT16F001;
run;


Or I reckon you could use

ods listing file=FT16F001;
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to
make
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Jack Clark
2009-10-13 13:53:16 UTC
Permalink
_null_,

This is the info from the remote session...

NOTE: Remote signon to GINGER commencing (SAS Release 9.01.01M3P072804).
NOTE: Script file 'tcpunix.scr' entered.
NOTE: Logged onto UNIX... Starting remote SAS now.
NOTE: SAS/CONNECT conversation established.
NOTE: Copyright (c) 2002-2003 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) 9.1 (TS1M3)
Licensed to UNIVERSITY OF MARYLAND BALTIMORE COUNTY-T&R, Site
0002318068.
NOTE: This session is executing on the SunOS 5.9 platform.


The code below is submitted from Windows to the remote Unix server. I
issue the ODS LISTING CLOSE and ODS LISTING statements in the local
environment. The PROC DATASETS shows all 4 data sets existing in the
remote WORK directory and I get the printout from all 4 datasets as
well.


rsubmit;

title1 "UNIX Processing";
title2 "Number 1";
proc report data = sashelp.class out=test1 nowindows;
column name age;
run;

endrsubmit;

ods listing close;

rsubmit;

title1 "UNIX Processing";
title2 "Number 2";
proc report data = sashelp.class out=test2 nowindows;
column name age;
run;

title2 "Number 3";
proc report data = sashelp.class out=test3 nowindows;
column name age;
run;

title2 "Number 4";
proc report data = sashelp.class out=test4 nowindows;
column name age;
run;


endrsubmit;

ods listing;


rsubmit;

proc datasets library = work;
run;

title1 "Output Test 1";
proc print data = test2;
run;

title1 "Output Test 2";
proc print data = test2;
run;

title1 "Output Test 3";
proc print data = test3;
run;

title1 "Output Test 4";
proc print data = test4;
run;

endrsubmit;











NOTE: SAS 9.1.3 Service Pack 4



Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
***@hilltop.umbc.edu

University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250


-----Original Message-----
From: Data _null_; [mailto:***@gmail.com]
Sent: Tuesday, October 13, 2009 9:38 AM
To: Jack Clark
Cc: SAS-***@listserv.uga.edu
Subject: Re: Where is the NOPRINT option for PROC REPORT?

It didn't for me. I got zero obs and zero vars. What version of SAS?

I have

NOTE: This session is executing on the WIN_PRO platform.
NOTE: SAS 9.1.3 Service Pack 4
_null_,
The dataset does still have data.
Jack
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:30 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
But that don't work because then the data set will have no data.
Post by Data _null_;
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs
to
Post by Data _null_;
Post by Jack Clark
generate output data sets (I know, I know, there are better ways
to
make
Post by Data _null_;
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of
the
Post by Data _null_;
Post by Jack Clark
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Data _null_;
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says
no
Post by Data _null_;
Post by Jack Clark
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Data _null_;
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Data _null_;
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that
is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you
are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this
e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Data _null_;
2009-10-13 13:59:53 UTC
Permalink
The "thing" that didn't work for me was ODS EXCLUDE. Did you try that?
_null_,
This is the info from the remote session...
NOTE: Remote signon to GINGER commencing (SAS Release 9.01.01M3P072804).
NOTE: Script file 'tcpunix.scr' entered.
NOTE: Logged onto UNIX... Starting remote SAS now.
NOTE: SAS/CONNECT conversation established.
NOTE: Copyright (c) 2002-2003 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) 9.1 (TS1M3)
Licensed to UNIVERSITY OF MARYLAND BALTIMORE COUNTY-T&R, Site
0002318068.
NOTE: This session is executing on the SunOS 5.9 platform.
The code below is submitted from Windows to the remote Unix server. I
issue the ODS LISTING CLOSE and ODS LISTING statements in the local
environment. The PROC DATASETS shows all 4 data sets existing in the
remote WORK directory and I get the printout from all 4 datasets as
well.
rsubmit;
title1 "UNIX Processing";
title2 "Number 1";
proc report data = sashelp.class out=test1 nowindows;
column name age;
run;
endrsubmit;
ods listing close;
rsubmit;
title1 "UNIX Processing";
title2 "Number 2";
proc report data = sashelp.class out=test2 nowindows;
column name age;
run;
title2 "Number 3";
proc report data = sashelp.class out=test3 nowindows;
column name age;
run;
title2 "Number 4";
proc report data = sashelp.class out=test4 nowindows;
column name age;
run;
endrsubmit;
ods listing;
rsubmit;
proc datasets library = work;
run;
title1 "Output Test 1";
proc print data = test2;
run;
title1 "Output Test 2";
proc print data = test2;
run;
title1 "Output Test 3";
proc print data = test3;
run;
title1 "Output Test 4";
proc print data = test4;
run;
endrsubmit;
NOTE: SAS 9.1.3 Service Pack 4
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:38 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
It didn't for me. I got zero obs and zero vars. What version of SAS?
I have
NOTE: This session is executing on the WIN_PRO platform.
NOTE: SAS 9.1.3 Service Pack 4
_null_,
The dataset does still have data.
Jack
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:30 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
But that don't work because then the data set will have no data.
Post by Data _null_;
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs
to
Post by Data _null_;
Post by Jack Clark
generate output data sets (I know, I know, there are better ways
to
make
Post by Data _null_;
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of
the
Post by Data _null_;
Post by Jack Clark
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Data _null_;
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says
no
Post by Data _null_;
Post by Jack Clark
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Data _null_;
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Data _null_;
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that
is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you
are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this
e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Jack Clark
2009-10-13 14:26:02 UTC
Permalink
_null_,

When I tried the ODS EXCLUDE, no observations were written to the output
data set from the PROC REPORT. This obviously is not what I want.

The DUMMY filename is what I will use. Thanks for the solution.


Jack




Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
***@hilltop.umbc.edu

University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250


-----Original Message-----
From: Data _null_; [mailto:***@gmail.com]
Sent: Tuesday, October 13, 2009 10:00 AM
To: Jack Clark
Cc: SAS-***@listserv.uga.edu
Subject: Re: Where is the NOPRINT option for PROC REPORT?

The "thing" that didn't work for me was ODS EXCLUDE. Did you try that?
_null_,
This is the info from the remote session...
NOTE: Remote signon to GINGER commencing (SAS Release
9.01.01M3P072804).
NOTE: Script file 'tcpunix.scr' entered.
NOTE: Logged onto UNIX... Starting remote SAS now.
NOTE: SAS/CONNECT conversation established.
NOTE: Copyright (c) 2002-2003 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) 9.1 (TS1M3)
Licensed to UNIVERSITY OF MARYLAND BALTIMORE COUNTY-T&R, Site
0002318068.
NOTE: This session is executing on the SunOS 5.9 platform.
The code below is submitted from Windows to the remote Unix server. I
issue the ODS LISTING CLOSE and ODS LISTING statements in the local
environment. The PROC DATASETS shows all 4 data sets existing in the
remote WORK directory and I get the printout from all 4 datasets as
well.
rsubmit;
title1 "UNIX Processing";
title2 "Number 1";
proc report data = sashelp.class out=test1 nowindows;
column name age;
run;
endrsubmit;
ods listing close;
rsubmit;
title1 "UNIX Processing";
title2 "Number 2";
proc report data = sashelp.class out=test2 nowindows;
column name age;
run;
title2 "Number 3";
proc report data = sashelp.class out=test3 nowindows;
column name age;
run;
title2 "Number 4";
proc report data = sashelp.class out=test4 nowindows;
column name age;
run;
endrsubmit;
ods listing;
rsubmit;
proc datasets library = work;
run;
title1 "Output Test 1";
proc print data = test2;
run;
title1 "Output Test 2";
proc print data = test2;
run;
title1 "Output Test 3";
proc print data = test3;
run;
title1 "Output Test 4";
proc print data = test4;
run;
endrsubmit;
NOTE: SAS 9.1.3 Service Pack 4
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:38 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
It didn't for me. I got zero obs and zero vars. What version of SAS?
I have
NOTE: This session is executing on the WIN_PRO platform.
NOTE: SAS 9.1.3 Service Pack 4
_null_,
The dataset does still have data.
Jack
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:30 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
But that don't work because then the data set will have no data.
Post by Data _null_;
ods exclude Report(persist);
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC
REPORTs
to
Post by Data _null_;
Post by Jack Clark
generate output data sets (I know, I know, there are better ways
to
make
Post by Data _null_;
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of
the
Post by Data _null_;
Post by Jack Clark
PROC REPORT output in my .lst file. I see that there is a
NOPRINT
Post by Data _null_;
Post by Jack Clark
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Data _null_;
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the
PROC
Post by Data _null_;
Post by Jack Clark
REPORT, but this generates a warning message in the log that
says
no
Post by Data _null_;
Post by Jack Clark
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Data _null_;
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing
on
UNIX.
Post by Data _null_;
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that
is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you
are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this
e-mail
and/or documents attributed to this e-mail is strictly prohibited.
If
you have received this information in error, please notify the
sender
immediately by phone and delete this entire e-mail. Thank you.
Jack Clark
2009-10-13 15:24:01 UTC
Permalink
Another development...

When using the DUMMY filename, the page numbers are still "counted" for
the procedure output being "suppressed".

The code below only displays the output for #1 and #4 - which is
desired. But the SAS list file has page numbers 1 and 4 instead of 1
and 2. I guess the page number still increments when writing to the
DUMMY file. Thoughts?


options pageno=1;

filename dumdum DUMMY;


title2 "Number 1";
proc report data = sashelp.class out=test1 nowindows;
column name age;
run;


ods listing file=dumdum;

title2 "Number 2";
proc report data = sashelp.class out=test2 nowindows;
column name age;
run;

title2 "Number 3";
proc report data = sashelp.class out=test3 nowindows;
column name age;
run;

ods listing;


title2 "Number 4";
proc report data = sashelp.class out=test4 nowindows;
column name age;
run;









Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
***@hilltop.umbc.edu

University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250


-----Original Message-----
From: Data _null_; [mailto:***@gmail.com]
Sent: Tuesday, October 13, 2009 9:33 AM
To: Jack Clark
Cc: SAS-***@listserv.uga.edu
Subject: Re: Where is the NOPRINT option for PROC REPORT?

Sounds like a job for good old proc printto.

filename FT16F001 dummy;
proc printto print=FT16F001;
run;


Or I reckon you could use

ods listing file=FT16F001;
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to
make
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Data _null_;
2009-10-13 15:45:36 UTC
Permalink
Oh dear!

This may help http://support.sas.com/techsup/technote/ts549.html
Post by Jack Clark
Another development...
When using the DUMMY filename, the page numbers are still "counted" for
the procedure output being "suppressed".
The code below only displays the output for #1 and #4 - which is
desired. But the SAS list file has page numbers 1 and 4 instead of 1
and 2. I guess the page number still increments when writing to the
DUMMY file. Thoughts?
options pageno=1;
filename dumdum DUMMY;
title2 "Number 1";
proc report data = sashelp.class out=test1 nowindows;
column name age;
run;
ods listing file=dumdum;
title2 "Number 2";
proc report data = sashelp.class out=test2 nowindows;
column name age;
run;
title2 "Number 3";
proc report data = sashelp.class out=test3 nowindows;
column name age;
run;
ods listing;
title2 "Number 4";
proc report data = sashelp.class out=test4 nowindows;
column name age;
run;
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:33 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
Sounds like a job for good old proc printto.
filename FT16F001 dummy;
proc printto print=FT16F001;
run;
Or I reckon you could use
ods listing file=FT16F001;
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs to
generate output data sets (I know, I know, there are better ways to
make
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County
Sondheim Hall, 3rd Floor
1000 Hilltop Circle
Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this e-mail
and/or documents attributed to this e-mail is strictly prohibited. If
you have received this information in error, please notify the sender
immediately by phone and delete this entire e-mail. Thank you.
Mike Rhoads
2009-10-13 17:20:26 UTC
Permalink
Or maybe a different approach (than EXCLUDE or PRINTTO) -- CLOSE and reopen LISTING as you suggested originally, but at the same time open some other ODS destination as a dummy. For instance, just create an HTML file that goes to some throwaway destination. Hopefully that would avoid both disjointed page numbers and the warning in your log.

Yes, it's somewhat clunky, but there doesn't seem to be a particularly elegant solution ...


Mike Rhoads
***@Westat.com


-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-***@LISTSERV.UGA.EDU] On Behalf Of Data _null_;
Sent: Tuesday, October 13, 2009 11:46 AM
To: SAS-***@LISTSERV.UGA.EDU
Subject: Re: Where is the NOPRINT option for PROC REPORT?

Oh dear!

This may help http://support.sas.com/techsup/technote/ts549.html
Post by Jack Clark
Another development...
When using the DUMMY filename, the page numbers are still "counted"
for the procedure output being "suppressed".
The code below only displays the output for #1 and #4 - which is
desired. But the SAS list file has page numbers 1 and 4 instead of 1
and 2. I guess the page number still increments when writing to the
DUMMY file. Thoughts?
options pageno=1;
filename dumdum DUMMY;
title2 "Number 1";
proc report data = sashelp.class out=test1 nowindows;
column name age;
run;
ods listing file=dumdum;
title2 "Number 2";
proc report data = sashelp.class out=test2 nowindows;
column name age;
run;
title2 "Number 3";
proc report data = sashelp.class out=test3 nowindows;
column name age;
run;
ods listing;
title2 "Number 4";
proc report data = sashelp.class out=test4 nowindows;
column name age;
run;
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County Sondheim Hall, 3rd Floor 1000
Hilltop Circle Baltimore, MD 21250
-----Original Message-----
Sent: Tuesday, October 13, 2009 9:33 AM
To: Jack Clark
Subject: Re: Where is the NOPRINT option for PROC REPORT?
Sounds like a job for good old proc printto.
filename FT16F001 dummy;
proc printto print=FT16F001;
run;
Or I reckon you could use
ods listing file=FT16F001;
Post by Jack Clark
Hello,
I am modifying some existing code which uses a lot of PROC REPORTs
to generate output data sets (I know, I know, there are better ways
to
make
Post by Jack Clark
data sets - it wasn't my code). I don't really want/need all of the
PROC REPORT output in my .lst file. I see that there is a NOPRINT
option on the DEFINE statements, but putting NORPINT on the PROC
REPORT
Post by Jack Clark
statement generates an error.
I considered using ODS LISTING CLOSE / ODS LISTING around the PROC
REPORT, but this generates a warning message in the log that says no
output destination is active.
Does anyone have a good solution for suppressing the PROC REPORT
output,
Post by Jack Clark
while avoiding the pesky warning messages in the log?
I am using SAS 9.1 on Windows, remote submitting for processing on
UNIX.
Post by Jack Clark
Thank you.
Jack Clark
Senior Research Analyst
phone: 410-455-6256
fax: 410-455-6850
University of Maryland, Baltimore County Sondheim Hall, 3rd Floor
1000 Hilltop Circle Baltimore, MD 21250
Confidentiality Notice: This e-mail may contain information that is
legally privileged and that is intended only for the use of the
addressee(s) named above. If you are not the intended recipient, you
are hereby notified that any disclosure, copying of this e-mail,
distribution, or action taken in reliance on the contents of this
e-mail and/or documents attributed to this e-mail is strictly
prohibited. If you have received this information in error, please
notify the sender immediately by phone and delete this entire e-mail. Thank you.
Loading...