DDM enables users or application programs on the iSeries server to access data files that reside on remote systems and allows these remote systems to access data on the local system. This remote file access is transparent to the application program command or utility. Remote file requests are routed through a DDM file, which contains the name of the file on the remote system as well as the name of this system as it is known on the network.
There are, however, certain limitations to the DDM support, particularly where printing applications are concerned. For example:
3 > OVRPRTF FILE(QSYSPRT) TOFILE(ITSCID03/DDMQSYSPRT) DDM file DDMSRC in MYLIB uses remote file QSYS/QSYSPRT. File DDMSRC in MYLIB not a data base file. Cannot open DDM file DDMSRC in MYLIB. Function check. CPF4207 unmonitored by QWSGET at statement *N, instruction X'0F9D'. A function check was received while opening the print file. The print operation used the default printer device file.
One way in which data could be printed on a remote iSeries server using DDM is as follows:
CRTDDMF FILE(MYLIB/DDMSRC) RMTFILE(QSYS/QSYSPRT) RMTLOCNAME(B20) TEXT('DDM file for remote printing on B20').
CRTPF FILE(MYLIB/PFILE) RCDLEN(80) TEXT('CPYSPLF data file').
SBMRMTCMD CMD('crtpf file (rlib/rfile) rcdlen(80)') DDMFILE(DDMSRC).
CPYSPLF FILE(QSYSPRT) TOFILE(MYLIB/PFILE) JOB(003049/USER/DSP06).
CPYF FROMFILE(MYLIB/PFILE) TOFILE(MYLIB/DDMSRC) MBROPT(*ADD).
SBMRMTCMD CMD('cpyf fromfile(rlib/rfile) tofile(qsysprt) mbropt(*add)') DDMFILE(DDMSRC).
This procedure can be adapted to direct i5/OS printing to remote System/36™ systems and System/38™ systems with DDM installed. See the Distributed Data Management topic collection for details of the differences in DDM implementation on these other systems.