HP Integrity NonStop H-Series Guide de l'utilisateur télécharger pdf (Page 263)

HP NonStop Shadowbase Command Definitions

Database Specification Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

254

When a program purges the contents of a file (e.g., a CONTROL(20) call,

or a COBOL OPEN OUTPUT option), or when a command purges the

contents of a file or table (e.g., FUP PURGEDATA or SQLCI

PURGEDATA), the command may or may not specify a specific partition

(e.g., PARTONLY) or it may specify the entire file (primary and secondary

partitions) have its contents purged (not PARTONLY when executed

against the primary partition of the source file or table). When the

command is executed, the audit trail only records the fact that a specific

primary or secondary partition was purgedata’d…it does not record the

nature (syntax) of the original command. Hence, all HP Shadowbase

receives are the specific partition purgedata events. These execution

modifiers allow the user to tell HP Shadowbase how they want HP

Shadowbase to implement the effects of the source command against the

target file or table.

Available Purgedata Options:

KEEPALTFILES – Existing data in alternate key files on the target is kept.

This applies to Enscribe files only.

PURGEDATAALTFILES – Existing alternate key files for the target file

have their data (contents) purged if the target file is a primary partition (or

a single partition file). The Consumer must be running on the same node

as the target file in order for PURGEDATAALTFILES to function properly

in all cases. This is the default if no ALTFILE option is specified. This

applies to Enscribe files only.

ALLPARTS – If the target file or table is a primary partition (or a single

partition file or table), its data is purged along with that of any secondary

partitions of the file or table. If the target file or table is a secondary

partition, the purgedata event is ignored. This is the default if no partition

options specified.

PARTONLY – The target file or table has its data purged for the specified

partition only. The volume names of the source and target files/tables

must match to use his option.

CLOSETABLES – By default for SQL/MP alter events, the Consumer will

not close its target tables before processing the PURGEDATA event. By

specifying CLOSETABLES, the Consumer will close its target tables prior

to replicating the purgedata against the related target table.

NODDLCOORDINATION – By default, all Consumers will complete

processing of all in-progress and queued messages (“drained”) before an

PURGEDATA event is processed. This is necessary for coordinating the

1 2 ... 258 259 260 261 262 263 264 265 266 267 268 ... 345 346

Pas de commentaire

HP Integrity NonStop H-Series Guide de l'utilisateur Page 263