Release Notes

3.0 Administrative API Reference

3.1 How the API Descriptions are Organized/C API Syntax

Change the second bullet to:

   Generic APIs have names that contain the prefix "db2g", followed by a
   string that matches the C API name. Data structures used by generic
   APIs have names that also contain the prefix "db2g".

3.2 db2LoadQuery - Load Query

Change the name of the generic API "db2GenLoadQuery" to "db2gLoadQuery". Change the name of the structure used by the generic API "db2gLoadQuery" to "db2gLoadQueryStruct".

A Fortran version of the "loadqry" sample program is not available.

3.3 sqlarbnd - Rebind

For both the C API "sqlarbnd" and the generic API "sqlgrbnd", replace the "void * pReserved" parameter with "struct sqlopt * pRebindOptions":

   pRebindOptions 
      Input. A pointer to the sqlopt structure, used to pass rebind options to the API.
      For more information about this structure, see SQLOPT.

The following table lists valid values for the TYPE and the VAL fields of the rebind options structure (see SQLOPT), as well as their corresponding CLP options. For a description of the rebind options (including default values), see the Command Reference.

   REBIND Option Types and Values
 
      CLP Option             Option Type       Option Value
 
      RESOLVE ANY            SQL_RESOLVE_OPT   SQL_RESOLVE_ANY
      RESOLVE CONSERVATIVE   SQL_RESOLVE_OPT   SQL_RESOLVE_CONSERVATIVE

3.4 Compound=x File Type Modifier (sqluimpr - Import)

If this modifier is specified, and the transaction log is not sufficiently large, the import operation will fail. The transaction log must be large enough to accommodate either the number of rows specified by COMMITCOUNT, or the number of rows in the data file if COMMITCOUNT is not specified. It is therefore recommended that the COMMITCOUNT option be specified to avoid transaction log overflow.

This modifier is incompatible with INSERT_UPDATE mode, hierarchical tables, and the USEDEFAULTS modifier.

3.5 SQLFUPD

The data type for the "dl_upper" database configuration parameter is Sint16, and for the "dl_token" parameter, it is char(10). The book incorrectly specifies the reverse.

There is a missing value in the list of valid values for the "authentication" database manager configuration parameter. The missing value is "SQL_AUTHENTICATION_DCE_SVR_ENC (6)".

3.6 SQLOPT

All references to bind and precompile should include rebind, because this structure can now also be used to pass bind options to sqlarbnd - Rebind.

3.7 SQLULOAD-IN Data Structure

The description of this structure is missing the "indexing_mode" parameter. Supported values (defined in sqlutil.h) are:

   SQLU_INX_AUTOSELECT
   SQLU_INX_REBUILD
   SQLU_INX_INCREMENTAL
   SQLU_INX_DEFRRED

For an explanation of these indexing modes, see the description of the LOAD command in the Command Reference.

3.8 Transaction Manager Log Records

Appendix G describes DB2 log records. Following is a modified description of the record structure of some of the transaction manager log records:

• Local Pending List: 20 bytes for log header, 4 bytes for commit time, 2 bytes for auth id length, auth id (variable length, indicated by the length field), pending list entries (note: auth id length and auth id are only there if the log record is marked as propagatable)

• Global Pending List: 20 bytes for log header, 2 bytes for auth id length, auth id (variable length, indicated by the length field), pending list entries (note: auth id length and auth id are only there if the log record is marked as propagatable; also, there is no commit time)

• Normal/Heuristic/MPP Coordinator/MPP Subordinator Commit, Normal/Heuristic Abort: change authid from fixed length 9-byte field to variable length

• XA Prepare: 20 bytes for log header, 4 bytes for prepare time, 8 bytes for log space used by transaction, 4 bytes for transaction node list size, transaction node list (variable length, indicated by the previous field), XA identifier for transaction, application information structure (consists of 4 bytes for length, 4 bytes for code page, 4 bytes for transaction start time, 20 bytes for application name, 32 bytes for application identifier, 4 bytes for sequence number, 20 bytes for client database alias, variable length for auth id), variable length for synclog information

• MPP Subordinator Prepare: 20 bytes for log header, 4 bytes for prepare time, 8 bytes for log space used by transaction, 6 bytes for coordinator LSN, 2 bytes for padding (no real data), 20 bytes for SQLP_GXID, application information structure (consists of 4 bytes for length, 4 bytes for code page, 4 bytes for transaction start time, 20 bytes for application name, 32 bytes for application identifier, 4 bytes for sequence number, 20 bytes for client database alias, variable length for auth id)

[ DB2 List of Books | Search the DB2 Books ]