Routing the SAS Log and SAS Procedure Output

Similar documents
Routing Output. Producing Output with SAS Software CHAPTER 6

Chapter 28 Saving and Printing Tables. Chapter Table of Contents SAVING AND PRINTING TABLES AS OUTPUT OBJECTS OUTPUT OBJECTS...

Data Representation. Variable Precision and Storage Information. Numeric Variables in the Alpha Environment CHAPTER 9

Storing and Reusing Macros

APPENDIX 2 Customizing SAS/ASSIST Software

Using Cross-Environment Data Access (CEDA)

Chapter 3 Managing Results in Projects. Chapter Table of Contents

External Files. Definition CHAPTER 38

APPENDIX 4 Migrating from QMF to SAS/ ASSIST Software. Each of these steps can be executed independently.

from the source host, use the FTP put command to copy a file from the source host to the target host.

Customizing Your SAS Session

Creating and Executing Stored Compiled DATA Step Programs

Using Data Transfer Services

Permission Program. Support for Version 6 Only. Allowing SAS/SHARE Client Access to SAS Libraries or Files CHAPTER 40

Procedures. PROC CATALOG CATALOG=<libref.>catalog <ENTRYTYPE=etype> <KILL>; CONTENTS <OUT=SAS-data-set> <FILE=fileref;>

Formats. Formats Under UNIX. HEXw. format. $HEXw. format. Details CHAPTER 11

Data Set Options. Specify a data set option in parentheses after a SAS data set name. To specify several data set options, separate them with spaces.

CHAPTER 13 Importing and Exporting External Data

OpenVMS Operating Environment

SAS File Management. Improving Performance CHAPTER 37

Introduction. LOCK Statement. CHAPTER 11 The LOCK Statement and the LOCK Command

SAS/ASSIST Software Setup

Graphics. Chapter Overview CHAPTER 4

Chapter 6 Creating Reports. Chapter Table of Contents

Using the SQL Editor. Overview CHAPTER 11

QUEST Procedure Reference

The EXPLODE Procedure

SAS I/O Engines. Definition. Specifying a Different Engine. How Engines Work with SAS Files CHAPTER 36

SAS Support for TELNET on Windows

Chapter 25 PROC PARETO Statement. Chapter Table of Contents. OVERVIEW SYNTAX SummaryofOptions DictionaryofOptions...

Informats. Informats Under UNIX. HEXw. informat. $HEXw. informat. Details CHAPTER 13

Using SAS Files. Introduction CHAPTER 5

Introduction to the OpenVMS Operating Environment

The correct bibliographic citation for this manual is as follows: SAS Institute Inc Proc EXPLODE. Cary, NC: SAS Institute Inc.

Windows: SPX Access Method

SAS Data Libraries. Definition CHAPTER 26

Macro Facility. About the Macro Facility. Automatic Macro Variables CHAPTER 14

DBLOAD Procedure Reference

Tasks Menu Reference. Introduction. Data Management APPENDIX 1

Using Unnamed and Named Pipes

Allocating External Files

Chapter 2 User Interface Features. networks Window. Drawing Panel

Introduction. CHAPTER 3 Working in the SAS Windowing Environment

OS/2: SPX Access Method

Choosing the Right Procedure

Chapter 23 Animating Graphs. Chapter Table of Contents ANIMATING SELECTION OF OBSERVATIONS ANIMATING SELECTED GRAPHS...347

Batch Importing. Overview CHAPTER 4

SCL Arrays. Introduction. Declaring Arrays CHAPTER 4

SAS Catalogs. Definition. Catalog Names. Parts of a Catalog Name CHAPTER 32

Using Dynamic Data Exchange

SAS. IT Service Level Management 2.1: Migration Documentation

Chapter 27 Saving and Printing Graphics

SAS Web Infrastructure Kit 1.0. Overview

UNIX Spawner Program. Starting the UNIX Spawner Program CHAPTER 36

Examples That Use Remote Objecting

Changes and Enhancements

OS/390 Platform Examples

The SERVER Procedure. Introduction. Syntax CHAPTER 8

Alternative ODS HTML Statements for Running Examples in Different Operating Environments

Optimizing System Performance

Overview. CHAPTER 2 Using the SAS System and SAS/ ASSIST Software

Procedures. Calls any BMDP program to analyze data in a SAS data set

SAS/FSP 9.2. Procedures Guide

