SQL Server Mode users need to be able to fire SQL trigger programs from the Server Mode client job, via Native database I/O operations and have any SQL statements within the trigger program execute within the client job instead of being rerouted to a QSQSRVR server job.

SQL Server mode has been extended to allow an application to direct the database to execute SQL statements within an SQL trigger program within the SQL Server mode client job instead of rerouting the SQL to a QSQSRVR server job.

The change only affects SQL triggers fired via Native database I/O operations.

To enable the new function, an environment variable must exist before any SQL statements are executed within the client job. An easy way to deploy the environment variable would be to define it at the system level.

ADDENVVAR ENVVAR(QIBM_DB2_MIXED_SERVER_MODE) LEVEL(*SYS)

Restrictions and Usage Information:

• The environment variable just needs to exist, it does not need to be assigned a specific value. Once a job chooses to use this mixed mode support, it cannot turn off the choice.
• The SQL triggers must not be built to use commitment control.
• The SQL triggers must not use statement level isolation level support to execute statements using commitment control.
• The SQL triggers must not directly or indirectly use Java/JDBC or CLI.
• The triggers must not use DRDA.
• If the client job is multi-threaded and triggers are fired in parallel over different threads, the mixed-mode server mode solution will serialize the execution of the triggers. Only one trigger would be allowed to execute at a time.
• The solution does not apply to native triggers (ADDPFTRG) built over programs which use SQL.
• The solution does not include SQL triggers which call procedures, fire user defined functions, or cause nested triggers to execute.