Previous Topic: UNIX and Linux User ExitsNext Topic: DBCOMMIT—Database Commit Exit

UNIX and Linux User Exits › UNIX and Linux Blockmode User Exits

UNIX and Linux Blockmode User Exits

The following table summarizes the functions available through the user exits for generated blockmode applications:

Name

Description

DBCOMMIT

Database Commit User Exit. There is one user exit routine for each supported database: Oracle, and DB2.

DBCONNCT

Database Connection User Exit. There is one user exit routine for each supported database: Oracle, and DB2.

DBDISCNT

Database Disconnect User Exit. There is one user exit routine for each supported database: Oracle, and DB2.

TIRDLCT

Dialect User Exit

TIRDRTL

Default Retry Limit User Exit

TIRHELP

Help Interface User Exit

TIRMTQB

Message Table User Exit

TIRSECR

Security Interface User Exit

TIRSYSID

System ID User Exit

TIRTERMA

User Termination User Exit

TIRTIAR

Database error message User Exit. There is one user exit routine for each supported database: Oracle and DB2.

TIRUPDB

MBCS Uppercase Translation User Exit

TIRUPPR

Uppercase Translation User Exit

TIRURTL

Ultimate Retry Limit User Exit

TIRUSRID

User ID User Exit

TIRYYX

Date User Exit

Note: The database user exits DBCONNCT, DBCOMMIT, DBDISCNT, and TIRTIAR are rebuilt into individual shared libraries (libae_db2.*, libae_ora.*) using the script $IEFH/make/mkdbs.

Blockmode runtime user exits are rebuilt into the shared library libae_userexits_c.* using the script $IEFH/make/mkexits. This is the same shared library that is used with Server applications.

Details for the preceding user exits follow in a separate section for each.