Verify that the communications software that you use to transfer the transport file is in BINARY format. If you use FTP, for example, you would explicitly enter 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 Chapter 6, "Transferring Files," on page 37.
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 operating environment. Although some target operating environments might not need file attributes, the transfer method (tape and network) always does. See "Attributes for Transport Files" on page 37 for a list of operating environments that require file attributes. 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 operating environment. How you list and set file attributes varies by operating environment. See the appropriate operating environment chapter for this information.
Also verify the file attributes that the transfer method sets. 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 by means of tape, see the appropriate operating environment chapter.
If you can correct the problem, re-create the transport file at the source operating environment, transfer it to the target, and restore it again.
If the problem persists, try to reblock the transport file and try transporting it again. See "Reblocking a Transport File" on page 78.