Chapter Contents |
Previous |
Next |
Moving and Accessing SAS Files across Operating Environments |
Member Type | Version 6 Filename Extension | Version 8 Filename Extension |
---|---|---|
SAS | .sas | .sas |
PROGRAM (DATA step) | .sspnn | .sas7bpgm |
DATA | .ssdnn | .sas7bdat |
INDEX | .snxnn | .sas7bndx |
CATALOG | .sctnn | .sas7bcat |
MDDB | .ssmnn | .sas7bmdb |
DMDB | .snmnn | .sas7bdmd |
PROC SQL view | .snvnn | .sas7bvew |
where: nn is an extension that is used to differentiate among UNIX host architectures. Here are the extensions and UNIX host groups:
SAS Filename Extension nn | UNIX Host Group | Supported by SAS Release | |||
---|---|---|---|---|---|
6.09 | 6.10 | 6.11 | 6.12 | ||
01 | HP-UX | n/a | |||
Sun | n/a | ||||
Solaris | n/a | ||||
AIX | n/a | ||||
MIPS ABI | n/a | n/a | |||
02 | ULTRIX | n/a | n/a | n/a | |
INTEL-ABI | n/a | ||||
04 | COMPAQ Digital UNIX | n/a |
Version 8 and Version 7 filename extensions are identical.
Because data sets are interchangeable among HP-UX, Sun, Solaris, AIX, and MIPS hosts, the creation of a transport file for moving among them is not necessary. Catalogs are interchangeable among HP-UX, Sun, Solaris, and MIPS hosts. However, you must create a transport file in order to move a catalog between an AIX host and any other UNIX host.
Furthermore, you can use the CONTENTS procedure to display information about the data, which identifies the member and the engine that was used to create it.
Here is an excerpt of typical PROC CONTENTS output:
The SAS System The CONTENTS Procedure Data Set Name: TEST.RECORDS Member Type: DATA Engine: V8
The output reports that the data set TEST.RECORDS is a member of type DATA that was created with the V8 engine.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.