Chapter 7 File Access. Chapter Table of Contents

Locking SAS Data Objects

Handling Exceptions. Introduction. Using the Program Halt Handler CHAPTER 10

CHAPTER 7 Using Other SAS Software Products

Managing SAS Output. Printing CHAPTER 5

Informats. SAS Informats under OpenVMS. Reading Binary Data CHAPTER 15

CHAPTER 7 Examples of Combining Compute Services and Data Transfer Services

SAS Simulation Studio 14.1: User s Guide. Introduction to SAS Simulation Studio

The G4GRID Procedure. Introduction APPENDIX 1

Loading Data. Introduction. Understanding the Volume Grid CHAPTER 2

CHAPTER 5 Macintosh: TCP/IP Access Method

SAS Strategy Management 5.2 Batch Maintenance Facility

Licensing SAS DataFlux Products

USER TRAINING AND SUPPORT

SAS Workflow Manager 2.2: Administrator s Guide

The FORMS Procedure. Overview CHAPTER 20

SAS Drug Development 3.3_03. December 14, 2007

Functions and CALL Routines

DATA Step Debugger APPENDIX 3

Defining Your Data Sources

SAS Drug Development. SAS Macro API 1.3 User s Guide

Chapter 41 SAS/INSIGHT Statements. Chapter Table of Contents

10 The First Steps 4 Chapter 2

Chapter 25 Editing Windows. Chapter Table of Contents

Using MDP Extensions. What Is the Multidimensional Data Provider? CHAPTER 3

Chapter 28 Command Reference. Chapter Table of Contents TSVIEW COMMAND FORECAST COMMAND

Performance Considerations

SAS Data Integration Studio 3.3. User s Guide

Installation Instructions for SAS/ACCESS Interface to SAP BW

Introduction to MDDBs

Chapter 9 Selected Examples. Queues with Reneging

The TIMEPLOT Procedure

Chapter 14 Introduction to the FACTEX Procedure

Changes and Enhancements

UNIX Platform Error Messages

Chapter 13 Multivariate Techniques. Chapter Table of Contents

SAS/ACCESS Interface to R/3

Transcription:

187 CHAPTER 8 Routing the SAS Log and SAS Procedure Output Introduction 187 Attributes of the SAS Log and Procedure Output Files 188 Controlling Log and Output Destinations 188 Windowing Environment Mode 189 Routing the Log to a Printer 189 Routing the Log to a Disk File 189 Routing Procedure Output to a Printer 189 Routing Procedure Output to a Disk File 190 Interactive Line Mode 191 Routing the Log to a Printer 191 Routing the Log to a Disk File 191 Routing Procedure Output to a Printer 191 Routing Procedure Output to a Disk File 192 Noninteractive Mode 192 Routing the Log to a Display 193 Routing the Log to a Printer 193 Routing the Log to a Disk File 193 Routing Procedure Output to a Display 194 Routing Procedure Output to a Printer 194 Routing Procedure Output to a Disk File 194 Batch Mode 195 Using the PRTFILE Command 196 Introduction For each SAS job, process, or session, the SAS System automatically creates the SAS log file and the WORK data library. (For a discussion of the WORK data library, see The WORK Data Library under OpenVMS on page 32.) If procedures in the SAS program produce printed output, then SAS also creates the procedure output file. The procedure output file is often called the listing file. If they are stored as disk files, the SAS log and procedure output files usually have file types of.log and.lis, respectively. The SAS log and procedure output files have default destinations, but you can control these defaults by using SAS system options and the PRINTTO procedure. This section describes how to choose output destinations (terminal, printer, or disk file) from the various modes of running SAS. Note: When you send your log or procedure output to a printer from the SAS windowing environment, you can use the FSFORM command to invoke the FORM window to set your default printer destination, page format, and so on. For more information about the OpenVMS specifics of the FSFORM command, see Host-Specific

