SAS Procedures under Windows

CIMPORT Procedure: Windows

Restores a transport file created by the CPORT procedure.

Windows specifics:	Name and location of transport file
See:	CIMPORT Procedure in Base SAS Procedures Guide

Syntax
Details
See Also

Syntax

PROC CIMPORT destination=libref| <libref.>member-name <option(s)>;

Note: This is a simplified version of the CIMPORT procedure syntax. For the complete syntax and its explanation, see the CIMPORT procedure in Base SAS Procedures Guide. [cautionend]

destination: identifies the file(s) in the transport file as a single SAS data set, single SAS catalog, or multiple members of a SAS library.
libref | <libref.>member-name: specifies the name of the SAS data set, catalog, or library to be created from the transport file.

Details

The CIMPORT procedure imports a transport file that was created (exported) by the CPORT procedure.

Coupled with the CPORT procedure, the CIMPORT procedure enables you to move catalogs and data sets from one operating environment to another.

Note: PROC CIMPORT processes a file generated by PROC CPORT, not a transport file generated by the XPORT engine. [cautionend]

Note: You can use the MIGRATE procedure, beginning with SAS 9.1, to migrate a SAS library from a previous release. [cautionend]

When you use the CIMPORT procedure under Windows, remember the following:

The value of the INFILE= option can be a fileref defined in a FILENAME statement, a quoted Windows pathname, or an environment variable.
If you omit the INFILE= option and have not defined the reserved fileref SASCAT, SAS tries to read from a file named SASCAT.DAT in your working directory. If no file by that name exists, the following error message is issued and the procedure terminates, assuming that C:\SAS has been defined as the working directory:
```
ERROR:
Physical file does not exist, C:\SAS\SASCAT.DAT
```
If you have not transferred the file created by PROC CPORT in binary format, PROC CIMPORT cannot read the file, and you receive the following message:
```
ERROR: Given transport
file is bad.
```