×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
AFAIK, as long as the trigger program is attached to a PF and the file is "open" in any jobs, the database manager (Db2i) will have locked the program object, preventing it from being renamed or deleted "out from under" the database while the file is active.
Once the file is closed and no jobs have any locks on the file, there should also be no locks on the trigger *PGM(s) and you could rename it, or more likely, replace it with a new version.
But if you really wanted to "rename" it, and have it still "work" as a "trigger" then as James suggests, you would need to issue RMVPFTRG, then rename it, then ADDPFTRG to re-attach it to the database physical file with the new object name.
On Monday, October 7, 2019, 5:55:22 PM EDT, <jamesl@xxxxxxxxxxxxxxxxx> wrote:
A trigger is just a program (?) therefore you could use
RNMOBJ
A trigger is also a named attribute of a file. Dunno if there's a way to rename that, short of doing a RMVPFTRG, followed by an ADDPFTRG. Also dunno what effect renaming the program would have.
midrange.com