188 Attributes of the SAS Log and Procedure Output Files 4 Chapter 8 Frames of the FORM Window on page 240. For general information about the FSFORM command, refer to the SAS online Help. 4 Attributes of the SAS Log and Procedure Output Files The physical line size (number of columns per line) and the page size (number of lines per page) of the SAS log and procedure output files depend on the destination of the file. If these files appear on your display, then the default line size and page size are derived from the size of your display. For example, on a display device, the default line size is dependent on the window size determined by X resources. If these files are sent to the system printer or written to a disk file (.LOG or.lis), then the default line size is 132 characters, and the default page size is 60 lines. You can change these defaults with the LINESIZE= and PAGESIZE= system options. The value of LINESIZE= can range from 64 to 256; the value of PAGESIZE= can range from 15 to 32767. Note: You can change the line size or page size either when you invoke the SAS System or during your session with the OPTIONS statement. 4 The.LOG and.lis files have the following OpenVMS file attributes: 3 file organization: sequential 3 record format: variable length 3 record attributes: FORTRAN carriage control. Controlling Log and Output Destinations Each method of running the SAS System has a default destination for the SAS log and procedure output files, but you can override these defaults with either SAS system options (when you invoke the SAS System) or the PRINTTO procedure (while you are running the SAS System). Two system options control the destination of the SAS log: LOG= and ALTLOG=. Two similar options control the destination of procedure output: PRINT= and ALTPRINT=. The LOG= and PRINT= system options change the default destination of the SAS log and procedure output; the output does not appear at the original default destination. The ALTLOG= and ALTPRINT= system options send a copy of the output to the new destination; the output also appears at the original default destination. These options can only be specified when you invoke SAS or a new SAS process. If you want to reroute the SAS log or the procedure output after you enter your SAS session, you can use the PRINTTO procedure with the LOG= and PRINT= statement options. Unlike the ALTLOG= and ALTPRINT= system options, the PRINTTO procedure does not send the output to both the new and default destinations; only the specified destination receives output. You must use the PROC PRINTTO statement before the SAS log entries or procedure output you want to route are generated. When you want the output to revert to the default destination, use a PROC PRINTTO statement with no statement options. The following sections describe the default destinations for the SAS log and procedure output file for each method of running the SAS System, and they explain how to send these files to a display, printer, or disk file.

Routing the SAS Log and SAS Procedure Output 4 Windowing Environment Mode 189 Windowing Environment Mode In the windowing environment, the SAS log is automatically routed to the LOG window, and the procedure output is automatically routed to the OUTPUT window. The LOG= and PRINT= system options are ignored in the windowing environment. Routing the Log to a Printer To send the SAS log to a printer from the windowing environment, choose from the PRINT This command, issued from the LOG window command line, sends the contents of the LOG window to the default system printer (SYS$PRINT). You can also use the PRTFILE command, which is described in Using the PRTFILE Command on page 196. $ SAS/ALTLOG=SYS$PRINT This SAS command sends a copy of the SAS log to the SYS$PRINT printer queue and to the default destination (LOG window). If you want to send the copy to a different printer, you must redefine the SYS$PRINT logical name. PROC PRINTTO LOG=fileref; This procedure statement sends any following SAS log entries to the default system printer during a SAS session. You must have defined fileref in a FILENAME statement or function with the PRINTER device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. Routing the Log to a Disk File To send the SAS log to a disk file from the windowing environment, choose from the FILE file-specification This command, issued from the command line of the LOG window, sends a copy of the window s contents to the file associated with file-specification. For more information about the FILE command, see FILE on page 228. $ SAS/ALTLOG=file-specification This SAS command sends a copy of the SAS log to the disk file file-specification, as well as to the default destination (LOG window). The following is an example of this command: $ SAS/ALTLOG=MYLOG.LOG PROC PRINTTO LOG=file-specification; This procedure statement sends any following SAS log entries to the disk file associated with file-specification during a SAS session. The value for file-specification can be any valid external file specification discussed in Routing Procedure Output to a Printer To send the procedure output to a printer from the windowing environment, choose from the

