Usage Note 22727: Do you have any examples of creating a transport file with PROC CPORT to move catalogs or a combination of catalogs and data sets from VM/CMS to another destination operating system?
In the following examples, we are assuming you are moving SAS files from
a lower release to a higher release.
- Example 1:
- When exporting SAS catalogs to tape, you can use the following approach. The TAPE option must be used in the PROC CPORT statement. In this example,
the FILENAME statement is used to specify the attributes of the fileref TRAN. Another approach for specifying the attributes of TRAN is to use the CMS FILEDEF statement.
filename tran tape 'tap1' lrecl=80 blksize=8000
recfm=fb label=nl;
libname dept12 'a';
proc cport library=dept12 file=tran memtype=catalog tape;
run;
- Example 2:
- Here we are copying all the catalogs on the B minidisk with the filetype of SASLIB into the transport file GONECATS DATA A. SAS catalogs on VM/CMS have
a prefix of '0' in their filename to distinguish them from SAS data sets and other SAS files. This prefix is added automatically by the SAS System.
Filename Filetype Fm
0GEOAPP SASLIB B1
0PD SASLIB B1
libname saslib 'b';
proc cport library=saslib memtype=catalog
file='gonecats data a';
run;
- Example 3:
- In this example we are copying all the catalogs and data sets in the directory referenced by the libref SASLIB into the transport file GONEALL DATA A.
CONSULT and DELAY are data sets and GEOAPP, PD, and SELLIST are catalogs.
Filename Filetype Fm
CONSULT SASLIB B1
DELAY SASLIB B1
0GEOAPP SASLIB B1
0PD SASLIB B1
0SELLIST SASLIB B1
libname saslib 'b';
proc cport library=saslib file='goneall data a' ;
run;
- Example 4:
- In this example we are copying one catalog, SELLIST, in the directory referenced by the libref SASLIB into the transport file GONECAT DATA A.
libname saslib 'b';
proc cport catalog=saslib.sellist file='gonecat data a';
run;
Operating System and Release Information
| SAS System | Base SAS | CMS | n/a | |
| All | n/a | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Usage Note |
| Priority: | low |
| Topic: | Data Management ==> Administration ==> Migration
|
| Date Modified: | 2008-01-28 13:44:08 |
| Date Created: | 2002-12-16 10:56:51 |