CL command considerations for DDM
Both compiled control language (CL) programs and interactively entered CL commands can refer to DDM files.
Generally, DDM file names can be specified in CL commands anywhere a database file name can be specified for both iSeries™ and non-iSeries target servers. But there are some limitations.
Listed here are some examples of where DDM file names can be specified:
- DDM file names can be specified on many of the database file-related commands, such as the copy, display, and override file commands.
- DDM file names can be specified on the create file commands to access remote source files, but only if the target server is an iSeries server or a System/38™. A DDM file name can be specified on the SRCFILE parameter, and a member name can be specified on the SRCMBR parameter. If the remote source file referred to by the DDM file is not on an iSeries server or a System/38, an error occurs. The considerations for remote iSeries or System/38 source members are the same as for local source members.
- DDM file names can be specified on the FILE parameter of the Declare File (DCLF) command.
When a DDM file name is specified, some commands act on files on the source server, some act on target files, and some parameter values allow you to specify either a source or target file.
Parent topic:
Programming language considerations for DDM
Related concepts
Use CL and DDS with DDM
Operating considerations for DDM
Related reference
DDM-related CL command summary charts