| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| recover log from partial data |
« View previous topic :: View next topic » |
| Author |
Message
|
| jcv |
 Posted: Wed May 09, 2007 6:13 am Post subject: |
 |
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
It uses an obsolete version:
$ mqver
MQSeries Version: 520
CMVC level: p520-CSD07G
BuildType: IKAP - (Production)
I didn't search for issues yet, because I know I have to upgrade server, so if the problem is in this mq version it will be solved with upgrade.
Most of the applications use bindings, but there are also MQ client applications. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed May 09, 2007 6:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm sure your problem will be solved by moving to v6.
And several others that you haven't run into yet.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jcv |
| Posted: Wed May 09, 2007 8:33 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
I suppose there is a complete backward compatibility for both bindings and client applications regarding communication with MQ server, meaning that they don't have to be rebuilt when upgrading from v5.2 to v6?
Last edited by jcv on Fri May 25, 2007 3:09 am; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 09, 2007 9:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, I'm sure you'll have to recompile.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jcv |
| Posted: Fri May 25, 2007 4:05 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
Let's get back to tracing API calls. I have adjusted amqsaxe0.c to my needs for testing environments, where performance degradation is not so relevant or critical. I have commented out logic which requires an adequate environment variable to be set for logging to occur, something like this:
| Code: |
//env = getenv( "MQAPI_TRACE_LOGFILE" );
//if (env){
/***************************************************************/
/* Open the log file */
/***************************************************************/
. . .
//}
|
I don't understand why I'm not able to catch any other API calls except for MQXE_OTHER environment, that is, none of these:
MQXE_MCA, MQXE_MCA_SVRCONN, MQXE_COMMAND_SERVER, MQXE_MQSC, although I'm connecting to observed qmgr with runmqsc, strmqcsv, client configured mo71, but nothing except for binding applications activity can be seen in logs. And that appears regardless of env setting, so this definitely is not a problem. Also, I don't know how to provoke MQXACT_INTERNAL records, too, although, I suppose qmgr is issuing some API calls too, from time to time. |
|
| Back to top |
|
|
| jcv |
| Posted: Fri May 25, 2007 5:04 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
The reason nothing is logged, is because when I issue for example runmqsc, it logs:
-------------------------------------------------------------------------------
2007. 05. 25 14:38:28
AMQ7217: The response set by the exit is not valid.
EXPLANATION:
The Api Exit '' module '' function'' returned a response code '-8' that is not
valid in the ExitResponse field of the Api Exit parameters (MQAXP).
ACTION:
Investigate why the Api Exit '' set a response code that is not valid.
-------------------------------------------------------------------------------
-8 stands for MQXCC_FAILED, so that I really have to investigate why api exit returns this value, when I start for example runmqsc,
and why it returns MQXCC_OK when I start for example amqsput, in which case everything is properly traced. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
