Global Statements
Definition
Global statements generally provide information to SAS, request information or data, move between different modes of execution, or set values for system options. Other global statements (ODS statements) deliver output in a variety of formats, such as in Hypertext Markup Language (HTML). You can use global statements anywhere in a SAS program. Global statements are not executable; they take effect as soon as SAS compiles program statements.
Other SAS software products have additional global statements that are used with those products. For information, see the SAS documentation for those products.
Global Statements by Category
The following table lists and describes SAS global statements, organized by function into eight categories:
| Statements in this category | let you |
|---|---|
| Data Access | associate reference names with SAS data libraries, SAS catalogs, external files and output devices, and access remote files. |
| Log Control | alter the appearance of the SAS log. |
| ODS: Output Control | choose objects to send to output destinations; edit the output format. |
| ODS: SAS Formatted | apply default styles to SAS specific entities such as a SAS data set, SAS output listing, or a SAS document. |
| ODS: Third-Party Formatted | apply styles to the output objects that are used by applications outside of SAS. |
| Operating Environment | access the operating environment directly. |
| Output Control | add titles and footnotes to your SAS output; deliver output in a variety of formats. |
| Program Control | govern the way SAS processes your SAS program. |
The following table provides brief descriptions of SAS global statements. For more detailed information, see the individual statements.
| Category | Statement | Description |
|---|---|---|
| Data Access | 'CATNAME Statement' on page 1118 | Logically combines two or more catalogs intoone by associating them with a catref (a shortcut name ); clears one or all catrefs; lists the concatenated catalogs in one concatenation or in all concatenations |
| 'FILENAME Statement' on page 1169 | Associates a SAS fileref with an external file or an output device; disassociates a fileref and external file; lists attributes of external files | |
| 'FILENAME Statement, CATALOG Access Method' on page 1176 | References a SAS catalog as an external file | |
| 'FILENAME, CLIPBOARD Access Method' on page 1178 | Enables youto read text data fromand write text data to the clipboard on the host machine. | |
| 'FILENAME Statement, EMAIL (SMTP) Access Method' on page 1181 | Allows you to send electronic mail programmatically from SAS using the SMTP (Simple Mail Transfer Protocol) e-mail interface | |
| 'FILENAME Statement, FTP Access Method' on page 1190 | Enables you to access remote files by using the FTP protocol | |
| 'FILENAME Statement, SOCKET Access Method' on page 1199 | Enables you to read from or write to a TCP/IP socket | |
| 'FILENAME Statement, URL Access Method' on page 1203 | Enables you to access remote files by using the URL access method | |
| 'LIBNAME Statement' on page 1284 | Associates or disassociates a SAS data library with a libref (a shortcut name); clears one or all librefs; lists the characteristics of a SAS data library; concatenates SAS data libraries; implicitly concatenates SAS catalogs. | |
| 'LIBNAME Statement, SAS/ACCESS' on page 1292 | Associates a SAS libref with a database management system (DBMS) database, schema, server, or groupof tables or views | |
| 'LIBNAME Statement for SAS/CONNECT Remote Library Services' on page 1292 | Associates a libref with a SAS data library that is located on the server for client access | |
| 'LIBNAME Statement for the Metadata Engine' on page 1292 | Associates a SAS libref with the metadata that is in a SAS Metadata Repository on the SAS Metadata Server | |
| 'LIBNAME Statement for SAS/CONNECT TCP/IP Pipe' on page 1293 | Associates a libref with a TCP/IP pipe (instead of a physical disk device) for processing input and output. The SASESOCK engine is required for SAS/CONNECT applications that implement MP CONNECT with piping. | |
| 'LIBNAME Statement for SAS/SHARE'on page 1293 | In a client session, associates a libref with a SAS data library that islocated onthe server forclient access. In a server session, pre-defines a server library that clients are permitted to access. | |
| 'LIBNAME Statement for Scalable Performance Data' on page 1293 | Associates a SAS libref with a SAS data library for rapid processing of very large data sets by multiple CPUs | |
| 'LIBNAME Statement for the XML Engine' on page 1293 | Associates a SAS libref with the physical location of an XML document | |
| Log Control | 'Comment Statement' on page 1121 | Documents the purpose of the statement or program |
| 'PAGE Statement' on page 1341 | Skips to a new page in the SAS log | |
| 'SKIP Statement' on page 1404 | Creates a blank line in the SAS log | |
| ODS: Output Control | 'LIBNAME Statement, SASEDOC' on page 1292 | Associates a SAS libref with one or more ODS output objects that are stored in an ODS document |
| 'ODS _ALL_ CLOSE Statement' on page 1330 | Closes all open ODS output destinations, including the Listing destination | |
| 'ODS EXCLUDE Statement' on page 1331 | Specifies output objects to exclude from ODS destinations | |
| 'ODS PATH Statement' on page 1333 | Specifies which locations to search for definitions that were created by PROC TEMPLATE, as well as the order in which to search for them | |
| 'ODS PROCLABEL Statement' on page 1334 | Enables you to change a procedure label | |
| 'ODS PROCTITLE Statement' on page 1335 | Determines whether to suppress the writing of the title that identifies the procedure that produces the results | |
| 'ODS RESULTS Statement' on page 1335 | Tracks ODS output in the Results window | |
| 'ODS SELECT Statement' on page 1336 | Specifies output objects to send to the ODS destinations | |
| 'ODS SHOW Statement' on page 1336 | Writes the specified selection or exclusion list to the SAS log | |
| 'ODS TRACE Statement' on page 1336 | Writes to the SAS log a record of each output object that is created,or suppresses the writing of this record | |
| 'ODS USEGOPT Statement' on page 1337 | Enables graphics option settings | |
| 'ODS VERIFY Statement' on page 1337 | Writes or suppresses a warning that a style definition or a table definition that is used is not supplied by SAS | |
| ODS: SAS Formatted | 'ODS DECIMAL_ALIGN Statement' on page 1330 | Aligns values by the decimal point in numeric columns when no justification is specified |
| 'ODS DOCUMENT Statement' on page 1331 | Creates an ODS document | |
| 'ODS LISTING Statement' on page 1332 | Opens, manages , or closes the LISTING destination | |
| 'ODS OUTPUT Statement ' on page 1333 | Creates a SAS data set from an output object and manages the selection and exclusion lists for the Output destination | |
| ODS: Third-Party Formatted | 'ODS CHTML Statement' on page 1329 | Produces a compact, minimal HTML that does not use style information |
| 'ODS CSVALL Statement' on page 1330 | Produces output that contains columns of data values that are separated by commas. ODS CSVALL produces tabular output with titles, notes, and bylines. | |
| 'ODS DOCBOOK Statement' on page 1330 | Produces XML output that conforms to the DocBook DTD by OASIS | |
| 'ODS HTML Statement' on page 1331 | Opens, manages, or closes the HTML destination, which produces HTML 4.0 embedded stylesheets | |
| 'ODS HTML3 Statement' on page 1332 | Opens, manages, orcloses the HTML3 destination, which produces HTML 3.2 formatted output | |
| 'ODS HTMLCSS Statement' on page 1332 | Produces HTML that is similar to ODS HTML with cascading style sheets | |
| 'ODS IMODE Statement' on page 1332 | Produces HTML that is a column of output, separated by lines | |
| 'ODS MARKUP Statement' on page 1333 | Opens, manages, or closes one or more specified destinations | |
| 'ODS PCL Statement' on page 1333 | Provides portable support for PCL (HP LaserJet) files | |
| 'ODS PDF Statement' on page 1334 | Opens, manages, or closes the PDF destination | |
| 'ODS PHTML Statement' on page 1334 | Produces a basic HTML that uses twelve style elements and no class attributes | |
| 'ODS PRINTER Statement' on page 1334 | Opens, manages, or closes the PRINTER destination | |
| 'ODS PS Statement' on page 1335 | Opens, manages, or closes the PostScript destination | |
| 'ODS RTF Statement' on page 1336 | Creates SAS output for Microsoft Word | |
| 'ODS WML Statement' on page 1337 | Uses the Wireless Application Protocol (WAP) to produce a Wireless Markup Language (WML) DTD with a simple href list fora table of contents | |
| Operating Environment | 'X Statement' on page 1435 | Issues an operating-environment command from within a SAS session |
| Output Control | 'FOOTNOTE Statement' on page 1206 | Writes up to 10 lines of text at the bottom of the procedure or DATA step output |
| 'TITLE Statement' on page 1407 | Specifies title lines for SAS output | |
| Program Control | 'DM Statement' on page 1141 | Submits SAS Program Editor, Log, Procedure Output or text editor commands as SAS statements |
| 'ENDSAS Statement' on page 1152 | Terminates a SAS job or session after the current DATA or PROC step executes | |
| '%INCLUDE Statement' on page 1215 | Brings a SAS programming statement, data lines, or both, into a current SAS program | |
| '%LIST Statement' on page 1297 | Displays lines that are entered in the current session | |
| 'LOCK Statement' on page 1298 | Acquires and releases an exclusive lock on anexisting SAS file | |
| 'OPTIONS Statement' on page 1337 | Changes the value of one or more SAS system options | |
| 'RUN Statement' on page 1387 | Executes the previously entered SAS statements | |
| '%RUN Statement' on page 1388 | Ends source statements following a %INCLUDE * statement | |
| 'SASFILE Statement' on page 1389 | Opens a SAS data set and allocates enough buffers to hold the entire file in memory |
EAN: N/A
Pages: 704