Hi:
If you do make a CSV file from your procedure output, then your limitation on the number of report rows that you can have are limited by your spreadsheet program limit.
Other options to a DATA step program writing to a file are:
--investigate the use of the FORMDLIM option, which does not remove page break characters, but would let you replace the usual page break character with something like a line of dashes, for example:
http://support.sas.com/documentation/cdl/en/lrdict/59540/HTML/default/a000279106.htm
It is possible that some combination of FORMDLIM with PROC PRINTTO will give you a LISTING version of your output that does not have page breaks.
--make an ODS HTML file with style=minimal. There are no page breaks in an HTML file you will get one huge table with all the report rows. Page breaks are only inserted in an HTML file when the browser needs to print the file. The viewer for an HTML file is a web browser or any HTML viewer.
--avoid "paged" destinations, like PDF and RTF. Those destinations DO insert page break characters or instructions, as appropriate to the destination.
I'm just wondering what the purpose of no page breaks is -- without any kind of pause or reader break in the output, it will be very hard for someone to review the output. If all you want is an archive or record of the output and you don't intend to look at the output file after the fact, then the page break characters and page numbers don't add -that- much to the size of the file (and you can turn the titles and page numbers off). You could just use ODS or PROC PRINTTO to do the equivalent of taking a snapshot of the LISTING file output and then store the file on disk.
Just a few more suggestions.
cynthia