When multiple servers are involved in a network, naming DDM files with location-specific file names can reduce confusion about which target server is being accessed for a file that has a commonly used name.
For example, for an inventory file that may be named INVEN on multiple servers, using location-specific names such as NYCINVEN, STLINVEN, and DALINVEN for the DDM files on the local server to access files in New York City, St. Louis, and Dallas helps you to access the correct file.
Using an abbreviation or code that identifies the destination target server as part of the DDM file names makes it easier to remember where the desired remote file is located.
For non-iSeries™ remote files that have record formats, using the same name for the DDM file as for the record format can also be useful.