PROGNOSIS Configuration Syntax

The PROGNOSIS Configuration contains overall settings that affect the operation of Prognosis and all of its collector processes. Each collector may also have further settings in other Configuration files used to set specific details of how data is collected, stored, and retrieved.

SUBSYS PROGNOSIS

AUDITLOG (ip=<ip-address>, port=<port-number>, protocol={UDP | TCP}[, shownewline={y | true | n | false}]])
AUDITLOG (fqdn=<syslog-server-name>, port=<port-number>, protocol=TLS, certpath=<path>[, shownewline={ y | true | n | false}])
AUTO-INV {HARDWARE | SOFTWARE | SCOBOL} ({ON | OFF})
AUTO-INV HARD-INT (<n>)
AUTO-INV HARDTIME (<time>)
DOMAIN ADDTONODE ({Y | N})
EMS-BACK (<minutes>)
EMS-LOG (<collector-name>[, ...])
EVENTS (<number-of-events>)
EXPAND COMPRESS ( * | <\node>, ...)
EXPAND NOCOMPRESS ( * | <\node>, ...)
MAX-MEASURES (<max-concurrent-meas>)
MEAS-SIZE (<measure-file-size>)
RECSTORAGE (<record-name>, <size-in-KB>
[,<wrap-time-number>, <wrap-time-units>])
SET CPU (<object>, <CPU-number>)
SET MEM-SIZE (<object>, <max mem-size for process>)
SET PRIORITY (<object>, <priority>)
SET RUN (<object>, {Y | N})
SPOOLINT (<number-of-seconds>)
SPOOLJOBS ({Y | N})
TME-HOST (<host-name>[, ...])
TME-USER ([<host-name>\]<user>[, <user>])
USERRECORDS (<file-name>)
WORKVOL (<volume-Subvolume-name>)

Syntax Elements

AUDITLOG

Send Audit Log to remote Syslog server using UPD/TCP or TLS protocols

ip

The IP address of the Syslog server.

fqdn

The Fully Qualified Domain Name (FQDN) of the Syslog server.

port

Port number on which the Syslog server is listening for messages.

protocol

Enter the communications protocol to be used to transfer messages from the Monitoring Server to the Syslog server, either:

UDP - Unencrypted message format, or.

TCP - Unencrypted message format.

TLS - Encrypted message format. If using TLS, the 'certpath' parameter must be completed.

certpath

For TLS protocol only

Path and filename for the public certificate file (.pem) used by the Syslog server. A directory and file name is required, e.g. c:\certificate\cert.pem

The certificate file (.pem) must be added to the 'trusted store' on the Monitoring Server before attempting the TLS handshake. The .pfx file needs to be installed on the Syslog server machine.

shownewline

Optional parameter that determines if newline characters are sent as part of the Syslog message body. Some Syslog servers support parsing a message containing newlines, while others interpret each line as a separate message. By default, new lines will be shown. If 'shownewline' is off, new lines are replaced with a tilde (~).

Valid parameters are y, true, n, false.

Set 'shownewline' to false if multiple Syslog messages appear for each event. 'Kiwi Server' and 'Logstash' are two servers that require this configuration.

AUTO-INV

Specifies whether HARDWARE, SOFTWARE or SCOBOL collection should take place. If the system is not licensed for Hardware Manager or Software Monitoring, or if detailed hardware and software monitoring is not required, this feature may be disabled.

AUTO-INV HARD-INT

This option specifies how often to process the hardware inventory. The number in parenthesis is a count of days. The default is 1 (that is, every day).

AUTO-INV HARDTIME

This option specifies the time of day in which to start the hardware processing. The default is 4:00 AM. Enter the time using a 24-hour clock.

DOMAIN ADDTONODE

Selecting Y (YES) will append a unique identifier (e.g. .abc.local) to each node name. This will differentiate nodes of the same name coming from different networks.

EMS-BACK

Specifies the number of minutes that the EMS collector will look back in the EMS logs (those listed in the EMS-LOG statement, see below) for device up/down information. The EMS logs are reviewed only when the EMS collector has gone down and been restarted. This allows the EMS collector to maintain accurate device up/down information even when the Prognosis service was unavailable for a period of time. The default is 5 minutes. The upper limit is 32767 minutes. Although the EMS review process is optimized to reduce performance requirements, setting a large number of minutes in the EMS-BACK clause can impact system performance if your EMS log contains many messages.

