beautypg.com

Parameters for monconf file, Table 5 parameters for monconf file – HP NonStop G-Series User Manual

Page 126

background image

Appendix O: Configuration File Parameters 126

Parameters for MONCONF File

Table 5

Parameters for MONCONF File

Parameter

Description/Allowed Value

Default Value

FileSys

Yes: Generate alerts if file does not exist OR threshold
violated

No: Generate alerts ONLY if file exists AND threshold
violated

SkipEMS

Yes: Skip first ems message if normal and using eEvents

All: Skip first ems message if normal

No: Generate first ems message if normal

NO

Live

Yes: Send messages to ObjectStats

No: Do not send messages to ObjectStats unless requested

YES

MAXPORTS

When set to -1 (the default) causes all TCPIP objects to be
monitored by a single ORM clone process.

When set to >= 0 this is the maximum number of TCPIP
objects that will be monitored by a single ORM clone
process.

-1

CPUMASK

Allows user to select which CPUs will run an ORM clone process.
Example: To avoid CPUs 0 &1 set param to:
0011111111111111.
If omitted ORM takes up the default value to all 1's (run clones on
all cpus).

1111111111111111

PINGPROG

Specifies the location of the PING program. This is used for the
PING thresholds.

CLOSETDF

When YES then ORM will only open TDF when necessary, i.e. to
read to process thresholds at the time polling intervals expire.
Default value is set as ‘No’ that means TDF can be opened
anytime.

NO

INITRETRIES

Used by master only. Specifies the number of times it will check
for expected clones to be ready before just processing with
clones that are ready. Retries are done at five second intervals.

6

B24OPTIONS

Used by master only.

0: Distributes all Base24 objects evenly across all CPUs.

1: Distributes all Base24 objects to ONE CPU.

2: Distributes all LISTOBJECTS type Base24 thresholds to one
CPU. Also, distributes non-LISTOBJECTS objects evenly.

FASTLOAD

Used by master only.

YES: Invoke the fastload process. In this case the master
process reads objects from disk and distributes them to clone
ORM processes over $RECEIVE. This eliminates WRITEing
records to ORMCPU files, READing of those files by clones,
KEYPOSITIONING on ORMOBJ file by clones and READing
of ORMOBJ file by clones. Generally results in better load
time performance, less disk I/O. FASTLOAD YES is required
for the WHOHAS command to work.

No: In this case master writes ORMCPU files which are read
by clones to select their assigned objects from ORMOBJ,
which clones and then reads from disk. Results are generally
displayed in slower load times, and more disk I/O is used.

YES

This manual is related to the following products: