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

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 346
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 29
HP NonStop Shadowbase Command Definitions
Monitor Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
21
PULSE Command
The PULSE command enables the operator to send a special data packet,
known as a ‘PULSE’ through the replication stream. When completed, the
PULSE will provide a series of timings based upon how long it takes the
message to transverse the replication stream and return to the source
component. These PULSe timing values can then be read by issuing the
PULSESTATS command.
Note that there are various pulsing error conditions (such as pulse file full)
that can cause AUDMON to disable the pulse feature. The PULSE
command can also be used as the trigger to try to re-enable the pulse
feature after it becomes disabled.
A CONSGROUP Consumer process grouping concept was also
introduced. This new CONS object parameter allows the grouping of a
number of Consumer processes into an identifiable group name which can
be entered for the PULSE command (and PULSESTASTS command).
This allows one to logically group a number of related replication threads,
for example if multiple replication threads are being used to replicate to a
common target database. See later enhancements in the softdoc for more
information pertaining to the CONSGROUP parameter details.
The PULSE command supports generating pulse events at the COLL
object, CONS object, or CONSGROUP levels. The command syntax for
the PULSE command is as follows:
PULSE {[COLL] {<collname>}
{* }}
{[CONS] {<consname>}
{* }}
{[CONSGROUP] {<consgroupname>}} [!]
Pulsing a Collector (or all Collectors via *) will generate pulses for all
source or client Consumers attached to the Collector(s). Pulsing a
specific Consumer (or all Consumers via *) will only generate pulses for
source or client Consumers. Pulsing a Consumer group will only generate
pulses for source or client Consumers in that group. Source or client
Consumers are the source of a pulse event; target or server Consumers
simply process the pulse event(s) they receive and return them.
Vue de la page 29
1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 345 346

Commentaires sur ces manuels

Pas de commentaire