Ensure that the following attributes are configured with appropriate values.

If you have configured the required attributes to enable the WebSphere MQ agent for IMF, but the agent is still not IMF-enabled, restart the agent. The imf_init function runs only when the agent starts up, so when you restart the agent, imf_init runs and initializes the WebSphere MQ agent to interface with the AMF kernel driver.

You can run the following command to check the value of the MonitorMethod attribute and to verify that a resource is registered for IMF.

# hares -value resource MonitorMethod system

The MonitorMethod attribute specifies the monitoring method that the agent uses to monitor the resource:

You can use the amfstat to see a list of registered PIDs for a WebSphereMQ6 resource.

Following is a sample output for the Queue Manager 'testQM'.

The ps -ef command output shows the Queue Manager process.

# ps  - ef | grep -i testQM
mqm 10085 10075   1 13:38:30 ?  0:00 amqzlaa0 -mTestQM 
                                     -fip0
mqm 10080 10075   1 13:38:28 ?  0:00 amqzmur0 -m TestQM
mqm 10083 10075   1 13:38:28 ?  0:00 /opt/mqm/bin/
                                     amqzdmaa -m TestQM
mqm 10076 10075   1 13:38:27 ?  0:00 /opt/mqm/bin/
                                     amqzfuma -m TestQM
mqm 10088 10081   1 13:38:30 ?  0:00 amqfqpub -mTestQM
mqm 10086 10084   0 13:38:30 ?  0:00 /opt/mqm/bin/
                                     runmqchi -m TestQM 
                                     -q SYSTEM.CHANNEL.
                                     INITQ -r
mqm 10089 10088   1 13:38:30 ?  0:00 amqfcxba -m TestQM
mqm 10077 10075   1 13:38:27 ?  0:00 amqzmuc0 -m TestQM
mqm 10082 10075   0 13:38:28 ?  0:00 /opt/mqm/bin/
                                     amqrrmfa -m TestQM 
                                     -t2332800 -s2592000 
                                     -p2592000 -g5184000 
                                     -c3600
mqm 10084 10075   1 13:38:29 ?  0:00 /opt/mqm/bin/
                                     amqzmgr0 -m TestQM
mqm 10075     1   1 13:38:27 ?  0:00 amqzxma0 -m TestQM
mqm 10081 10075   1 13:38:28 ?  0:00 amqzmuf0 -m TestQM
mqm 10087 10084   1 13:38:30 ?  0:00 /opt/mqm/bin/
                                     amqpcsea TestQM

The amfstat command shows the Queue Manager PIDs monitored by the WebSphereMQ agent.

# amfstat
AMF Status Report

Registered Reapers (3):
=======================
 RID    PID     MONITOR TRIGG   REAPER
163    16417   7       0       WebSphereMQ6

Process ONLINE Monitors (7):
============================
 RID    R_RID   PID     GROUP
 165    163     10082   TestQM
 166    163     10086   TestQM
 167    163     10083   TestQM
 168    163     10076   TestQM
 169    163     10075   TestQM
 170    163     10077   TestQM
 171    163     10080   TestQM

Run the following command to set the ResLogLevel attribute to TRACE. When you set ResLogLevel to TRACE, the agent logs messages in the WebSphereMQ6_A.log file.

# hares -modify ResourceName ResLogLevel TRACE

Run the following command to view the content of the AMF in-memory trace buffer.

# amfconfig -p dbglog

If you have upgraded to VCS version 5.1 SP1, from an earlier VCS version, and if you already have WebSphere MQ agent version 5.1.9.0 installed, ensure that the appropriate symbolic links have been created. You can run the following commands to create appropriate symbolic links: