This structure is used to specify connection setting types and values (see sqleqryc - Query Client, and sqlesetc - Set Client).
Table 32. Fields in the SQLE-CONN-SETTING Structure
| Field Name | Data Type | Description |
|---|---|---|
| TYPE | SMALLINT | Setting type. |
| VALUE | SMALLINT | Setting value. |
The valid entries for the SQLE-CONN-SETTING TYPE element and the associated
descriptions for each entry are listed below (defined in sqlenv and
sql):
| Type | Value | Description | ||
|---|---|---|---|---|
| SQL_CONNECT_TYPE | SQL_CONNECT_1 | Type 1 CONNECTs enforce the single database per unit of work semantics of older releases, also known as the rules for remote unit of work (RUOW). | ||
|
| SQL_CONNECT_2 | Type 2 CONNECTs support the multiple databases per unit of work semantics of DUOW. | ||
| SQL_RULES | SQL_RULES_DB2 | Enable the SQL CONNECT statement to switch the current connection to an established (dormant) connection. | ||
|
| SQL_RULES_STD | Permit only the establishment of a new connection through the SQL CONNECT statement. The SQL SET CONNECTION statement must be used to switch the current connection to a dormant connection. | ||
| SQL_DISCONNECT | SQL_DISCONNECT_EXPL | Removes those connections that have been explicitly marked for release by the SQL RELEASE statement at commit. | ||
|
| SQL_DISCONNECT_COND | Breaks those connections that have no open WITH HOLD cursors at commit, and those that have been marked for release by the SQL RELEASE statement. | ||
|
| SQL_DISCONNECT_AUTO | Breaks all connections at commit. | ||
| SQL_SYNCPOINT | SQL_SYNC_TWOPHASE | Requires a Transaction Manager (TM) to coordinate two-phase commits among databases that support this protocol. | ||
|
| SQL_SYNC_ONEPHASE | Uses one-phase commits to commit the work done by each database in multiple database transactions. Enforces single updater, multiple read behavior. | ||
|
| SQL_SYNC_NONE | Uses one-phase commits to commit work done, but does not enforce single updater, multiple read behavior. | ||
| SQL_MAX_NETBIOS_ CONNECTIONS | Between 1 and 254 | This specifies the maximum number of concurrent connections that can be made using a NETBIOS adapter in an application. | ||
| SQL_DEFERRED_PREPARE | SQL_DEFERRED_PREPARE_ NO | The PREPARE statement will be executed at the time it is issued. | ||
|
| SQL_DEFERRED_PREPARE_ YES | Execution of the PREPARE statement will be deferred until the corresponding OPEN, DESCRIBE, or EXECUTE statement is issued. The PREPARE statement will not be deferred if it uses the INTO clause, which requires an SQLDA to be returned immediately. However, if the PREPARE INTO statement is issued for a cursor that does not use any parameter markers, the processing will be optimized by pre-OPENing the cursor when the PREPARE is executed. | ||
|
| SQL_DEFERRED_PREPARE_ ALL | Same as YES, except that a PREPARE INTO statement which contains parameter markers is deferred. If a PREPARE INTO statement does not contain parameter markers, pre-OPENing of the cursor will still be performed. If the PREPARE statement uses the INTO clause to return an SQLDA, the application must not reference the content of this SQLDA until the OPEN, DESCRIBE, or EXECUTE statement is issued and returned. | ||
| SQL_CONNECT_NODE | Between 0 and 999, or the keyword SQL_CONN_CATALOG_ NODE. | Specifies the node to which a connect is to be made. Overrides the
value of the environment variable DB2NODE.
For example, if nodes 1, 2, and 3 are defined, the client only needs to be able to access one of these nodes. If only node 1 containing databases has been cataloged, and this parameter is set to 3, the next connect attempt will result in a connection at node 3, after an initial connection at node 1. | ||
| SQL_ATTACH_NODE | Between 0 and 999. | Specifies the node to which an attach is to be made. Overrides the
value of the environment variable DB2NODE.
For example, if nodes 1, 2, and 3 are defined, the client only needs to be able to access one of these nodes. If only node 1 containing databases has been cataloged, and this parameter is set to 3, then the next attach attempt will result in an attachment at node 3, after an initial attachment at node 1. | ||
| ||||
Language Syntax
C Structure
/* File: sqlenv.h */
/* Structure: SQLE-CONN-SETTING */
/* ... */
SQL_STRUCTURE sqle_conn_setting
{
unsigned short type;
unsigned short value;
};
/* ... */
|
COBOL Structure
* File: sqlenv.cbl
01 SQLE-CONN-SETTING.
05 SQLE-CONN-SETTING-ITEM OCCURS 7 TIMES.
10 SQLE-CONN-TYPE PIC S9(4) COMP-5.
10 SQLE-CONN-VALUE PIC S9(4) COMP-5.
*
|