Rocky is correct. It's all part of a process to update a client database.
The issue was resolved after IBM delivered a PTF. If IT let's me know what the specific PTF is, I will come back and list it. In case they don't, this is the clue that led us to bring the issue to IBM.
This problem occurred when we tried to rename a physical file that had an SQL materialized query attached to it and we saw the problem when we ran DSPFD against the materialized query before and after the rename.
References to the physical file before the rename included something like this: "FROM LIBRARY/FILE".
After the physical was renamed, the description looked like this: "FROMLIBRARY/NEWFILE".
The net result was that the physical name was changed but not all of the attached dependent files were re-associated correctly since the new SQL syntax being generated by the OS was invalid.