Page tree
Skip to end of metadata
Go to start of metadata

PATROL KM for UNIX uses the DCM collector as the default means to gather information for application classes and collector processes.

The following events are generated by conditions that affect a change in data collection. Note that when PATROL KM for UNIX switches to PSL (PATROL Scripting Language) data collection, Process Presence functionality does not exist. Look for these events to alert you to a change in data collection methods and the fact that the agent might not be collecting the type of data you want.

Switch to Manual PCM Data Collection

The following event is logged when you manually switch to PSL (PATROL Scripting Language) data collection.

Type of Event

INFORMATION

Severity

3

Event Class

UNIXToggleCollection

Description

This agent is now using classic PSL methods to collect data. This change was initiated from a Console in developer mode by @developer.

Toggle the DCM/PSL Collection Menu Command to DCM

The following event is logged when you select the DCM/PSL toggle command to switch to DCM data collection.

Type of Event

INFORMATION

Severity

3

Event Class

UNIXToggleCollection

Description

This agent is now using the PERFORM collector to collect data. This change was initiated from a Console in developer mode by @developer.

DCM Binary Dies

One of the following events will be logged when the DCM binary dies.

Type of Event

WARNING

Severity

3

Event Class

41

Description

DcmCol.psl: dcm died 1 times.

Type of Event

ALARM

Severity

4

Event Class

11

Description

Alarm #2 of global parameter 'DCMStatus' triggered on 'DCM.DCM'. 2 <= 2.00 <= 2.

DCM Fails over to PSL

The following event is logged when DCM fails over to PSL data collection.

Type of Event

WARNING

Severity

3

Event Class

41

Description

DcmCol.psl: Switching to PSL data collection. DcmCol.psl: Event text: DcmCol.psl: Reason for switch to PSL: DCM terminated count exceeds maximum allowed.

Deactivate SMP Application on a Single-CPU System

The following event is logged when the SMP application is deactivated on a single-CPU system. (This event only seems to occur when PSL collection is in effect.)

Type of Event

INFORMATION

Severity

3

Event Class

41

Description

SMP: Single CPU system, deactivating.

Toggle PSL/DCM Collection and Reinitialize the Patrol Agent

The following event is logged after using the PSL/DCM toggle command and reinitializing the BMC PATROL Agent.

Type of Event

INFORMATION

Severity

3

Event Class

0

Description

Event (0,StartStop) not found in catalog: snowcap 1 0.

Defined Process Presence Instance Does Not Exist for pconfig Variable

If the pconfig variable, /PUK/PROCPRES/attach_ps_list", exists and is set to TRUE, the following event is generated when the defined process presence instance does not exist. (This condition is based on a recovery action defined for PROCPPCountCheck parameter.) The following event is logged after using the PSL/DCM toggle and re initializing the BMC PATROL agent.

Type of Event

INFORMATION

Severity

3

Event Class

41

Description

This event contains a list of top ten processes and monitored processes. It is generated by the recovery action of the PPROCPCountCheck parameter due to an alert condition.

Related topics

Collection Methods

Changing the collection method

  • No labels