iSeries Access Family transfer function considerations

 

A personal computer user can use the transfer function in iSeries™ Access Family and the DDM support on the local iSeries server to which the personal computer is attached either to transfer data from the personal computer to a remote file, or to transfer data from a remote file to the personal computer.

The remote file must be on an iSeries server or a System/38™.

When DDM is used to transfer files or data from a remote server to an attached personal computer, the DDM files (that refer to remote files) on the local iSeries server cannot be joined with local files to transfer data to the personal computer. (That is, data from files on both the remote and local servers cannot be joined.) However, a DDM file can specify a remote file that is a logical join file built over multiple physical files. DDM files that refer to the same target server and use the same remote location information can be joined.

A transfer request that requires group processing does not work if the local server is a System/38 and the remote server is an iSeries server, or if the local server is an iSeries server and the remote server is a System/38.

When DDM is used to transfer a file or data from an attached personal computer to a remote server, a remote file cannot be created on the target server. The remote file must already exist before the data from the personal computer can be transferred. However, because the target must be an iSeries server or a System/38, a new member can be added in the remote file before personal computer data is transferred to that file member.

 

Parent topic:

iSeries Access Family considerations for DDM