HP NonStop Shadowbase Command Definitions
Database Specification Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
221
information when using this handler. Note that the Consumer
settings for RETRYDELAY is used to timeout file IO opeations.
When this bit is turned on (1), HP Shadowbase will assume that the
source “primary key” (relative record number) will not be preserved
when the records are replicated to the target file (this is common for
replicating relative records in an active/active environment where
the relative record numbers cannot be assured across the database
copies). Instead, the unique alternate key (identified via the “TM”
key specifier) will be used for positioning. Note that when this logic
is enabled, HP Shadowbase implements special logic for properly
handling the “reversing delete” operation of source-side alternate
key file duplicate key errors (contact HP Shadowbase Support for
more information).
<Bit1> Entry Sequenced file replication and BASE24 handling of DML
events (e.g., a BASE24 PTLF file). This includes the handling of
inserts, updates and deletes for files such as the BASE24
PCyymmdd and PAyymmdd file sets. When enabled, the “header”
records (at relative record 0 position in the file, i.e.,i.e., the first
record in the file) are always replicated to the appropriate target
location’s header record (INSERT and UPDATEs to the source’s
header record are always applied to the header record of the target
file, either as an insert or an update/overlay of what is at that
position). UPDATEs to other records in the source are discarded
(should not happen) – see the description of other bits below (for
example, bit <3>) for how updates to other types of entry-
sequenced files in BASE24 are handled .
<Bit2> This is the insert-anywhere bit and is used to determine how an
insert into a relative file is handled by the file system (this logic is
used for files that have the BASE24HANDLERID specified with bit
<0> enabled).
When set to 1 (on), relative inserts are inserted “anywhere” (relative
record value -2). When set to 0 (off), inserts are appended to the
eof (relative record value -1).
<Bit3> Entry Sequenced file replication and BASE24 handling of DML
events (e.g., a BASE24 ILF file). When enabled, the header
records (relative record 0) are always replicated to the appropriate
target location’s header record (INSERT and UPDATEs to the
source’s header record are always applied to the header record of
the target file, either as an insert or an update/overlay of what is at
that position).
Comentários a estes Manuais