190 Windowing Environment Mode 4 Chapter 8 PRINT This command, issued from the OUTPUT window command line, sends the contents of the OUTPUT window to the default system printer (SYS$PRINT). See your system manager for the location of your default printer. You can also use the PRTFILE command. For more information, see Using the PRTFILE Command on page 196. P selection-field command When issued from the OUTPUT MANAGER window, this selection-field command sends the procedure output to the default system printer. Also, you can edit your output from the OUTPUT MANAGER EDIT window and then send the modified output to the printer. For more information about the OUTPUT MANAGER window, refer to the SAS online Help. $ SAS/ALTPRINT=SYS$PRINT This SAS command sends a copy of the procedure output to the SYS$PRINT printer queue and to the default destination (OUTPUT window). If you want to send the procedure output to a different printer, you must redefine the SYS$PRINT logical name. PROC PRINTTO PRINT=fileref; This procedure statement sends any following procedure output to the default system printer during a SAS session. You must have defined fileref in a FILENAME statement or function with the PRINTER device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. Routing Procedure Output to a Disk File To send the procedure output to a disk file from the windowing environment, choose from the FILE file-specification When issued from the command line of the OUTPUT window, this command sends a copy of the window s contents to the file associated with file-specification. For more information about the FILE command, see FILE on page 228. F selection-field command When issued from the OUTPUT MANAGER window, this selection-field command brings up a requestor window that asks for the filename and allows you to specify attributes such as REPLACE or APPEND. Also, you can edit your procedure output from the OUTPUT MANAGER EDIT window and then send the modified output to a file. For more information about the OUTPUT MANAGER window, refer to the SAS online Help. $ SAS/ALTPRINT=file-specification This SAS command sends a copy of the procedure output to the disk file file-specification and to the default destination (OUTPUT window). The following is an example of this command: $ SAS/ALTPRINT=MYPROG.LIS PROC PRINTTO PRINT=file-specification; This procedure statement sends any following procedure output to the disk file associated with file-specification during a SAS session. The value for file-specification can be any valid external file specification discussed in

Routing the SAS Log and SAS Procedure Output 4 Interactive Line Mode 191 Interactive Line Mode If you run your SAS program in interactive line mode, the SAS log and procedure output appear on the display by default. SAS statements from your program, the SAS log, and procedure output (if the program produces any) are interleaved on the display according to the order of DATA and PROC steps in your program. Routing the Log to a Printer To send the SAS log to a printer in interactive line mode, choose from the following methods: $ SAS/NODMS/LOG=SYS$PRINT This SAS command sends the SAS log to the SYS$PRINT printer queue instead of the default destination (the display). If you want to send the log to a different printer, you must redefine the SYS$PRINT logical name. $ SAS/NODMS/ALTLOG=SYS$PRINT This SAS command sends a copy of the SAS log to the SYS$PRINT printer queue and to the default destination (the display). If you want to send the log to a different printer, you must redefine the SYS$PRINT logical name. PROC PRINTTO LOG=fileref; This procedure statement sends any following SAS log entries to the default system printer during a SAS session. You must have defined fileref in a FILENAME statement or function with the PRINTER device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. Routing the Log to a Disk File To send the SAS log to a disk file in interactive line mode, choose one of the following methods: $ SAS/NODMS/LOG=file-specification This SAS command sends the SAS log to the disk file file-specification instead of the default destination (the display). The following is an example of this command: $ SAS/NODMS/LOG=MYLOG.LOG $ SAS/NODMS/ALTLOG=file-specification This SAS command sends a copy of the SAS log to the disk file file-specification and to the default destination (the display). The following is an example of this command: $ SAS/NODMS/ALTLOG=MYLOG.LOG PROC PRINTTO LOG=file-specification; This procedure statement sends any following SAS log entries to the disk file associated with file-specification during a SAS session. The value for file-specification can be any valid external file specification discussed in Routing Procedure Output to a Printer To send the procedure output to a printer in interactive line mode, choose from the

192 Noninteractive Mode 4 Chapter 8 $ SAS/NODMS/PRINT=SYS$PRINT This SAS command sends the procedure output to the SYS$PRINT printer queue instead of to the default destination (the display). If you want to send the procedure output to a different printer, you must redefine the SYS$PRINT logical name. $ SAS/NODMS/ALTPRINT=SYS$PRINT This SAS command sends a copy of the procedure output to the SYS$PRINT printer queue and to the default destination (the display). If you want to send the procedure output to a different printer, you must redefine the SYS$PRINT logical name. PROC PRINTTO PRINT=fileref; This procedure statement sends any following procedure output to the default system printer during a SAS session. You must have defined fileref in a FILENAME statement or function with the PRINTER device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. Routing Procedure Output to a Disk File To send the procedure output to a disk file in interactive line mode, choose from the $ SAS/NODMS/PRINT=file-specification This SAS command sends the procedure output to the disk file file-specification instead of to the default destination (the display). The following is an example of this command: $ SAS/NODMS/PRINT=MYPROG.LIS $ SAS/NODMS/ALTPRINT=file-specification This SAS command sends a copy of the procedure output to the disk file file-specification and to the default destination (the display). The following is an example: $ SAS/NODMS/ALTPRINT=MYPROG.LIS PROC PRINTTO PRINT=file-specification; This procedure statement sends any following procedure output to the disk file associated with file-specification during a SAS session. The value for file-specification can be any valid external file specification discussed in Noninteractive Mode In noninteractive mode, the default destination for the log is the disk file program-name.log, where program-name is the name of the file that contains the submitted SAS statements. The default destination for the procedure output is a disk file named program-name.lis. For example, if you run your SAS program in noninteractive mode using the following command, the SAS log is automatically directed to a file named PROGNAME.LOG and the procedure output is written to a file named PROGNAME.LIS: $ SAS PROGNAME Both files are written in the default directory.

