Think of actions as a nested sequence. The COMMIT action is the innermost level, then CLOSE, then DISCONNECT. Events are also organized hierarchically; CRTFORM is the innermost level, then COMMIT, then COMMAND, and, finally, FIN.

In general, you should not set the outer of two actions to occur more frequently than the inner action. Recommended combinations follow:

   When AUTOCOMMIT     is set to FIN,
         AUTOCLOSE      must be   FIN,
         AUTODISCONNECT must be   FIN*.
 
    When AUTOCLOSE      is set to FIN
         AUTODISCONNECT must be   FIN.
    When AUTOCOMMIT     is set to COMMAND or CRTFORM,
         AUTOCLOSE      may be    FIN, COMMAND or COMMIT,
         AUTODISCONNECT may be    FIN, COMMAND or COMMIT.
    When AUTOCLOSE      is set to COMMAND or COMMIT,
         AUTODISCONNECT may be    FIN, COMMAND or COMMIT.
    When AUTOCLOSE or AUTODISCONNECT is set to COMMIT,
         AUTOCOMMIT     may be    COMMAND or CRTFORM.
    * Violations of this rule can cause unpredictable behavior.

Note For DB2:

• Whenever you open a thread to a new application plan or connect to a new DB2 subsystem, the adapter issues a COMMIT WORK regardless of the AUTOCOMMIT setting.
• If the event that triggers AUTODISCONNECT occurs more frequently than the event that triggers AUTOCLOSE, the adapter forces a CAF CLOSE prior to any CAF DISCONNECT.
• In order to use the CLOSE and DISCONNECT commands, the Adapter for DB2 must be installed to use CAF.