Previous Page | Next Page

Using SAS Files

Filename Extensions and Member Types in UNIX Environments

Because SAS needs to distinguish between the different file types, it automatically assigns an extension to each file when it creates the file. Also, because each SAS file is a member of a library, SAS assigns each file a member type.

The following table lists the file extensions and their corresponding SAS member types.

Do not change the file extensions of SAS files.

File extensions determine how SAS accesses files; changing them can cause unpredictable results.  [cautionend]

File Extensions for SAS File Types
Version 6 Version 8, SAS 9

Random Access Files Sequential Access Files Random Access Files Sequential Access Files SAS Member Type Description
.sas .sas .sas .sas .sas SAS program
.lst .lst .lst .lst .lst Procedure output
.log .log .log .log .log SAS log file
.ssdnn (table note 1) .sdqnn .sas7bdat .sas7sdat DATA SAS data file
.snxnn .siqnn .sas7bndx .sas7sndx INDEX Data file index; not treated by the SAS system as a separate file
.sctnn .scqnn .sas7bcat .sas7scat CATALOG SAS catalog
.sspnn .ssqnn .sas7bpgm .sas7spgm PROGRAM Stored program (DATA step)
.ssvnn .svqnn .sas7bvew .sas7svew VIEW SAS view
.ssann .saqnn .sas7bacs .sas7sacs ACCESS Access descriptor file
.sstnn .stqnn .sas7baud .sas7saud AUDIT Audit file
.sfdnn .sfqnn .sas7bfdb .sas7sfdb FDB Consolidation database
.ssmnn .smqnn .sas7bmdb .sas7smdb MDDB Multidimensional database
.sdsnn .soqnn .sas7bods .sas7sods SASODS Output delivery system file
.snmnn .sqnnn .sas7bdmd .sas7sdmd DMDB Data mining database
.sitnn .srqnn .sas7bitm .sas7sitm ITEMSTOR Item store file
.sutnn .suqnn .sas7butl .sas7sutl UTILITY Utility file
.spunn .spqnn .sas7bput .sas7sput PUTILITY Permanent utility file
.ssbnn .sbqnn .sas7bbak .sas7sbak BACKUP Backup file

TABLE NOTE 1:   All Version 6 files end with a two-character code (nn) that identifies sets of compatible SAS files. See Sharing SAS Files in a UNIX Environment for more information. [arrow]

A UNIX directory can store a variety of files, but you might find it more practical to store files in separate directories according to their use. Also, you can keep libraries that are accessed by different engines in the same directory, but this is not recommended. For more information, see Using Multiple Engines for a Library in UNIX Environments.

Previous Page | Next Page | Top of Page