Even if DUMPANALYZER is running with FAMILY substitution in effect, the program initially ignores the FAMILY substitution when it is searching for MCP and program code files referenced in the dump. For those files that it cannot find by this method, DUMPANALYZER searches again, using FAMILY substitution.

Note that you can use the CODEFILE FAMILY command to establish the family for all object code files referenced in the dump. If you use this command, DUMPANALYZER ignores the family names that object code files had at the time of the dump, and also ignores FAMILY substitution.