HP Integrity NonStop H-Series Guía de usuario descargar pdf (Pagina 31)

HP NonStop Shadowbase Command Definitions

Monitor Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

The ! (now) option can be used to expedite a pulse. Expedited pulses are

not inserted into the TMF audit trail like normal pulses; instead, they are

sent directly to the COLL and injected into the replication stream

immediately.

Upon successful completion of the PULSE command, a message will be

displayed to list the CONS objects that will receive the pulse event. Note

that this message will be truncated to about 128 bytes if the list of CONS

objects exceeds this limit. This message is to identify the Consumers for

which pulse events were generated for an AUDCOM PULSE command.

See the sample below for the format of the User Error Message that is

displayed.

PULSE GEN'D FOR 001 CONS'S: <consname>…

PULSESTATS Command

The AUDCOM PULSESTATS command was added in the Version 3.990

release to output pulse statistics related to the flow of a pulse from the

SOURCEFILE to the TARGETFILE. Similar to the PULSE command, the

PULSESTATS command supports requests at the COLL object, CONS

object, or CONSGROUP levels.

The output is grouped by CONS object and is in most recent to oldest time

sequence (i.e.,i.e., reverse timestamp order). By default, based up the

AUD MAXPULSESTATS value, the most recent two pulse file records are

output if available when the FROM and TO datetime parameters aren’t

input. Note that you can SET or ALTER the MAXPULSESTATS to have

more pulse records displayed when no FROM and TO clauses are

entered.

Each record displayed shows pertinent timestamps that are captured as a

pulse travels from its generation into the source pulse file to the target and

its completion gets acknowledged back. Note that the datetime

(timestamp) values stored in the file are in GMT, however the values

displayed are in local civil time (LCT). Also note that the DIFF value

durations are the difference between the related timestamp for the field

and the creation timestamp (CREATE TS).

Since the pulsing feature relies on timestamps generated by the clocks on

the source and target system, these clocks should be synchronized (either

with each other or with a GMT timer feed). If they are not, the clocks can

drift. This drift can be accounted for by the PULSECLOCKADJ and

1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 345 346

Sin comentarios

HP Integrity NonStop H-Series Guía de usuario Pagina 31