MQSeries.net :: View topic

IanB · Posted: Wed Oct 18, 2006 6:44 am Post subject:

We use v5.3 and I think I've found out why the dotnet PCF support was giving me gip.
Now I've got the queue status thing running I thought I'd start pulling out useful stats. If I pass it an attribute to retrieve that doesn't exist (just make up a number, and I've set the value of the requested field to something in my response message it is not overwritten. However if the attribute does exist the value is always overwritten.
The reason for the test is to see if it assumes default values and find a way to identify which attributes work and which don't.

Anyway I was suspicious that the attributes that returned nothing were not defined in the header files and that all the attributes that were not defined failed to return anything, so...

It seems all the documentation on publib relates to v6. After hunting through the web I found this on the IBM site by searching for "new mq 6 pcf"

Monitoring, management, and problem determination

Much of the new release is concerned with being able to manage a WebSphere MQ environment. While there are many different aspects to management, one that is relevant to application developers is problem determination.

Examples of functions added to support this include the ability to:

Check which applications are using the queue manager and the objects they have opened.
Show the applications with long-running transactions.
Look at whether messages are being passed quickly through queues.
Lots of attributes have been added to the DISPLAY QSTATUS and DISPLAY CHSTATUS to assist, along with a DISPLAY CONN command.

So it seems all the interesting stats are v6 only.
Can anyone confirm my suspicions? Has anyone used MQIACF_OLDEST_MSG_AGE on v5.3?

Cheers
Ian