
HP NonStop Shadowbase Command Definitions
Collector Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
73
lagging behind if the difference between the time of last read audit trail
record and the time of the current audit trail restart position is equal to or
greater than CHKPTWARNTDIFFB. In release v3.980B the Collector was
enhanced to produce EMS warning messages if the bi-directional restart
position is not advancing within a threshold defined by the
CHKPTWARNTDIFFB parameter plus 12 more bi-directional flush
intervals (1 additional hour by default). A message will be generated if the
bi-directional restart position falls out of tolerance. A message will be
repeated every CHKPTWARNRATE interval if it remains out of tolerance.
When it is determined to be back within range, a message is generated to
indicate this. In v4.090 the maximum value was increased from 32767 to
2147483647 (from a 16-bit value to a 32-bit value).
CHKPTWARNTDIFFB is specified in seconds, from 0 to 2147483647.
The checking is disabled when CHPTWARNTDIFFB is set to 0. The
default is 8100 seconds (2.25 hours). 2.25 hours is the standard window
that the HP Shadowbase Collector maintains for the bi-directional restart
position. Note that CHKPTTIME must be set for the check to be
performed. CHKPTTIME is also used for the check associated with the
existing CHKPTWARNTDIFF parameter (used to check the normal restart
position to make sure it is advancing).
CPU cpu_number
Initial Changed
Version Version Values Default Value Specifications Alter
1.000 None Valid CPU number Yes
Specifies the processor where the Collector runs. It is required to add a
Collector. Cpu_number must be a valid CPU for your system.
Note: That the CPU can be altered at any time. If altered, the new value
will be used in the event a restart is performed.
CPULIST { (cpu-number [, cpu-number]…) }
{ (-1) }
Initial Changed
Version Version Values Default Value Specifications Alter
4.080 -1 Valid CPU number list Yes
This parameter specifies a list of processors to be used for starting the
related COLL or CONS object process. Up to 16 can be specified (0
through 15). The order of usage is the order of the cpu list. If a processor
is not available, the next in the list will tried. Note that when the CPULIST
is specified, the CPU and BACKUPCPU will not be considered. An
appropriate EMS messages will be logged to indicate if a problem
occurred attempting to use a processor. A message will be logged to
Comentarios a estos manuales