Date:         Thu, 21 Mar 2002 13:09:40 -0500
Reply-To:     Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Subject:      Re: print control characters on MVS
Content-Type: text/plain; charset=ISO-8859-1

On Thu, 21 Mar 2002 17:15:53 GMT, Tony Harmon
<atharmonshirt@REMOVESHIRTSWBELL.NET> wrote:

>ghellrieg@T-ONLINE.DE (Gerhard Hellriegel) writes:
>
>> On Thu, 21 Mar 2002 16:05:43 GMT, Tony Harmon
>> <atharmonshirt@REMOVESHIRTSWBELL.NET> wrote:
>>
>> >ghellrieg@T-ONLINE.DE (Gerhard Hellriegel) writes:
>> >
>> >> On Thu, 21 Mar 2002 15:03:36 GMT, Tony Harmon
>> >> <atharmonshirt@REMOVESHIRTSWBELL.NET> wrote:
>> >>
>> >> >All,
>> >> >
>> >> >We have some SAS programs that create reports that are ftp'd
>> >> >to a mid-tier environment (AIX), and then converted to a pdf
>> >> >document. Our problem is that SAS is not putting the print
>> >> >control characters in the report and therefore the report
>> >> >doesn't page correctly when printed or viewed by anything
>> >> >other than the SAS system. Is there a parameter in PROC
>> >> >PRINT that tells SAS to put in the print control characters?
>> >> >
>> >> >Thanks,
>> >> >Tony
>> >>
>> >>
>> >> Hm, I think the main problem there is, that the print control chars on
>> the
>> >> mainframe are the ASA - chars which on a AIX are only 1, -, +, ...
but no
>> >> control-characters.
>> >> What about using ODS to produce something what also the AIX can
handle? I
>> >> think it should be possible to produce formatted output in a standard
>> >> format, like HTML. I'm not really sure if it is possible to output
PDFs
>> >> directly on the host machine, but I assume that it won't! But HTML
could
>> be
>> >> converted to PDF on the AIX machine, I'm sure. The "normal" output
will
>> not
>> >> contain any valid printer control chars. Another possibility: you can
>> >> produce a graphical output with proc gprint, e.g. GIFs, if you have
graph
>> >> on the host. That should also be convertable to PDF.
>> >
>> >Thanks. On the mainframe we have a process that strips the mainframe
>> control
>> >characters and replaces them with the AIX equivalents. We then ftp the
file
>> >down to the mid-tier where I have scripts that convert it to postscript
>> then
>> >to pdf.
>> >
>> >I think I may have found an answer: I found that in the FILE/FILENAME
>> keyword
>> >you can specify cc=<format>. The problem is that I am not a SAS
programmer,
>> >and we don't have anyone available. Right now it does a PROC PRINTTO to
>> >associate the file that the PROC PRINT statements print to. I'm
guessing I
>> >have to associate a FILE/FILENAME to that file first?
>> >
>> >Thanks,
>> >Tony
>>
>> Tony, I can't imagine, that CC does what you need! CC= is a mail option
and
>> specifies a "carbon copy recipient" of a mail which you can send by SAS.
>> Maybe you do not use FTP to bring the results to the AIX, but you sent it
>> by a automaticly generated e-mail.
>>
>> Normally cc looks like
>>
>> cc='Joe Smith <joe§somplace.org>'
>
>Maybe I'm looking at it wrong, but according to the documentation I have:
>
>CC= specifies the carriage-control format of the SAS log and listing file.
>This option has three possible values:
>
>     FORTRAN
>          indicates FORTRAN carriage-control format. This is the default
>          for print files.
>
>     PRINT
>          indicates OpenVMS print format.
>
>     CR
>          indicates OpenVMS carriage-return, carriage-control format. This
>          is the default for nonprinting files.
>
>     Only SAS print files are affected by the CC= option. The CC= option is
>     used for output.
>
>     The CC= option also exists as a SAS system option (see CC=). If you
>     specify this option both as a system option and in the FILENAME or
FILE
>     statement, then SAS uses the value that you specified in the FILENAME
>     or FILE statement.
>
>Tony

...by the way:

what do you mean with FILENAME or FILE statement??

FILENAME is a global statement which assigns a logical name to a physical
one.
e.g.
filename a "test.test.test";
where a is the logical (SAS-internal) name and test.test.test is the
external (physical) name in your OS-environment.

FILE is a statement in a DATA step which assigns a external output-file.
This can be a physical or a logical name:

data _null_;
  file a;
  put ....;
run;

or

data _null_;
  file "test.test.test";
  put ...;
run;


So let's try that and have a look on the log:

53   data _null_;
54     file "int5112.sas.output(test)" cc=FORTRAN;
                                       --
                                       23
ERROR 23-2: Invalid option name CC.

55     put "test";
56   run;

NOTE: The SAS System stopped processing this step because of errors.
NOTE: The DATA statement used 0.00 CPU seconds and 13719K.


or the other way:

 57   filename a "int5112.sas.output(test)" cc=FORTRAN;
                                            --
                                            23
 ERROR: Error in the FILENAME statement.
 ERROR 23-2: Invalid option name CC.

 58   data _null_;
 59     file a cc=FORTRAN;
               --
               23
 ERROR 23-2: Invalid option name CC.

 60     put "test";
 61   run;

 NOTE: The SAS System stopped processing this step because of errors.
 NOTE: The DATA statement used 0.00 CPU seconds and 13719K.


So I don't know what you use!