The control language (CL) commands that have a specific relationship
with DDM are grouped in charts in these topics to show the command functions
that are available with DDM, those having common limitations when used with
DDM, and those that cannot be used with DDM.
Notes: - Not all of the CL commands on an iSeries™ server are
shown in these topics. Only those that are intended (or recommended) by IBM® for
use with DDM or those specifically not intended for DDM use are shown.
The intended use can be either for commands that are run on the source server
to affect a remote file on the target server, or for commands that are submitted
to the target server by using the Submit Remote Command (SBMRMTCMD) command
to run there.
- Some of these commands appear in more than one of the following charts.
The charts in these topics show:
- Commands affecting only the DDM file:
Object-oriented commands that
can be used with DDM files, but do not affect the associated remote files.
The Create DDM File (CRTDDMF), Change DDM File
(CHGDDMF), and Reclaim DDM Conversations (RCLDDMCNV) commands
are included in this group.
- Commands affecting both the DDM file and the remote file:
- File management commands that require that the target server be another iSeries server or a System/38™.
The SBMRMTCMD command is included in this group.
- Member-related commands that can be used in some way on remote files.
- Source file commands that can operate on source files while DDM is being
used.
These commands, normally used for processing local files, can (transparently
to the programs) process remote files when one of their parameters specifies
the name of a DDM file.
- Commands that cannot be used with DDM.
Many of these commands, when limited as shown in the charts, can
still be submitted by the SBMRMTCMD command to a target
server (an iSeries server or a System/38 only) to run, but it might
not be useful to do so.