Moving and Accessing SAS Files across Operating Environments

Transferring a Transport File over the Network for CMS

Examples of transferring a transport file are provided for the FTP and Attachmate Corporation's Extra for Windows.

In some instances, a transport file that is transferred to a CMS target host has the correct file format but an incorrect record length. For recovery actions for this problem, see Preventing and Fixing Problems.

FTP

Here is an FTP example in which the source host puts the transport file on the CMS target host:

ftp
> open target-host
> binary 80 
> quote site recfm=fb blocksize=8000 lrecl=80
> put xportout grades
> close
> quit

Here is an FTP example in which the CMS target host gets the transport file from the source host:

ftp
> open source-host
> binary 80
> locsite recfm=fb blocksize=8000 lrecl=80
> get xportout grades
> close
> quit

Note: In order to transfer a transport file to any directory-based host such as Windows, OS/2, or UNIX, do not declare file attributes with either the FTP QUOTE SITE or the FTP LOCSITE command. [cautionend]

Note: You may consolidate FTP commands by using

binary f 80

instead of BINARY, QUOTE SITE FIXRECFM 80 or LOCSITE FIXRECFM 80 FTP, which are used in the preceding examples. [cautionend]

Attachmate

If you use Extra for Windows, select translation NONE and verify that the File Transfer dialog box contains this information:

send a:grades xportout lrecl(80) blksize(8000) 
 recfm(f) space(10,10)

Consult your documentation for details.

Chapter Contents
Previous
Next
Top of Page