Transferring a Transport File over the Network

Record Length Issues

In some instances, a transport file that is transferred to a z/OS target machine has the correct file format, but it has an incorrect record length. For recovery actions for this problem, see "Verifying That the Transport File Has Not Been Corrupted" on page 68.

FTP

Here is an FTP example in which the z/OS target machine gets the transport file from the source machine:

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

Here is an FTP example in which the source machine puts the transport file on the z/OS target machine:

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

Note  

In order to transfer a transport file to any directory-based operating environment such as Windows or UNIX, do not use the FTP QUOTE SITE or the FTP LOCSITE command to declare file attributes.

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) 

See your operating environment documentation for details.