Routing the SAS Log and SAS Procedure Output 4 Noninteractive Mode 193 Routing the Log to a Display To send the SAS log to a display in noninteractive mode, choose from the following methods: $ SAS/LOG=SYS$OUTPUT program-name This SAS command sends the SAS log to your display instead of the default destination (program-name.log file). $ SAS/ALTLOG=SYS$OUTPUT program-name This SAS command sends a copy of the SAS log to your display and to the default destination (program-name.log file). PROC PRINTTO LOG=fileref; This procedure statement sends the SAS log to your display during a noninteractive job. You must have defined fileref in a FILENAME statement or function with the TERMINAL device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. Routing the Log to a Printer To send the SAS log to a printer in noninteractive mode, choose from the following methods: $ SAS/LOG=SYS$PRINT program-name This SAS command sends the SAS log to the SYS$PRINT printer queue instead of the default destination (program-name.log file). If you want to send the log to a different printer, you must redefine the SYS$PRINT logical name. $ SAS/ALTLOG=SYS$PRINT program-name This SAS command sends a copy of the SAS log to the SYS$PRINT printer queue and to the default destination (program-name.log file). If you want to send the log to a different printer, you must redefine the SYS$PRINT logical name. PROC PRINTTO LOG=fileref; This procedure statement sends the SAS log to a printer during a noninteractive job. You must have defined fileref in a FILENAME statement or function with the PRINTER device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. You can also use the DCL PRINT command to send the program-name.log file to the printer after a noninteractive job finishes. Routing the Log to a Disk File To send the SAS log to a disk file in noninteractive mode, choose one of the following methods: $ SAS/LOG=file-specification program-name This SAS command sends the SAS log to the file file-specification instead of the default destination (program-name.log file). The following is an example of this command: $ SAS/LOG=MYLOG.LOG PROG1 $ SAS/ALTLOG=file-specification program-name This SAS command sends a copy of the SAS log to the disk file file-specification and to the default destination (program-name.log file). The following is an example of this command:

194 Noninteractive Mode 4 Chapter 8 $ SAS/ALTLOG=MYLOG.LOG PROG1 PROC PRINTTO LOG=file-specification; This procedure statement sends any following SAS log entries to the disk file associated with file-specification during a noninteractive job. The value for file-specification can be any valid external file specification, as discussed in Routing Procedure Output to a Display To send the procedure output to a display in noninteractive mode, choose from the $ SAS/PRINT=SYS$OUTPUT program-name This SAS command sends the procedure output to your display instead of the default destination (program-name.lis file). $ SAS/ALTPRINT=SYS$OUTPUT program-name This SAS command sends a copy of the procedure output to your display and to the default destination (program-name.lis file). PROC PRINTTO PRINT=fileref; This procedure statement sends the procedure output to your display during a noninteractive job. You must have defined fileref in a FILENAME statement or function with the TERMINAL device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. Routing Procedure Output to a Printer To send the procedure output to a printer in noninteractive mode, choose from the $ SAS/PRINT=SYS$PRINT program-name This SAS command sends the procedure output to the SYS$PRINT printer queue instead of the default destination (program-name.lis file). If you want to send the procedure output to a different printer, you must redefine the SYS$PRINT logical name. $ SAS/ALTPRINT=SYS$PRINT program-name This SAS command sends a copy of the procedure output to the SYS$PRINT printer queue and to the default destination (program-name.lis file). If you want to send the procedure output to a different printer, you must redefine the SYS$PRINT logical name. PROC PRINTTO PRINT=fileref; This procedure statement sends the procedure output to a printer during a noninteractive job. You must have defined fileref in a FILENAME statement or function with the PRINTER device-type keyword. For more information, see the procedure PRINTTO on page 346 and Device-Type Keywords on page 360 in the FILENAME statement. You can also use the DCL PRINT command to send the program-name.lis file to the printer after a noninteractive job finishes. Routing Procedure Output to a Disk File To send the procedure output to a disk file in noninteractive mode, choose one of the

