Chapter Contents |
Previous |
Next |
SAS Companion for the Microsoft Windows Environment |
All permanent and temporary SAS files are stored in SAS data libraries. To use a SAS data library in your SAS session, you must assign a libref (library reference) and an engine to the data library. The libref is the name you use to refer to the data library during a SAS session or job. You can programmatically define it with an environment variable or with the LIBNAME statement or function. For a complete explanation of librefs, see SAS Language Reference: Concepts. The SAS Explorer window provides an easy way to manage all of your SAS files, including librefs. For information about working with SAS files in the SAS Explorer window, see Getting Started with the SAS System. For information on using librefs in the Windows environment, see Using Data Libraries
The engine identifies the set of routines that the SAS System uses to access the files in the data library. With this architecture, data can reside in different types of files, including SAS data files and data formatted by other software products, such as database management systems. By using the appropriate engine for the file type, the SAS System can write to or read from the file. For some types of files, you need to tell the SAS System what engine to use. For others, SAS automatically chooses the appropriate engine. For more details about engines and Multiple Engine Architecture, see SAS Language Reference: Concepts.
Library Engines |
SAS
has two types of library engines: native and interface. These engines support
the SAS data library model. Library engines perform several important functions,
including determining fundamental processing characteristics. For a more
detailed description of library engines, see SAS Language Reference: Dictionary. For examples of using
library engines, see Using Data Libraries.
Native library engines are those engines that access forms of a SAS file created and maintained by the SAS System. Native library engines include the default engine, the compatibility engine, and the transport engine. Native Library Engines lists the acceptable names (and nicknames) for these engines.
Engine Names | Description | |
---|---|---|
default | V8, BASE | accesses Version 8 data files |
Version 7 compatibility | V7 | accesses Version 7 data files |
Release 6 compatibility | V6 | accesses any data file created by Release 6.08 through Release 6.12 |
Release 6.03 and Release 6.04 compatibility | V604 | accesses data files created by Release 6.03 and Release 6.04 |
transport | XPORT | accesses transport files |
Note: This book uses the term default engine to refer to the V8 engine. The V8 engine is the default engine for accessing SAS files under Version 8 of the SAS System unless the default engine is changed with the ENGINE system option. To see the value of the ENGINE system option, select
Tools | Options | System |
Files | SAS Files |
Interface library engines support access to other vendors' files. These engines allow read-only access to BMDP, OSIRIS, and SPSS files. You must specify as part of the LIBNAME statement or function the name of the interface library engine that you want. Interface Library Engines lists the interface engine names:
Name | Description |
---|---|
BMDP | allows read-only access to BMDP files |
OSIRIS | allows read-only access to OSIRIS files |
SPSS | allows read-only access to SPSS files |
For more information about these engines, see
Reading BMDP, OSIRIS and SPSS Files.
Note: It is always more efficient to specify the engine
name than to have the SAS System determine the correct engine.
You can use the ENGINE system option to specify the default engine the SAS System uses when it detects a mixed mode library or a library with no SAS files. The valid values for the ENGINE option are V8, V7, V6, and BASE. By default, the ENGINE option is set to V8. For more information, see the system optionENGINE.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.