Sets the interrupt processing mode.
- db2cli.ini keyword syntax:
- Interrupt = 0 | 1 | 2
- Default setting:
- In Version 10.5 GA client:
- 1
- In Version 10.5 Fix Pack 2 and later client:
- 1 for connection to all database servers other
than DB2® for z/OS® servers.
- 2 for connection to DB2 for z/OS servers.
Important: The default value affects direct connection to DB2 for z/OS server.
- Usage notes:
- The Interrupt keyword can be set in the [Data_Source] section
of the db2cli.ini file for a specific data source,
or in a connection string.
The Interrupt keyword
can be set to following values:
- 0
- Disables interrupt processing. The SQLCancel function
call does not interrupt the processing.
- 1
- Interrupts are supported. In this mode, if the server supports
an interrupt, an interrupt is sent. Otherwise, the connection is
dropped.
The settings for INTERRUPT_ENABLED (a DB2 Connect™ gateway setting)
and the DB2 registry
variable DB2CONNECT_DISCONNECT_ON_INTERRUPT takes
precedence over the Interrupt keyword setting of 1.
When you connect to a
DB2 for z/OS server
with the interrupt mode 1 setting, the following operations are not
interrupted:
- Stored procedure operations.
- SQL statement operations that hold a DB2 internal
resource lock manager (IRLM) lock used by DB2 for z/OS servers
to serialize access to your data. DB2 for z/OS servers
request locks from IRLM to ensure data integrity when applications,
utilities, and commands attempt to access the same data.
- 2
- Interrupt drops the connection regardless of server's interrupt
capabilities. The SQLCancel function call drops
the connection.
The TCPIP protocol is required for
the Interrupt setting 2.
In Version 10.5 Fix Pack 2 and later, interrupt processing
mode 2 is the default value when you are directly
connecting to a DB2 for z/OS server.
DB2 10.5 for Linux, UNIX, and Windows