PM61811: TEMPORAL SUPPORT TO SUPPRESS PRODUCTION OF HISTORY DATA

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

Closed as new function.

Error description

Temporal support to suppress production of history data

Local fix

n/a

Problem summary

****************************************************************
* USERS AFFECTED: All users of DB2 10 for z/OS who use both *
* temporal support and replication products. *
****************************************************************
* PROBLEM DESCRIPTION: DM1541 for DB2 10 for z/OS: A new *
* DB2-supplied stored procedure has been *
* implemented to set the internal *
* option to disable recording of *
* temporal history for a system-period *
* temporal table and allow values to be *
* specified for the special temporal *
* column types previously mentioned. *
* *
* When this procedure is invoked by a *
* connection, DB2 behavior (for static *
* and dynamic SQL) is affected as *
* follows: *
* 1, historical rows are not written *
* to a history table for update or delete *
* operations. *
* 2, an application may specify values *
* (such as in an INSERT statement or *
* UPDATE statement) for a row-begin, *
* row-end, or transaction-start-ID *
* column even though the column is *
* defined as GENERATED ALWAYS, and *
* these values will be stored in the *
* affected rows. *
* *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DM1541 for DB2 for z/OS V10: A new DB2-supplied stored procedure
has been implemented to set the internal option to disable
recording of temporal history for a system-period temporal
table and allow values to be specified for the special
temporal column types previously mentioned. The DB2-supplied
procedure is named,
SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY.
This stored procedure is not intended for general use. It is
intended to be used by products that enable DB2 replication.
When this procedure is invoked by a connection, DB2 behavior
(for static and dynamic SQL) is affected as follows:
1, historical rows are not written to a history table for
update or delete operations.
2, an application may specify values (such as in an INSERT
statement or UPDATE statement) for a row-begin, row-end, or
transaction-start-ID column even though the column is defined
as GENERATED ALWAYS, and these values will be stored in the
affected rows.
Additional Keywords: SQLBITEMPORAL SQLSPTT