02.05.2013 Views

SAS(R) 9.1.3 Companion for z/OS

SAS(R) 9.1.3 Companion for z/OS

SAS(R) 9.1.3 Companion for z/OS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

116 Directing Output to a Printer Chapter 6<br />

//REPORT JOB accounting-in<strong>for</strong>mation,<br />

// MSGLEVEL=(1,1)<br />

//<strong>SAS</strong>STEP EXEC <strong>SAS</strong>,OPTIONS=’LINESIZE=80 N<strong>OS</strong>TATS’<br />

//<strong>SAS</strong>LOG DD DSN=MYID.MONTHLY.REPORT(DEPT),<br />

// DISP=OLD<br />

//<strong>SAS</strong>LIST DD DSN=MYID.MONTHLY.OUTPUT,DISP=MOD<br />

//SYSIN DD *<br />

<strong>SAS</strong> statements<br />

//<br />

Note: <strong>SAS</strong>LOG and <strong>SAS</strong>LIST are the default DDnames of the <strong>SAS</strong> log and<br />

procedure output files. If these DDnames have been changed in your site’s <strong>SAS</strong><br />

cataloged procedure, then use your site’s DDnames in place of <strong>SAS</strong>LOG and <strong>SAS</strong>LIST. R<br />

CAUTION:<br />

The <strong>SAS</strong> cataloged procedure specifies default DCB characteristics unless you specify them<br />

in the <strong>SAS</strong>LOG or <strong>SAS</strong>LIST DD statement. If you are directing the <strong>SAS</strong> log to a member<br />

of a partitioned data set whose DCB characteristics are different from those given in<br />

“<strong>SAS</strong> Log File” on page 19, you must include the existing DCB characteristics in the<br />

<strong>SAS</strong>LOG DD statement. Similarly, if you are directing the <strong>SAS</strong> procedure output to a<br />

member of a partitioned data set whose DCB characteristics are different from those<br />

given in “<strong>SAS</strong> Procedure Output File” on page 20, you must include the existing DCB<br />

characteristics in the <strong>SAS</strong>LIST DD statement. Otherwise, the existing DCB<br />

characteristics of the partitioned data set will be changed to the characteristics that<br />

are specified <strong>for</strong> <strong>SAS</strong>LOG or <strong>SAS</strong>LIST in the <strong>SAS</strong> cataloged procedure, making the<br />

other members of the partitioned data set unreadable. R<br />

Directing Output to a Printer<br />

Beginning in Release 8.2, <strong>SAS</strong> supports two printing destinations <strong>for</strong> directing<br />

procedure output on z/<strong>OS</strong>: Universal Printing and Xprinter (line) printing. A Universal<br />

printer is an e-mail message, network printer, or file that exists on a local area network<br />

(LAN). Universal Printing is the default printing destination. Xprinter translates to a<br />

printer device on an SNA network. The FORM subsystem is one way to direct output<br />

that is destined <strong>for</strong> a line printer.<br />

The printing destination and default printer at a site are typically determined by data<br />

center personnel. This section contains instructions <strong>for</strong> directing procedure output using<br />

either of the printing destinations. You can direct <strong>SAS</strong> output to a printer as follows:<br />

3 by using the PRINTTO procedure combined with Universal Printing<br />

3 by using the PRINT command or menu selection combined with Universal Printing<br />

3 by using the PRINT command or menu selection combined with the FORM<br />

subsystem<br />

3 by using the PRTFILE command and the PRINT command or menu selection<br />

combined with the FORM subsystem.<br />

Universal Printing and the FORM subsystem are portable and are there<strong>for</strong>e<br />

documented in the Base <strong>SAS</strong> section of the <strong>SAS</strong> Help and in the <strong>SAS</strong> Language<br />

Reference: Dictionary. To help customer sites get started with Universal Printing, some<br />

common z/<strong>OS</strong> printer definitions, sample printer setup programs, and sample print<br />

commands are also provided in Chapter 7, “Universal Printing,” on page 147.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!