Monitor messages

Monitors issue messages as problems occur and get resolved. A monitor issues a warning message when a user-defined threshold is exceeded. When the monitored situation returns to a level below the threshold, a resolution message is issued.

The following example show both warning and resolution messages for each monitor. If a monitor does not have a unique resolution message listed, its resolution message is the same as its warning message (with the addition of a Z severity indicator).

Related topic

Using-monitor-views

The @TSKC monitor, for example, has the following warning message

FT042W TRAN XXXXXXXX TASK 00000 HAS USED NNNNNN.N CPU SEC )

but no unique resolution message. Its resolution message is

FT042Z TRAN XXXXXXXX TASK 00000 HAS USED NNNNNN.N CPU SEC )

Messages that are issued by monitors that use thresholds specified in the starting parameter consist of three parts: message ID, title, and monitored data. These message IDs can be used in messages issued by more than one monitor, the title portion is always unique to the issuing monitor, which means that a message’s issuing monitor can always be identified.

The message FT1110W, for instance, can be issued by eight monitors. The following message was issued by the PGMS monitor, identified by the title portion of the message:

FT1110W (01) 07:37:00 PROGRAM STORAGE SIZE(ECHOBIG) = 46032 (>40)

If the message had been issued by the TSTE monitor instead, it would be

FT1110W (01) 07:37:00 Temporary Storage Size(ECHOBIG) = 46032 (>40)

Messages issued from monitors that uses the thresholds from the problem threshold table are identical.

For example, the TSKS and PRB2 monitors can both issue the following message, which is identical both in terms of message ID and title:

FT041 TRAN XXXXXXXX TASK 00000 USING NNNNNNK OF STORAGE

To determine which monitor actually issued a message, review the BBI-SS PAS journal log.

The following section lists the message:

Monitor messages

On this page