Other DDM-related functions involving remote files
Besides accessing remote files for data record I/O operations,
other operations related to remote files can be performed. These are briefly
described in these topics.
Lock files and members for DDM
Putting object locks on DDM files and their associated remote files requires special consideration.
Control DDM conversations
Normally, the DDM conversations associated with a source server job are kept active until one of the conditions described in this topic is met.
Display DDM remote file information
The CL commands Display File Description (DSPFD) and Display
File Field Description (DSPFFD) can be used by an iSeries™ source
server user to display the attributes of one or more DDM files on the source
server, or to display the attributes of one or more remote files on a target
server.
Display DDM remote file records
The Display Physical File Member (DSPPFM) command
can be used to display a remote file on a target server.
Use of object distribution
Although DDM file names can be specified on the Send Network
File (SNDNETF) and Receive Network File (RCVNETF) commands,
these commands should be run, whenever possible, on the server where the data
actually exists. Therefore, if both servers are iSeries™ servers
and both are part of a SNADS network, object distribution can
be used instead of DDM to transfer the data between them.
Use of object distribution with DDM
You can also use both SNADS (on iSeries™ servers)
and DDM (on iSeries™ servers and non-iSeries™ servers) to transfer files between iSeries™ servers and servers that are not part
of a SNADS network but have DDM installed.