Properties of CAF connections

Call attachment facility (CAF) enables programs to communicate with Db2.

The connection that CAF makes with Db2 has the basic properties that are listed in the following table.

Table 1. Properties of CAF connections
Property	Value	Comments
Connection name	DB2CALL	You can use the DISPLAY THREAD command to list CAF applications that have the connection name DB2CALL.
Connection type	BATCH	BATCH connections use a single phase commit process that is coordinated by Db2. Application programs can also control when statements are committed by using the SQL COMMIT and ROLLBACK statements.
Authorization IDs	Authorization IDs that are associated with the address space	Db2 establishes authorization IDs for each task's connection when it processes that connection. For the BATCH connection type, Db2 creates a list of authorization IDs based on the authorization ID that is associated with the address space. This list is the same for every task. A location can provide a Db2 connection authorization exit routine to change the list of IDs.
Scope	CAF processes connections as if each task is entirely isolated. When a task requests a function, the CAF passes the functions to Db2 and is unaware of the connection status of other tasks in the address space. However, the application program and the Db2 subsystem are aware of the connection status of multiple tasks in an address space.	none

If a connected task terminates normally before the CLOSE function deallocates the plan, Db2 commits any database changes that the thread made since the last commit point. If a connected task abends before the CLOSE function deallocates the plan, Db2 rolls back any database changes since the last commit point. In either case, Db2 deallocates the plan, if necessary, and terminates the task's connection before it allows the task to terminate.

If Db2 abnormally terminates while an application is running, the application is rolled back to the last commit point. If Db2 terminates while processing a commit request, Db2 either commits or rolls back any changes at the next restart. The action taken depends on the state of the commit request when Db2 terminates.