Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Ordinateurs - HP Integrity NonStop H-Series (16.73 mb)
Ordinateurs - HP Integrity NonStop H-Series (957.56 kb)
Ordinateurs - HP Integrity NonStop H-Series (881.66 kb)
Ordinateurs - HP Integrity NonStop H-Series (965.62 kb)
Ordinateurs - HP Integrity NonStop H-Series (676.93 kb)
Ordinateurs - HP Integrity NonStop H-Series (393.72 kb)
Ordinateurs - HP Integrity NonStop H-Series (776.57 kb)
Facilité d'utilisation
Introduction
Reject Files
file can leave “garbage data” in that byte position(s) in the file; aborting an
insert for an entry-sequenced file replaces the entry with a 0-length record
(these must be skipped when subsequently processing the Reject File
entries).
When the consumer is configured to write to a Reject File it will create a
new file on startup if necessary – the new file will be the next in sequence
from the last logically numbered file in the subvolume. A new file will not
be created if the existing “last” file in sequence has no data in it (i.e., the
EOF is zero); instead this file will be reused. If the last file does have data
in it a file with the next sequence id will be created and used. New Reject
Files are also created while the consumer is running and the active Reject
File becomes full.
At startup, the consumer will determine the maximum sequence number of
the existing Reject File. If this file is empty it will be reused. Otherwise
the consumer will create a new file that comes next in the sequence. All
subsequent Reject Files will continue being created in this sequence.
Note: The Reject Files are logically numbered with a 4-digit suffix added
to a 4-character prefix (e.g., XXXXnnnn where XXXX can be
specified in the HP Shadowbase configuration and nnnn will be
automatically selected by HP Shadowbase). The 4-digit suffix is
implemented to allow wrapping from 9999 to 0000. Hence, if the
only file in the subvolume is XXXX9998 at startup, the next file
created will be XXXX9999, the next file after that will be XXXX0000,
and the next file after that will be XXXX0001.
The consumer will not purge ‘old’ Reject Files. They need to be manually
cleaned up by the user. They can be archived or purged by the user when
they are no longer open by the consumer and needed by the user. We
anticipate that a future release will allow for a HP Shadowbase-managed
rolling retention of ‘n’ Reject Files.
The actual data in a Reject File contains packed data values. This is done
to preserve space for the events that are logged. This causes some
binary data fields to be positioned on an odd byte boundary. Programs
reading data out of this file need to properly handle the binary data byte
alignment (i.e., Guardian forces numeric binary data fields (such as
integers) to begin on even byte boundaries when they are processed).
Because the Reject File is an Enscribe entry-sequenced file on the HP
NonStop, the maximum length of each record can only be 4072 bytes. As
a result, a single reject entry can span multiple records in this file (i.e., it
may take several entry-sequenced records to log a Reject File event).
HP NonStop Shadowbase Reject Processing Manual—785428-001
2
... Ce manuel est également adapté pour les modèles :
Ordinateurs - HP Integrity NonStop J-Series (417.36 kb)