Preventing and Fixing Problems

Verifying Transfer Format and Transport File Attributes

Verify that the communications software that you use to transfer the transport file specifies BINARY format. For example, if you use FTP, you would specify the FTP BINARY command. Here is a sample invocation of FTP:

ftp
> open host
> binary
> get file file
> close
> quit

For details about FTP, see Transferring Files.

Even if your communications software claims to submit transport files in an appropriate format by default, always be certain of binary format by explicitly specifying it. For details about how to specify the transfer format, consult your communications software documentation.

Also, verify the file attributes of the transport file, which are required in order to restore the file at the target computer. Although some target computers might not need file attributes, the transfer method (tape and network) always does. For a list of operating environments that require file attributes, see Attributes for Transport Files. Problems can result when the file attributes that are required by the target operating environment and those applied by the transfer method are incompatible.

Verify file attributes that are required by the target computer. The method to list and specify file attributes varies by computer. See the chapter that is appropriate to your operating environment.

Also verify the file attributes that are set by the transfer method. For example, if using FTP, you set file attributes in an FTP command. Here is a sample invocation of FTP:

ftp
> open host
> binary
> locsite recfm=fb blocksize=8000 lrecl=80
> get file file
> close
> quit

If transferring a transport file across a network, see your communications software documentation. For information about transferring a file via tape, see the topic that is appropriate to your operating environment.

If you can correct the problem, re-create the transport file at the source computer, transfer it to the target computer, and restore the transport file again.

If the problem persists, try to reblock the transport file and try transporting it again. For details, see Reblocking a Transport File.

Top of Page