File management handling of DDM files

Because of the way data management handles DDM files, you must be careful when specifying a member name on commands. If a member name is specified, data management first searches for a local database file containing the member specified before looking for a DDM file.

For example, assume the following items:

DDM file CUST021 is in library NYCLIB.
Database file CUST021 is in library CUBSLIB.

NYCLIB is listed before CUBSLIB in the user's library list. CUBSLIB/CUST021 contains member NO1. The remote file pointed to by the DDM file contains member NO1. If the following override is used on an Override with Database File (OVRDBF) command:

OVRDBF FILE(CUST021) MBR(NO1)

Data management finds the database file CUBSLIB/CUST021 instead of the DDM file NYCLIB/CUST021.

To avoid this, you can do one of the following things:

Qualify the TOFILE on the override:

OVRDBF FILE(CUST021) TOFILE(NYCLIB/CUST021) MBR(NO1)

Remove the library containing the database file from the library list:
```
RMVLIBLE LIB(CUBSLIB)
```
Remove the override and change the remote file name in the DDM file to contain the member name:
```
CHGDDMF FILE(NYCLIB/CUST021)
   RMTFILE(*NONSTD 'XYZ/CUSTMAST(NO1)')
```