| Author |
Message
|
| j1 |
 Posted: Sun May 01, 2011 8:14 pm Post subject: customizing/updating amqsaxe |
 |
|
Centurion
Joined: 23 Jun 2003
Posts: 139
|
Hi,
Are there any options to have amqsaxe o/p to just trap MQPUT* and MQGET* calls to make the logs less voluminous?
also, how could I go about updating the code to log just the messsages in ascii text rather than hex?
Im assuming everything under /opt/mqm/samp/ would be supported by ibm? Would customizations to amqsaxe be supported or can I write some kind of a utility to convert the hex msg o/p received from aqsaxe to jsut get the ascii text of the message to a log file?
Thanks in advance for the assist.
Cheers |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Sun May 01, 2011 9:39 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| Are there any options to have amqsaxe o/p to just trap MQPUT* and MQGET* calls to make the logs less voluminous? |
from the short documentation at the top of the program it does not look like there is such an option.
| Quote: |
| also, how could I go about updating the code to log just the messsages in ascii text rather than hex? |
just add the proper code, or modify it to fitt your needs.
| Quote: |
| Im assuming everything under /opt/mqm/samp/ would be supported by ibm? |
no, they are just samples. whatever you do with them, its all up to you and on your own risk.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| mvic |
| Posted: Mon May 02, 2011 8:46 am Post subject: Re: customizing/updating amqsaxe |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| j1 wrote: |
| Are there any options to have amqsaxe o/p to just trap MQPUT* and MQGET* calls to make the logs less voluminous? |
For this and the other questions, you presumably have some idea what to do. Your questions are sensible and to-the-point. I am a bit confused what you are asking for, as you already seem to know what is needed.
On the question about support, the amqsaxe0.c file is "sample code". That is, it shows a way of writing the code you might need. If you want your API exits do something different, write the code to make it happen. But IBM does not then support your code.
Hope I understood OK... |
|
| Back to top |
|
|
| j1 |
| Posted: Mon May 02, 2011 9:55 am Post subject: |
|
|
Centurion
Joined: 23 Jun 2003
Posts: 139
|
| does anyone know of sample code to o/p the results in ascii instead of hex? Im a bit of a newbie to C and this is probably best done in C. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon May 02, 2011 10:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The sample actually appears to log both in hex and a slightly modified ascii - anything that is not a printable character is replaced by a "."... because, you know, it is otherwise not a printable character...
and if you're a newbie to C, it's probably not a good idea to start by modifying or working with MQ exits. |
|
| Back to top |
|
|
| mvic |
| Posted: Mon May 02, 2011 10:23 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| mqjeff wrote: |
| and if you're a newbie to C, it's probably not a good idea to start by modifying or working with MQ exits. |
 with that!
j1, get someone who knows C in your team or company to advise. In fact I think you have quite a lot of code in amqsaxe0.c that will do what you want, or can be re-used to do what you want. But coding with pointers in C is difficult to get right. Get some experience in. |
|
| Back to top |
|
|
|
|
