ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP5219E: invalid tag name; parent element '{4}'; current el

Post new topic  Reply to topic
 BIP5219E: invalid tag name; parent element '{4}'; current el « View previous topic :: View next topic » 
Author Message
shcherb
PostPosted: Mon Sep 17, 2001 3:12 am    Post subject: Reply with quote

Apprentice

Joined: 12 Sep 2001
Posts: 34

Hello,

I have a parsing error with XML netsale2 message set: wrong tag. I checked every tag, and it seems to be OK. Any ideas ?
I am working with MQSeries 5.2/MQSI 2.02 on Windows NT Server SP6a. Below is trace file:

2001-08-21 17:19:10.545999 1055 UserTrace BIP2638E: MQPUT to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'ConfigurationMessageFlow.outputNode'.
The node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:19:10.545999 1055 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'ConfigurationMessageFlow.outputNode' successfully wrote an output message to the specified queue SYSTEM.BROKER.EXECUTIONGROUP.REPLY connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP2632I: Message being propagated to the output terminal; node 'ConfigurationMessageFlow.InputNode'.
An input message received from MQSeries input queue in node 'ConfigurationMessageFlow.InputNode' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '276' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
The message broker has created a parser of type 'XML' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '276' bytes long. This parser type was selected as the best match given the value 'XML' from the previous parser.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP4040I: The execution group 'test1' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP2638E: MQPUT to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'ConfigurationMessageFlow.outputNode'.
The node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:19:11.420999 1055 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'ConfigurationMessageFlow.outputNode' successfully wrote an output message to the specified queue SYSTEM.BROKER.EXECUTIONGROUP.REPLY connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-21 17:19:41.187000 1909 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'netsale2.ECI_IN' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-21 17:19:41.187000 1909 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'netsale2.ECI_IN' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-21 17:19:41.187000 1909 UserTrace BIP2632I: Message being propagated to the output terminal; node 'netsale2.ECI_IN'.
An input message received from MQSeries input queue in node 'netsale2.ECI_IN' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-21 17:19:41.187000 1909 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length '508' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
The message broker has created a parser of type 'MRM' on behalf of node 'netsale2.ECI_IN' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '508' bytes long. This parser type was selected as the best match given the value 'MRM' from the previous parser.
No user action required.
2001-08-21 17:19:41.187000 1909 UserTrace BIP2538I: Node 'netsale2.Trace1': Evaluating expression 'Root' at (1, 3).
The expression being evaluated was 'Root'.
No user action required.
2001-08-21 17:19:41.187000 1909 UserTrace BIP4060I: Data '(
(0x1000000)Properties = (
(0x3000000)MessageSet = 'DMBEARO072001'
(0x3000000)MessageType = 'netsale2'
(0x3000000)MessageFormat = 'XML'
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2001-08-21 15:19:41.180'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'ECI_IN'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Format = 'MQSTR '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d51204d5153495f53414d504c455f6030823ba2b60000'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'MQSI_SAMPLE_QM '
(0x3000000)UserIdentifier = 'yuri '
(0x3000000)AccountingToken = X'16010515000000fb6d27470b685f10bf7df76dea03000000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = 'C:WINNTSystem32mmc.exe '
(0x3000000)PutDate = DATE '2001-08-21'
(0x3000000)PutTime = GMTTIME '15:19:41.180'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000008)MRM = ' from Trace node 'netsale2.Trace1'.
The Trace node 'netsale2.Trace1' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2001-08-21 17:19:41.202999 1909 Error BIP2628E: Exception condition detected on input node 'netsale2.ECI_IN'.
The input node 'netsale2.ECI_IN' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2001-08-21 17:19:41.202999 1909 RecoverableException BIP2230E: Error detected whilst processing a message in node 'netsale2.Trace1'.
The message broker detected an error whilst processing a message in node 'netsale2.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2001-08-21 17:19:41.202999 1909 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
2001-08-21 17:19:41.202999 1909 ParserException BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2001-08-21 17:19:41.202999 1909 ParserException BIP5219E: Message Translation Interface error. Invalid tag name: message set 'DMBEARO072001'; message 'netsale2'; parent element '{4}'; current element '{5}'.
This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
Check that the XML message contains the correct tags for the message type defined in the message set given above.
2001-08-21 17:19:41.202999 1909 UserTrace BIP2231E: Error detected whilst processing a message 'netsale2.ECI_IN'.
The message broker detected an error whilst processing a message in node 'netsale2.ECI_IN'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2001-08-21 17:19:41.202999 1909 RecoverableException BIP2230E: Error detected whilst processing a message in node 'netsale2.Trace1'.
The message broker detected an error whilst processing a message in node 'netsale2.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2001-08-21 17:19:41.202999 1909 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
2001-08-21 17:19:41.202999 1909 ParserException BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2001-08-21 17:19:41.202999 1909 ParserException BIP5219E: Message Translation Interface error. Invalid tag name: message set 'DMBEARO072001'; message 'netsale2'; parent element '{4}'; current element '{5}'.
This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
Check that the XML message contains the correct tags for the message type defined in the message set given above.
2001-08-21 17:19:41.202999 1909 UserTrace BIP2638E: MQPUT to queue 'ECI_FAILURE' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'netsale2.ECI_FAILURE'.
The node 'netsale2.ECI_FAILURE' attempted to write a message to the specified queue 'ECI_FAILURE' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:19:41.202999 1909 UserTrace BIP2622I: Message successfully output by output node 'netsale2.ECI_FAILURE' to queue 'ECI_FAILURE' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'netsale2.ECI_FAILURE' successfully wrote an output message to the specified queue ECI_FAILURE connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-21 17:20:05.484000 1055 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-21 17:20:05.484000 1055 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-21 17:20:05.484000 1055 UserTrace BIP2632I: Message being propagated to the output terminal; node 'ConfigurationMessageFlow.InputNode'.
An input message received from MQSeries input queue in node 'ConfigurationMessageFlow.InputNode' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-21 17:20:05.484000 1055 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '239' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
The message broker has created a parser of type 'XML' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '239' bytes long. This parser type was selected as the best match given the value 'XML' from the previous parser.
No user action required.
2001-08-21 17:20:05.500000 1055 UserTrace BIP4040I: The execution group 'test1' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2001-08-21 17:20:05.500000 1055 UserTrace BIP2638E: MQPUT to queue 'AMQ.3B82306000235012' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'ConfigurationMessageFlow.outputNode'.
The node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'AMQ.3B82306000235012' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:20:05.500000 1055 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'AMQ.3B82306000235012' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'ConfigurationMessageFlow.outputNode' successfully wrote an output message to the specified queue AMQ.3B82306000235012 connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'netsale2.ECI_IN' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'netsale2.ECI_IN' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP2632I: Message being propagated to the output terminal; node 'netsale2.ECI_IN'.
An input message received from MQSeries input queue in node 'netsale2.ECI_IN' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length '508' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
The message broker has created a parser of type 'MRM' on behalf of node 'netsale2.ECI_IN' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '508' bytes long. This parser type was selected as the best match given the value 'MRM' from the previous parser.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP2538I: Node 'netsale2.Trace1': Evaluating expression 'Root' at (1, 3).
The expression being evaluated was 'Root'.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP4060I: Data '(
(0x1000000)Properties = (
(0x3000000)MessageSet = 'DMBEARO072001'
(0x3000000)MessageType = 'netsale2'
(0x3000000)MessageFormat = 'XML'
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2001-08-21 15:24:29.760'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'ECI_IN'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Format = 'MQSTR '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d51204d5153495f53414d504c455f6030823be2b60000'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'MQSI_SAMPLE_QM '
(0x3000000)UserIdentifier = 'yuri '
(0x3000000)AccountingToken = X'16010515000000fb6d27470b685f10bf7df76dea03000000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = 'C:WINNTSystem32mmc.exe '
(0x3000000)PutDate = DATE '2001-08-21'
(0x3000000)PutTime = GMTTIME '15:24:29.760'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000008)MRM = ' from Trace node 'netsale2.Trace1'.
The Trace node 'netsale2.Trace1' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2001-08-21 17:24:29.764999 1909 Error BIP2628E: Exception condition detected on input node 'netsale2.ECI_IN'.
The input node 'netsale2.ECI_IN' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2001-08-21 17:24:29.764999 1909 RecoverableException BIP2230E: Error detected whilst processing a message in node 'netsale2.Trace1'.
The message broker detected an error whilst processing a message in node 'netsale2.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2001-08-21 17:24:29.764999 1909 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
2001-08-21 17:24:29.764999 1909 ParserException BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2001-08-21 17:24:29.764999 1909 ParserException BIP5219E: Message Translation Interface error. Invalid tag name: message set 'DMBEARO072001'; message 'netsale2'; parent element '{4}'; current element '{5}'.
This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
Check that the XML message contains the correct tags for the message type defined in the message set given above.
2001-08-21 17:24:29.764999 1909 UserTrace BIP2231E: Error detected whilst processing a message 'netsale2.ECI_IN'.
The message broker detected an error whilst processing a message in node 'netsale2.ECI_IN'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2001-08-21 17:24:29.764999 1909 RecoverableException BIP2230E: Error detected whilst processing a message in node 'netsale2.Trace1'.
The message broker detected an error whilst processing a message in node 'netsale2.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2001-08-21 17:24:29.764999 1909 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
2001-08-21 17:24:29.764999 1909 ParserException BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2001-08-21 17:24:29.764999 1909 ParserException BIP5219E: Message Translation Interface error. Invalid tag name: message set 'DMBEARO072001'; message 'netsale2'; parent element '{4}'; current element '{5}'.
This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
Check that the XML message contains the correct tags for the message type defined in the message set given above.
2001-08-21 17:24:29.764999 1909 UserTrace BIP2638E: MQPUT to queue 'ECI_FAILURE' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'netsale2.ECI_FAILURE'.
The node 'netsale2.ECI_FAILURE' attempted to write a message to the specified queue 'ECI_FAILURE' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:24:29.764999 1909 UserTrace BIP2622I: Message successfully output by output node 'netsale2.ECI_FAILURE' to queue 'ECI_FAILURE' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'netsale2.ECI_FAILURE' successfully wrote an output message to the specified queue ECI_FAILURE connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'netsale2.ECI_IN' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'netsale2.ECI_IN' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP2632I: Message being propagated to the output terminal; node 'netsale2.ECI_IN'.
An input message received from MQSeries input queue in node 'netsale2.ECI_IN' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'netsale2.ECI_IN' to handle portion of incoming message of length '508' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
The message broker has created a parser of type 'MRM' on behalf of node 'netsale2.ECI_IN' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '508' bytes long. This parser type was selected as the best match given the value 'MRM' from the previous parser.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP2538I: Node 'netsale2.Trace1': Evaluating expression 'Root' at (1, 3).
The expression being evaluated was 'Root'.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP4060I: Data '(
(0x1000000)Properties = (
(0x3000000)MessageSet = 'DMBEARO072001'
(0x3000000)MessageType = 'netsale2'
(0x3000000)MessageFormat = 'XML'
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2001-08-21 15:24:52.060'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'ECI_IN'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Format = 'MQSTR '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d51204d5153495f53414d504c455f6030823b02b70000'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'MQSI_SAMPLE_QM '
(0x3000000)UserIdentifier = 'yuri '
(0x3000000)AccountingToken = X'16010515000000fb6d27470b685f10bf7df76dea03000000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = 'C:WINNTSystem32mmc.exe '
(0x3000000)PutDate = DATE '2001-08-21'
(0x3000000)PutTime = GMTTIME '15:24:52.060'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000008)MRM = ' from Trace node 'netsale2.Trace1'.
The Trace node 'netsale2.Trace1' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2001-08-21 17:24:52.062000 1909 Error BIP2628E: Exception condition detected on input node 'netsale2.ECI_IN'.
The input node 'netsale2.ECI_IN' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2001-08-21 17:24:52.062000 1909 RecoverableException BIP2230E: Error detected whilst processing a message in node 'netsale2.Trace1'.
The message broker detected an error whilst processing a message in node 'netsale2.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2001-08-21 17:24:52.062000 1909 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
2001-08-21 17:24:52.062000 1909 ParserException BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2001-08-21 17:24:52.062000 1909 ParserException BIP5219E: Message Translation Interface error. Invalid tag name: message set 'DMBEARO072001'; message 'netsale2'; parent element '{4}'; current element '{5}'.
This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
Check that the XML message contains the correct tags for the message type defined in the message set given above.
2001-08-21 17:24:52.062000 1909 UserTrace BIP2231E: Error detected whilst processing a message 'netsale2.ECI_IN'.
The message broker detected an error whilst processing a message in node 'netsale2.ECI_IN'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2001-08-21 17:24:52.062000 1909 RecoverableException BIP2230E: Error detected whilst processing a message in node 'netsale2.Trace1'.
The message broker detected an error whilst processing a message in node 'netsale2.Trace1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2001-08-21 17:24:52.062000 1909 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
2001-08-21 17:24:52.062000 1909 ParserException BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2001-08-21 17:24:52.062000 1909 ParserException BIP5219E: Message Translation Interface error. Invalid tag name: message set 'DMBEARO072001'; message 'netsale2'; parent element '{4}'; current element '{5}'.
This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
Check that the XML message contains the correct tags for the message type defined in the message set given above.
2001-08-21 17:24:52.062000 1909 UserTrace BIP2638E: MQPUT to queue 'ECI_FAILURE' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'netsale2.ECI_FAILURE'.
The node 'netsale2.ECI_FAILURE' attempted to write a message to the specified queue 'ECI_FAILURE' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:24:52.062000 1909 UserTrace BIP2622I: Message successfully output by output node 'netsale2.ECI_FAILURE' to queue 'ECI_FAILURE' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'netsale2.ECI_FAILURE' successfully wrote an output message to the specified queue ECI_FAILURE connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-21 17:25:04.436999 1055 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-21 17:25:04.436999 1055 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-21 17:25:04.436999 1055 UserTrace BIP2632I: Message being propagated to the output terminal; node 'ConfigurationMessageFlow.InputNode'.
An input message received from MQSeries input queue in node 'ConfigurationMessageFlow.InputNode' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-21 17:25:04.436999 1055 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '239' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
The message broker has created a parser of type 'XML' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '239' bytes long. This parser type was selected as the best match given the value 'XML' from the previous parser.
No user action required.
2001-08-21 17:25:04.467999 1055 UserTrace BIP4040I: The execution group 'test1' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2001-08-21 17:25:04.467999 1055 UserTrace BIP2638E: MQPUT to queue 'AMQ.3B8230600023E032' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'ConfigurationMessageFlow.outputNode'.
The node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'AMQ.3B8230600023E032' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-21 17:25:04.467999 1055 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'AMQ.3B8230600023E032' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'ConfigurationMessageFlow.outputNode' successfully wrote an output message to the specified queue AMQ.3B8230600023E032 connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-22 10:35:18.264999 1055 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-22 10:35:18.264999 1055 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-22 10:35:18.264999 1055 UserTrace BIP2632I: Message being propagated to the output terminal; node 'ConfigurationMessageFlow.InputNode'.
An input message received from MQSeries input queue in node 'ConfigurationMessageFlow.InputNode' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-22 10:35:18.264999 1055 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '176' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
The message broker has created a parser of type 'XML' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '176' bytes long. This parser type was selected as the best match given the value 'XML' from the previous parser.
No user action required.
2001-08-22 10:35:18.264999 1055 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication node with Subscription Point '' has received a message of type Publish.
The Publication node with Subscription Point '' has started processing a message.
No user action required.
2001-08-22 10:35:18.264999 1055 UserTrace BIP7082I: Node '{2}': Publishing to destination MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
A publication destination is being added to the list of destinations to MQSI_SAMPLE_QM:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233 for user mqsiuid.
No user action required.
2001-08-22 10:35:18.281000 1055 UserTrace BIP7081I: The Publication node has matched 1 subscriptions to topic '$SYS/Broker/MQSI_SAMPLE_BROKER/Status/ExecutionGroup/test1' for subscription point ''.
The Publication node has matched subscriptions for the current publication and topic.
No user action required.
2001-08-22 10:35:18.281000 1055 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication node has propagated a message to its Output terminal for subscription point ''.
The Publication node has propagated the current message to its Output terminal.
No user action required.
2001-08-22 10:35:18.281000 1055 UserTrace BIP2638E: MQPUT to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'PubSubControlMsgFlow.ListOutputNode'.
The node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-22 10:35:18.281000 1055 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'PubSubControlMsgFlow.ListOutputNode' successfully wrote an output message to the specified queue SYSTEM.BROKER.ADMIN.REPLY connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-22 10:35:18.281000 1055 UserTrace BIP4040I: The execution group 'test1' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2001-08-22 10:35:240000000 2125 Information BIP2204I: Execution group using process '2112' thread '2125' stopped.
The execution group using process '2112' and thread '2125' has stopped. This may be because it has been instructed to do so or because it has encountered a problem.
No user action required. The execution group will be restarted automatically if need be.
2001-08-22 10:40:10.390000 2964 Error BIP2300E: File 'D:IBMMQSeries Integrator 2.0binimbdfneo.lil' could not be loaded; operating system return code '126'.
The message broker detected the loadable implementation file 'D:IBMMQSeries Integrator 2.0binimbdfneo.lil' but this could not be loaded by the operating system. The operating system return code was '126'.
Determine the cause of the load failure by analysing the operating system return code. If necessary contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
2001-08-22 10:40:10.875000 2964 Error BIP2300E: File 'D:IBMMQSeries Integrator 2.0binNEONMapTransform.lil' could not be loaded; operating system return code '126'.
The message broker detected the loadable implementation file 'D:IBMMQSeries Integrator 2.0binNEONMapTransform.lil' but this could not be loaded by the operating system. The operating system return code was '126'.
Determine the cause of the load failure by analysing the operating system return code. If necessary contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
2001-08-22 10:40:10.890000 2964 Error BIP2300E: File 'D:IBMMQSeries Integrator 2.0binNEONMSGParser.lil' could not be loaded; operating system return code '126'.
The message broker detected the loadable implementation file 'D:IBMMQSeries Integrator 2.0binNEONMSGParser.lil' but this could not be loaded by the operating system. The operating system return code was '126'.
Determine the cause of the load failure by analysing the operating system return code. If necessary contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
2001-08-22 10:40:10.906000 2964 Error BIP2300E: File 'D:IBMMQSeries Integrator 2.0binNEONRulesEvaluation.lil' could not be loaded; operating system return code '126'.
The message broker detected the loadable implementation file 'D:IBMMQSeries Integrator 2.0binNEONRulesEvaluation.lil' but this could not be loaded by the operating system. The operating system return code was '126'.
Determine the cause of the load failure by analysing the operating system return code. If necessary contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
2001-08-22 10:40:12.170999 2963 UserTrace BIP2638E: MQPUT to queue 'SYSTEM.BROKER.CONTROL.QUEUE' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'PubSubControlMsgFlow.MainControlOutputNode'.
The node 'PubSubControlMsgFlow.MainControlOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.CONTROL.QUEUE' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-22 10:40:12.170999 2963 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.MainControlOutputNode' to queue 'SYSTEM.BROKER.CONTROL.QUEUE' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'PubSubControlMsgFlow.MainControlOutputNode' successfully wrote an output message to the specified queue SYSTEM.BROKER.CONTROL.QUEUE connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-22 10:40:12.265000 2963 UserTrace BIP2638E: MQPUT to queue 'SYSTEM.BROKER.CONTROL.QUEUE' on queue manager 'MQSI_SAMPLE_QM': MQCC=0, MQRC=0; node 'PubSubControlMsgFlow.MainControlOutputNode'.
The node 'PubSubControlMsgFlow.MainControlOutputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.CONTROL.QUEUE' connected to queue manager 'MQSI_SAMPLE_QM'. The MQCC was 0 and the MQRC was 0.
No user action required.
2001-08-22 10:40:12.265000 2963 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.MainControlOutputNode' to queue 'SYSTEM.BROKER.CONTROL.QUEUE' on queue manager 'MQSI_SAMPLE_QM'.
The MQSeries Integrator output node 'PubSubControlMsgFlow.MainControlOutputNode' successfully wrote an output message to the specified queue SYSTEM.BROKER.CONTROL.QUEUE connected to queue manager MQSI_SAMPLE_QM.
No user action required.
2001-08-22 10:40:12.890000 2968 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'PubSubControlMsgFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'PubSubControlMsgFlow.InputNode' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2001-08-22 10:40:12.890000 2968 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'PubSubControlMsgFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'PubSubControlMsgFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2001-08-22 10:40:12.890000 2968 UserTrace BIP2632I: Message being propagated to the output terminal; node 'PubSubControlMsgFlow.InputNode'.
An input message received from MQSeries input queue in node 'PubSubControlMsgFlow.InputNode' is being propagated to any nodes connected to the Output terminal.
No user action required.
2001-08-22 10:40:12.890000 2968 UserTrace BIP6061I: Parser type 'MQRFH2' created on behalf of node 'PubSubControlMsgFlow.InputNode' to handle portion of incoming message of length '448' bytes beginning at offset '364'. Parser type selected based on value 'MQHRF2' from previous parser.
The message broker has created a parser of type 'MQRFH2' on behalf of node 'PubSubControlMsgFlow.InputNode' to hand
Back to top
View user's profile Send private message Send e-mail
CodeCraft
PostPosted: Wed Sep 19, 2001 5:00 am    Post subject: Reply with quote

Disciple

Joined: 05 Sep 2001
Posts: 195

Check the earlier messages. It seems the definition for the message you've supplied can't be found:

BIP5153E: Retrieving Message Definition from dictionary: message 'netsale2'; message set 'DMBEARO072001'.
When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.

Ensure that the message and message set are accurate in both make up and case, and that the set has actually been deployed to the broker.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP5219E: invalid tag name; parent element '{4}'; current el
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.