MQSeries.net :: View topic - MQSI to WBIMB Trace Script Output

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSI to WBIMB Trace Script Output

MQSI to WBIMB Trace Script Output

« View previous topic :: View next topic »

Author

Message

catwood2

Posted: Wed Mar 09, 2005 3:54 pm Post subject: MQSI to WBIMB Trace Script Output

Centurion

Joined: 17 May 2002
Posts: 108

Hi,
Any assistance appreciated. This may be a wmqi->wbimb learning curve.

I am running trace scripts on a message flow (basically from the support pac to automate running the trace commands and formatting the output):

Code:

system ("mqsichangetrace $broker -u -e $execution_group -f $message_flow -l normal -r");
system ("mqsichangetrace $broker -u -e $execution_group -f $message_flow -l none");
system ("mqsireadlog $broker -u -e $execution_group -o $message_flow.xml -f");
system ("mqsiformatlog -i $message_flow.xml -o $message_flow.txt");

The issue(?) is that when the flow is idle we are getting output around execution group configuration changes. WMQI I would expect "no threads encountered in trace". Specifically, in WBIMB getting:

Code:

Timestamps are formatted in local time, 360 minutes before GMT.
One MQSC command read.
2005-03-09 16:55:15.878776 5655 UserTrace BIP4040I: The Execution Group
'eg0262c1' has processed a configuration message successfully.
A configuration message has been processe
d successfully. Any configuration changes have been made and stored persistently
. bReq.pl HubAutomationRetryFlow.txt
No user action required.
2005-03-09 16:55:15.879423 5655 UserTrace BIP2638I: The MQ output node '
ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYST
EM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0262'. The MQCC
was '0' and the MQRC was '0'.
2005-03-09 16:55:15.879438 5655 UserTrace BIP2622I: Message successfully
output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BR
OKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0262'.
of incoming message of length '364' bytes beginning at offset '0'. Parser type s
elected based on value 'MQHMD' from previous parser. gurationMessageFlow.InputNo
2005-03-09 16:55:46.072818 5655 UserTrace BIP6061I: Parser type 'XML' cr
eated on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion o
f incoming message of length '234' bytes beginning at offset '364'. Parser type
selected based on value 'XML' from previous parser. g at offset '0'.
2005-03-09 16:55:46.076423 5655 UserTrace BIP4040I: The Execution Group
'eg0262c1' has processed a configuration message successfully. o handle portion
A configuration message has been processe
d successfully. Any configuration changes have been made and stored persistently
.
No user action required.
2005-03-09 16:55:46.077713 5655 UserTrace BIP2638I: The MQ output node '
ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYST
EM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0262'. The MQCC
ies' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle po
rtion of incoming message of length 0 bytes beginning at offset '0'. uccessfully
2005-03-09 16:55:46.198417 5655 UserTrace BIP6061I: Parser type 'MQMD' c
reated on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion
of incoming message of length '364' bytes beginning at offset '0'. Parser type s
elected based on value 'MQHMD' from previous parser. gurationMessageFlow.InputNo
2005-03-09 16:55:46.199096 5655 UserTrace BIP6061I: Parser type 'XML' cr
eated on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion o
f incoming message of length '307' bytes beginning at offset '364'. Parser type
selected based on value 'XML' from previous parser.
2005-03-09 16:55:46.559398 5655 UserTrace BIP2265I: Attribute in message
flow 'ADebitCardRequest' (uuid='2a835ebd-ff00-0000-0080-c5a2e446e26f') successf
ully changed.
The message broker received a configurati
on message containing an instruction to change an attribute in the message flow
No user action required.
2005-03-09 16:55:46.680797 5655 UserTrace BIP2638I: The MQ output node '
ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYST
hofsorlab06c/home/wbimb/csc_scripts#>
was '0' and the MQRC was '0'. figuration message successfully.
2005-03-09 16:55:46.680812 5655 UserTrace BIP2622I: Message successfully
output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BR
OKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0262'.

Threads encountered in this trace:

I searched around on this ConfigurationMessageFlow and the only references were in examples that weren't going into what this is. Basically, it's being reported there is an intermittent issue with this flow (not servicing the queue...unless broker is bounced) and I am not sure if this is any sort of indication of issue. Thoughts appreciated.
thx
chris

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQSI to WBIMB Trace Script Output

Jump to:

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

Protected by Anti-Spam ACP