Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| Moving and Accessing SAS Files across Operating Environments |
Consider a cross-version environment in which a SAS/SHARE client accesses files on a SAS/SHARE server, with each running a different SAS version from the other. These factors determine your ability to access (read, write, or update) a file in such an environment:
| Accessing Data Sets in a Cross-Version Environment |
Accessing Data Sets in a Cross-Version Environment summarizes the permissions to access data sets in a cross-version environment.
|
|
V6 Server | V8 or V7 Server | ||
|---|---|---|---|---|
| V6 Data Set | V7 or V8 Data Set | V6 Data Set | V8 or V7 Data Set | |
| V6 Client | RWU | No Access | RWU | RWU¹ |
| V8 or V7 Client | RWU¹ | No Access | RWU¹ | RWU |
RWU means that read, write, and update access is supported. A Version 6 client's ability to recognize Version 7 or Version 8 files on a Version 7 server or Version 8 server is determined by the server's base engine.
No Access means that neither read, write, nor update access is supported.
| ¹ indicates that features that are specific to Version 7 and Version 8 , such as long names, are not supported. |
| Accessing DATA Step and PROC SQL Views in a Cross-Version Environment |
Accessing DATA Step Views and PROC SQL Views in a Cross-Version Environment summarizes the permissions to access DATA step views and PROC SQL views in a cross-version environment.
| V6 Server | V8 or V7 Server | |||
|---|---|---|---|---|
| V6 View | V8 or V7 View | V6 View | V8 or V7 View | |
| V6 Client | RWU | No Access | RWU¹ | R² |
| V8 or V7 Client | R² | No Access | R³ | RWU |
In this table, View refers to DATA step views and PROC SQL views only.
RWU means read, write, and update access is supported.
No Access means that neither read, write, nor update access is supported.
| ¹ At either the client or the server, the RMTVIEW=NO option and the argument to the LIBNAME statement has been set. For more information about this option, see Deciding Where Views Should Be Interpreted. | |
| ² At either the client or the server, the RMTVIEW=YES option and the argument to the LIBNAME statement has been set. For more information about this option, see Deciding Where Views Should Be Interpreted. | |
| ³ Applies to PROC SQL views only. |
| Accessing SAS/ACCESS Views in a Cross-Version Environment |
Accessing SAS/ACCESS Views in a Cross-Version Environment summarizes the permissions to access SAS/ACCESS views in a cross-version environment.
| V6 Server | V8 or V7 Server | |||
|---|---|---|---|---|
| V6 Data Set | V8 or V7 Data Set | V6 Data Set | V8 or V7 Data Set | |
| V6 Client | RWU | No Access | RWU | RWU |
| V8 or V7 Client | RWU | No Access | RWU | RWU |
RWU means that read, write, and update access is supported.
No Access means that neither read, write, nor update access is supported.
| Accessing Catalogs in a Cross-Version Environment |
Accessing Catalogs in a Cross-Version Environment summarizes the permissions to access catalogs in a cross-version environment.
| V6 Server | V8 or V7 Server | |||
|---|---|---|---|---|
| V6 Catalog | V8 or V7 Catalog | V6 Catalog | V8 or V7 Catalog | |
| V6 Client | RWU | No Access | R | RWU¹ |
| V8 or V7 Client | RW² | No Access | RW² | RWU |
RWU means that read, write, and update access is supported.
No Access means that neither read, write, nor update access is supported.
| ¹ indicates that this update operation produces a Version 8 or Version 7 catalog that contains Version 6 data. | |
| ² indicates that this write operation allows only a limited copy. You can use PROC COPY to copy a V6 catalog to another V6 library. |
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.