Chapter Contents |
Previous |
Next |
Moving and Accessing SAS Files across Operating Environments |
Because these methods produce transport files whose formats are different, you cannot mix methods to create and then to restore the transport file. The methods that you use must be identical or be a compatible pair. For example, you can create and restore a transport file using the XPORT engine and PROC COPY or the DATA step at both the source and target hosts. Likewise, you can create a transport file using PROC CPORT at the source host, and you can import the transport file using PROC CIMPORT at the target host. However, you cannot, for example, create a transport file using the XPORT engine and PROC COPY at the source host and then try to use PROC CIMPORT to import the transport file at the target host.
Determining Which Method Was Used to Create the Transport File |
Use a text editor or an operating system read or view command to read the file.
The XPORT engine creates a file whose first 40 characters contain this ASCII text:
HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!00
PROC CPORT creates a file whose first 40 characters contain this ASCII text:
**COMPRESSED** **COMPRESSED** **COMPRESSED** **COM
Note: If you set the NOCOMPRESS option to PROC CPORT,
compression is suppressed, which prevents the display of the preceding text
in a transport file.
For technical details about the transport format that is used for a data set, see Technical Support article TS-140, The Record Layout of a SAS Transport Data Set.
Transport files that are created on hosts that represent character data in EBCDIC (OS/390 and CMS) are not readable. For details about how to interpret ASCII data on EBCDIC hosts, see Interpreting EBCDIC as ASCII Data.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.