Grofaty,
According to the manual, no you cannot do that. This is what is allowed:
---------------------------------
SQL-procedure-statement
The SQL-procedure-statement can contain a dynamic compound statement or any of the SQL control statements listed in "Compound SQL (Dynamic)".
If the trigger is a BEFORE trigger, an SQL-procedure-statement can also include one of the following:
* a fullselect (A common-table-expression may precede a fullselect.)
* a SET variable statement.
If the trigger is an AFTER trigger or an INSTEAD OF trigger, an SQL-procedure-statement can also include one of the following:
* an INSERT SQL statement (not using nicknames)
* a searched UPDATE SQL statement (not using nicknames)
* a searched DELETE SQL statement (not using nicknames)
* 2a MERGE statement
* a SET variable statement
* a fullselect (A common-table-expression may precede a fullselect.)
The SQL-procedure-statement must not contain a statement that is not supported (SQLSTATE 42987).
The SQL-procedure-statement cannot reference an undefined transition variable (SQLSTATE 42703), a federated object (SQLSTATE 42997), or a declared temporary table (SQLSTATE 42995).
The SQL-procedure-statement in a BEFORE trigger cannot reference a materialized query table defined with REFRESH IMMEDIATE (SQLSTATE 42997).
The SQL-procedure-statement in a BEFORE trigger cannot reference a generated column, other than the identity column, in the new transition variable (SQLSTATE 42989).
-----------------------------
It would be nice to be able to do something like that from a code maintenance viewpoint. But alas, you will have to have the code in both triggers.
Andy