Skip to Content

Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

qpasatraps.pl logging

All traps are logged in the qpasatraps.txt file in the MainView Middleware Monitor (MVMM) directory on the computer with the  Event Service. The log is in comma-delimited (CSV) format and can be viewed using any text editor or a CSV capable editor such as Microsoft Excel.

Most log entries have the following format:

  • Status
  • Rule Name
  • Date/Time
  • Queue Manager
  • WebSphere MQ Object
  • WebSphere MQ Attribute
  • Value of WebSphere MQ attribute
  • Application
  • Contact
  • Severity

Related topics

Defining-SNMP-Traps

Configuring-SNMP-traps-with-qpasatraps-pl

Defining-events-triggers-and-actions

An exception to this format is if an undefined event rule was specified in the MVMM event in which case the status is set to RULE NOT DEFINED and all parameters are printed in the sequence that was specified in the MVMM event. If the qpasatrap.txt log indicates a send failed that you are unsure of, you can enable the SNMP modules debugging by uncommenting the line:

#<== Uncomment to debug SEND FAILED errors

All events are logged in qpasatrap.txt even if they are suppressed by the time parameter.

Error

Corrective action

RULE NOT DEFINED

Check that the event trigger name (if using the SNMP format script) matches the names in the $event_info hash, or the first parameter in the command arguments.

TIME SUPPRESSED

The time specified in the qptime parameter was sometime in the future.

OPEN FAILED

Unable to open the session to the SNMP Receiver. Verify the MySNMPServer has been properly replaced. Check that networking it properly set up on the server system.

SEND FAILED

The session was established to the SNMP Receiver but the send failed. Verify second command argument matches the necessary format.

TRAP SENT

Normal completion.

Qpasatrap.txt lists each attempt to send a trap.

Message

Result or value

TRAP SENT

Trap sent.

event_type

First command line parameter.

time

Time on the system at the time qpasatrap.pl is executed.

OID

Oid on which the trap is sent.

Mqhost

Host on which the event occurred (from 2nd command line parameter).

qmgr

Queue Manager on which the event occurred (from 2nd command line parameter).

object

Object for which the event occurred (from 2nd command line parameter).

attr

Attribute associated with the event (from 2nd command line parameter).

value

Value associated with Attribute (from 3nd command line parameter) app Value from the qpapp optional parameter.

contact

Value from the qpcontact optional parameter.

severity

Value from the $event_info hash in qpasatrap.pl.

duration

Value from the qpduration optional parameter.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView Middleware Monitor 9.0