Routing the SAS Log and SAS Procedure Output 4 Batch Mode 195 $ SAS/PRINT=file-specification program-name This SAS command sends the procedure output to the disk file file-specification instead of the default destination (program-name.lis file). The following is an example of this command: $ SAS/PRINT=MYPROG.LIS PROG1 $ SAS/ALTPRINT=file-specification program-name This SAS command sends a copy of the procedure output to the file file-specification and to the default destination (program-name.lis file). The following is an example of this command: $ SAS/ALTPRINT=MYPROG.LIS PROG1 PROC PRINTTO PRINT=file-specification; This procedure statement sends any following procedure output to the disk file associated with file-specification during a noninteractive job. The value for file-specification can be any valid external file specification discussed in Batch Mode The default for handling output in batch mode is similar to noninteractive mode. When you invoke SAS in batch mode, the SAS log is written to a file with OpenVMS file type.log, and the procedure output is written to a file with OpenVMS file type.lis in the default directory of the command procedure within which SAS was invoked. Typically, the default directory for a batch job is the SYS$LOGIN directory. You can change the default by using a SET DEFAULT command in the BATCH command file. The filename for the.log and.lis files is the name of the SAS program file that you specified in the SAS command. In addition to the.log and.lis files that are created for SAS output, the OpenVMS system also creates an OpenVMS log file in batch mode. The OpenVMS batch log is named command-file.log, where command-file is the command procedure that you submitted for execution. Do not confuse the OpenVMS log with the SAS log. Both have the OpenVMS file type.log, but the OpenVMS log contains commands and messages that are generated by OpenVMS when it processes any batch job, including a SAS batch job. The SAS log contains statements and messages that are generated by the SAS System. CAUTION: Do not give your SAS program and the command procedure the same name. This causes confusion when the OpenVMS and SAS logs are created. If this does occur, the OpenVMS log is created first (for example MYPROG.LOG;1) and the SAS log is created second (MYPROG.LOG;2). If you cannot keep more than one version of a file, the OpenVMS batch log is overwritten with the SAS log. 4 You can send the SAS log and procedure output to a printer instead of to the default.log and.lis files. To redirect the SAS log and procedure output to the system printer, use SYS$PRINT as the value for the LOG=, ALTLOG=, PRINT=, and ALTPRINT= system options, where appropriate. You can also use the DCL PRINT command to send the.log and.lis files to the printer after a batch job has finished.

196 Using the PRTFILE Command 4 Chapter 8 Using the PRTFILE Command The PRTFILE command enables you to change the control information for a file that you are routing to a printer. For example, if you want to send a file to a printer queue other than the default, submit the following FILENAME statement: filename woutput printer queue=myqueue; Then you can issue the following series of commands from the command line of a window to send the contents of the window to the MYQUEUE printer queue: prtfile woutput print free After you issue the PRTFILE command, a note in the SAS log indicates that the output was sent to a file named SAS nnnn.dat. This is a temporary file that is deleted when you issue the PRINT command. As another example, the following FILENAME statement associates the fileref MYFILE with the external file [MYDIR]SPECIAL.SAS and specifies that the carriage-control format is FORTRAN: filename myfile [mydir]special.sas cc=fortran; Then the following series of commands from the command line of a window sends the contents of the window to the external file SPECIAL.SAS: prtfile woutput print myfile free Note: Do not use the PRTFILE command with the FSFORM command. For information about the FSFORM command, see Host-Specific Frames of the FORM Window on page 240. 4

The correct bibliographic citation for this manual is as follows: SAS Institute Inc., SAS Companion for the OpenVMS Environment, Version 8, Cary, NC: SAS Institute Inc., 1999. 518 pp. SAS Companion for the OpenVMS Environment, Version 8 Copyright 1999 by SAS Institute Inc., Cary, NC, USA. 1 58025 526 4 All rights reserved. Printed in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, by any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of the software by the government is subject to restrictions as set forth in FAR 52.227 19 Commercial Computer Software-Restricted Rights (June 1987). 1st printing, October 1999 SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies. The Institute is a private company devoted to the support and further development of its software and related services. SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.