| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| amqsactz enhancement |
« View previous topic :: View next topic » |
| Author |
Message
|
| tczielke |
 Posted: Wed Jan 14, 2015 11:31 am Post subject: amqsactz enhancement |
 |
|
Guardian
Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
|
The amqsactz program (an enhanced version of the amqsact sample that comes with MQ) has some recent changes. You can find them on the Capitalware web site -> http://www.capitalware.com/mq_code_c.html
Here are the enhancements to amqsactz:
1. Customizing fields in the API one line summary. You can now choose from around 40 fields to include in the API one line summary for each API call.
2. The Time field in the API one line summary includes a microsend time, if the high resolution timer was included in the operation.
3. Summary reports now include the queue manager
Enhancement 3 is helpful, if you want to combine AAT records from multiple queue managers and be able to summarize the data.
Along these lines, here is a suggestion on one way that you could use the AAT. One thing I have recently done is write a program that can reach out to all (or a subset) of our queue managers, turn the AAT on/off, and also move all the messages from the SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE on these queue managers to a holding queue. You can then run this new version of the amqsactz against this holding queue and get summary reports by queue manager, adjust the API one line summary fields so you can track a message by message or correlation id across multiple queue managers, etc. This gives you the ability to leverage a multi-queue manager activity trace, and synthesize the data in a more accessible way.
Unfortunately, my RFE for including the AAT in z/OS was turned down, so we can not leverage this tool for our entire MQ environment. Bummer . . . |
|
| Back to top |
|
 |
| tczielke |
| Posted: Fri May 01, 2015 4:52 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
|
I have made the following usability enhancement to the amqsactz tool.
When working with the one line API trace output, I have found it cumbersome and an eye strain to compare the 8-byte connection ids between different lines. Therefore, I have added a -u switch that will abstract each unique connection id to a unique but more readable number. This makes it much easier to read the connection id in the one line API trace output.
Here is an example:
amqsactz one line summary data that would before look like this:
| Code: |
1LS= Rec(0) Pid(13495) Tid(1) Date(2015-04-30) Time(16:38:42) Opr(MQXF_CMIT) RC(0) Chl() CnId(BB762A550171E721)
1LS= Rec(1) Pid(8089) Tid(567517) Date(2015-04-30) Time(16:38:42.631207) Opr(MQXF_CALLBACK) RC(0) Chl(MON.2S.SERVER) CnId(BB762A5569CE6F21) HObj(6) Obj(MON.RESPONSE)
1LS= Rec(2) Pid(8089) Tid(710853) Date(2015-04-30) Time(16:38:42.668476) Opr(MQXF_PUT) RC(0) Chl(CL.2S.SERVER1) CnId(BB762A550573D121) HObj(8) Obj(XXXX.00000.QUEUE1.BATCH)
|
now looks like this when run with the -u switch (with the CnId more readable):
| Code: |
1LS= Rec(0) Pid(13495) Tid(1) Date(2015-04-30) Time(16:38:42) Opr(MQXF_CMIT) RC(0) Chl() CnId(1)
1LS= Rec(1) Pid(8089) Tid(567517) Date(2015-04-30) Time(16:38:42.631207) Opr(MQXF_CALLBACK) RC(0) Chl(MON.2S.SERVER) CnId(2) HObj(6) Obj(MON.RESPONSE)
1LS= Rec(2) Pid(8089) Tid(710853) Date(2015-04-30) Time(16:38:42.668476) Opr(MQXF_PUT) RC(0) Chl(CL.2S.SERVER1) CnId(3) HObj(8) Obj(XXXX.00000.QUEUE1.BATCH)
|
Of course, if you do need to get back to the actual connection id for some reason, you can find it in the amqsactz verbose report (created with the -v switch) by searching for the record number key (i.e. Rec(1) )that appears in the one line summary output. Or you can just run the amqsactz program again without the -u switch.
The amqsactz.c source can be found on the Capitalware web site -> http://www.capitalware.com/mq_code_c.html
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| tczielke |
| Posted: Sat Aug 15, 2015 5:48 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
|
There is an update to the amqsactz.c (enhancement to the IBM supplied amqsact tool for working with the Application Activity Trace) -> http://www.capitalware.com/mq_code_c.html
Changes:
- Correct issue where when using startTime and endTime for message selection, the start and end time on the message was not being properly parsed by the program.
- Add MDAC (Message Data As Character) to API summary line.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
