This straight from IBM, though I don't remember exactly where I found it: ============================================================= Create Duplicate Object (CRTDUPOBJ)· When a physical file and its trigger program are originally in the same library, the trigger program library will always be changed to the new library, even if the trigger program doesn't exist in the new library. In addition, the following holds true: o If the CRTDUPOBJ command is duplicating both the physical file and its trigger program to a new library, then the new trigger program will be associated with the new physical file. o If the CRTDUPOBJ command is duplicating only the physical file, then the trigger program with the same program name in the TO library will be associated with the new physical file. This is true even if there is no trigger program by that name in the TO library. The library of the trigger program will be changed. o If the CRTDUPOBJ command is duplicating only the trigger program, then the new trigger program will not be associated with any physical files. · When a physical file and its trigger program are originally in different libraries: o The old trigger program will be associated with the new physical file. Even though the new physical file is duplicated to the same library as the trigger program, the old trigger program will still be associated with the new physical file.
============================================================So my question would be... Does the new file point to a Trigger Program that actually exists ?? I've got a document with a whole list of "Gotchas" regarding Triggers that I'd be happy to share. The info is about 2 years old so hopefully no drastic changes since then.