Updates the location, device type, or comment in a history file entry.
Authorization
One of the following:
Required Connection
Database. To update entries in the history file for a database other than the default database, a connection to the database must be established before calling this API.
Version
db2ApiDf.h
C API Syntax
/* File: db2ApiDf.h */ /* API: Update Recovery History File */ /* ... */ SQL_API_RC SQL_API_FN db2HistoryUpdate ( db2Uint32 version, void * pDB2HistoryUpdateStruct, struct sqlca * pSqlca); typedef struct { char * piNewLocation, char * piNewDeviceType, char * piNewComment, db2Uint32 iEID } db2HistoryUpdateStruct; /* ... */ |
Generic API Syntax
/* File: db2ApiDf.h */ /* API: Update Recovery History File */ /* ... */ SQL_API_RC SQL_API_FN db2GenHistoryUpdate ( db2Uint32 version, void * pDB2GenHistoryUpdateStruct, struct sqlca * pSqlca); typedef struct { char * piNewLocation, char * piNewDeviceType, char * piNewComment, db2Uint32 iEID } db2GenHistoryUpdateStruct; /* ... */ |
API Parameters
REXX API Syntax
UPDATE RECOVERY HISTORY USING :value |
REXX API Parameters
Usage Notes
This is an update function, and all information prior to the change is replaced and cannot be recreated. These changes are not logged.
The history file is used for recording purposes only. It is not used directly by the restore or the roll-forward functions. During a restore operation, the location of the backup image can be specified, and the history file is useful for tracking this location. The information can subsequently be provided to sqlubkp - Backup Database. Similarly, if the location of a load copy image is moved, the rollforward utility must be provided with the new location and type of storage media. For additional information, see the Administration Guide and sqluroll - Rollforward Database.
See Also
db2HistoryCloseScan - Close Recovery History File Scan
db2HistoryGetEntry - Get Next Recovery History File Entry
db2HistoryOpenScan - Open Recovery History File Scan
db2Prune - Prune Recovery History File.