IBM i Database Trigger Support › Implementing Triggers › CA 2E Trigger Limitations

CA 2E Trigger Limitations

1. Triggers are only supported when the physical files on which trigger is implemented, are present in the generation library, denoted by model value (YGENLIB).
2. When we convert the database from DDS to DDL or SQL, the access path objects get recreated in SQL collection library, denoted by the model value YSQLLIB. However, because of a limitation in trigger processing algorithm, the trigger functionality can only be implemented on access paths present in generation library, denoted by the model value YGENLIB. Therefore, trigger implementation fails when you convert the database from DDS to DDL or SQL and the SQL collection library is different from the Generation Library.

The following lists the steps that you must perform for the trigger functionality to work after converting the database from DDS to DDL/SQL:

1. Ensure that the SQL collection library is same as the Generation library, (that is, both model values YSQLLIB and YGENLIB hold the same value) before regenerating your access paths as DDL or SQL. This ensures that the DDL/SQL type access paths objects are recreated in the same library where the original DDS-based access paths existed.
2. After converting the database to DDL or SQL, delete the trigger reference by using YWRKTRGREF command and choosing option 4=Delete against the access path that is being converted from DDS to DDL/SQL.
3. Rerun the YCVTTRGDTA command.