This documentation update applies to Note #3 for Table 103. Add/Delete/Non-update Long Field Record Log Record Structure in |the section entitled Long Field Manager Log Records in the topic entitled DB2 UDB log records. | The text for Note #3 should read:
|3. Long field data length in 512-byte sectors (actual data length is recorded |as the first 4 bytes of LF descriptor, which is logged in the subsequent insert/delete/update |log record as part of the formatted user data record ). The value of this |field is always positive. The long field manager never writes log records |for zero length long field data that is being inserted, deleted, or updated.
| | |In DB2 DB2 V8, the oBackupsize parameter from the db2Backup API accounts |for full backups and not for delta or incremental backups. The oBackupsize |parameter represents the size of the backup image (in MB).
The SYNCPOINT option for the sqlesetc, sqleqryc, and sqlaprep APIs is ignored as of Version 8; it is available only for backward compatibility.
In the sqlecrea API, a new field has been added to support Direct I/O.
A new field, unsigned char fsCaching, has been added in the SQLB-TBSPQRY-DATA structure. This new field supports Direct I/O. Although the size of the reserved bit is documented as 32-bit, the correct size is 31-bit.
[ Top of Page |Previous Page | Next Page | Contents ]