This topic covers target considerations for DDM.
As with any database file, DDS might or might not be used to externally describe the attributes of the remote file when it is created on the remote iSeries™ server. If DDS is used, then the source server program uses those attributes when it accesses the remote file (by using the DDM file). If DDS is not used, then the file's attributes must be described in the program.
When a source server program that accesses a file on a target iSeries server is compiled (or recompiled), the existing DDM file is used to establish communications with the target server, and the remote file is actually accessed during compilation to extract its file and record attributes. Whether DDS is used to describe the file or not, level check identifiers are created during compilation and are included in the compiled program. These values are then used when the program is run and LVLCHK(*RMTFILE) is in effect for the DDM file.
Whether DDS is used to describe a remote iSeries file or not, a source server program can have its own field and record format definitions provided in the program, or the program can substitute the definitions of another source server file that is created using DDS. Either can be done if LVLCHK(*NO) is in effect in the DDM file or specified in an Override with Database File (OVRDBF) command used at program run time. LVLCHK(*NO) need only be used when the record format used on the source server is different than that of the remote iSeries file.