Implicit connection management for nondefault activation groups

 

An application requester can be implicitly connected to an application server. Implicit SQL connection occurs when the application requester detects that the first SQL statement issued for the activation group is not a CONNECT statement with parameters.

For a distributed program, the implicit SQL connection is made to the relational database specified on the RDB parameter. For a nondistributed program, the implicit SQL connection is made to the local relational database.

Implicit disconnect can occur at the following times in a process:

• When the activation group ends, if commitment control is not active, activation group level commitment control is active, or the job level commitment definition is at a unit of work boundary.

  If the job level commitment definition is active and not at a unit of work boundary, SQL is placed in the exited state.

• If SQL is in the exited state, when the job level commitment definition is committed or rolled back.

• At the end of a job.

 

Parent topic:

Connection management and activation groups

 

Related reference

Ending connections