This example shows how to use the ALLOW_DDL_CHANGES_WHILE_OPEN QAQQINI option within a specific job to avoid the requirement of needing an exlusive lock for the *FILE object, before making a change to a trigger program.

Change trigger programs in production.sql

--
-- Create, Replace, Delete, or Disable trigger programs 
-- without acquiring an exclusive lock over the file
-- =======
--
-- Resource: ibmsystemsmag.com/blogs/i-can/august-2017/manage-trigger-programs-in-productions

-- Prepare to break the rules
call qsys2.override_qaqqini(1, '', '');
-- Rules broken
call qsys2.override_qaqqini(2,  
                            'ALLOW_DDL_CHANGES_WHILE_OPEN', 
                            '*YES');
 
CREATE OR REPLACE TRIGGER toystore.new_hire 
  AFTER INSERT ON toystore.employee
    FOR EACH ROW MODE DB2SQL
      UPDATE toystore.company_stats
        SET Number_of_employees = Number_of_employees + 1;
        
-- Done breaking the rules
call qsys2.override_qaqqini(3, '', '');

-- Done breaking the rules
call qsys2.override_qaqqini(3, '', '');

Thanks, this is now fixed.

btw...

Resource:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/OVERRIDE_QAQQINI%20procedure

You welcome
Thank you for all these interesting things !