The most important question to ask when setting this parameter is 'How long will my Monitoring Server be down for system outages under normal outage conditions?'. If a normal system or software outage, requiring the shutdown for 3 hours, this parameter could safely be set at 240 minutes.

The EMS collector will look back further in the EMS Log if required by the Availability collector (IRAVCOL). As a result, your displays may contain events earlier than the configured value of EMS-BACK. However, Databases and Thresholds will not get events that have already been received.

EMS-LOG

Specifies the EMS collectors to be monitored. The default is $0. However, if an alternate collector is specified and $0 is also required to be monitored, then $0 must also be included in the list.

EVENTS

Specifies the number of EMS events to keep in memory for online users. The default is 50 and the maximum is 32767. Specify zero (0) to save no events. The EVENTS statement does not affect databases.

For HPE NonStop the EMS-BACK, EMS-LOG and EVENTS statements have been superseded with the new EVENT Configuration Syntax. If an active EVENT Configuration is present, then the PROGNOSIS Configuration settings of EMS-BACK, EMS-LOG and EVENTS will be ignored.

EXPAND

Specifies which fields should be passed to the specified nodes. COMPRESS indicates only requested fields will be passed. NOCOMPRESS passes all fields.

MAX-MEASURES

Defines the maximum number of unique Measure intervals that may be in use concurrently. The default is 5.

MEAS-SIZE

Sets the size of any Measure work files created when a user specifies Measure records for collection. The default is 50MB.

RECSTORAGE

Specifies the amount of data to be kept for specified internal Records. This parameter is supported for the following records; AUTOOUT, AVOUTAGE, CMDLOG and TIVOLI. The amount of data kept will be the minimum of the size and wrap times specified. The relevant shared memory segment (and associated f0* file) will be sized as per the <size-in-KB> specified plus some space for header information. The supported <wrap-time-units> are DAYS, HOURS and MINUTES. The defaults are;

RECSTORAGE ( AUTOOUT, 134, 30, DAYS )
RECSTORAGE ( AVOUTAGE, 1000, 30, DAYS )
RECSTORAGE ( CMDLOG, 100, 30, DAYS )
RECSTORAGE ( TIVOLI, 127, 30, DAYS )

SET CPU

This statement is used to assign a particular CPU to a specific server/collector. If a particular CPU is used heavily, the SET CPU statement can be used to specify alternate CPUs for certain processes. For further information see Set Process CPU.

SET PRIORITY

This statement is used to specify a particular priority for the processes started by Prognosis. Use this clause to limit the impact of any collector or user collector on the system. See Set Process Priority for full details of this parameter.

SET MEM-SIZE

This is used to ensure that processes do not monopolize system memory. See Set Process Memory Size for full details of this parameter.

SET RUN

Indicates whether or not the Process Manager (irpromgr) is to start the specified executable/object or symbolic process id (as shown in the PSTATUS record). Y (YES), start the object or N (NO), do not start the object

Example:

SET RUN (STPATH, Y)
SET RUN (STTUNE, N)

SPOOLINT

Defines the number of seconds between spooler information collections. The default is 300 seconds (5 minutes). If the spooler needs to be monitored closely then set this to a smaller value such as 30 to 60 seconds.

SPOOLJOBS

Defines whether spooler job details (SPLJOB record) are collected. Y (YES), collect spooler job details (Default) or N (NO), do not collect spooler job details.

Note: - If SPOOLJOBS=N, then QLEN field in SPLDEV record will be zero (0).
Note: - A list of names can be used if there are multiple processes.

TME-HOST

Specifies hosts that are allowed to send commands to the TIVOLI listener process. This also enables the IRTECAD process.

TME-USER

Specifies users that are allowed to send commands to the TIVOLI listener process. This also enables the IRTECAD process.

USERRECORDS

Defines the location of an edit file containing the record definitions for User Records. If omitted, assumes there are no user-defined records. See the User Record Definitions for more information.

WORKVOL

This is used to define the volume and subvolume in which all work files will be created. The default is the Prognosis subvolume. This clause does not set the swap volume.

Provide feedback on this article