| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Difference between CREATE LASTCHILD and SET statements |
« View previous topic :: View next topic » |
| Author |
Message
|
| kimbert |
 Posted: Mon Dec 15, 2014 12:06 pm Post subject: |
 |
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Even if I put trace node after and trace gets creates, I do not have right (mqm) access to see the trace file in a new place I am in. |
OK - I have heard of other users with similar problems. Maybe you should talk to the management about getting the Developer Edition of IIB installed. It's free, and comes with a broker that you can use for testing your flows.
| Quote: |
| I am not understanding, why parser is expecting a comment or processing instruction instead of a folder type. |
Can you attach a debugger? Or is that not allowed either? If you can, then put a breakpoint just before the output node.
You will see that this code:
| Code: |
| CREATE LASTCHILD OF OutputRoot AS RF_ErrorDetails DOMAIN 'XMLNSC' NAME 'CombinedErrorDetails'; |
produces this message tree:
| Code: |
OutputRoot
Properties
[MQMD] -- only if you are using an MQOutput node
CombinedErrorDetails |
but this code:
| Code: |
| SET OutputRoot.XMLNSC.CombinedErrorDetails = ''; |
produces this message tree:
| Code: |
OutputRoot
Properties
[MQMD] -- only if you are using an MQOutput node
XMLNSC
CombinedErrorDetails |
One aspect of this is easy to understand ( once you see the message trees ): if you ask for 'CombinedErrorDetails' to be the last child of OutputRoot then that is what you will get.
But what about the 'DOMAIN XMLNSC' part. The working ESQL does not say anything about the domain, does it? But when you create an element as a child of the message root,
IF the element name matches one of the known domains THEN the correct domain is automatically assigned.
The rest should be obvious - the error message is from the XMLNSC parser. It is trying to write the message tree that exists under the last child of OutputRoot. But the structure of the tree does not match the structure of a valid XML document so it complains.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
 |
| ghoshly |
| Posted: Mon Dec 15, 2014 12:37 pm Post subject: yes, definitely Single root element for XML |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 327
|
I am able to get the trace done...thanks a lot for your time to describe in detail...
SET statement:
(0x01000000:Folder):XMLNSC = ( ['xmlnsc' : 0x116926b70]
(0x03000000:PCDataField):CombinedErrorDetails = '' (CHARACTER)
(
(0x01000000:Folder ):BrokerDetails = (
CREATE LASTCHILD statement:
(0x01000000:Folder):CombinedErrorDetails = ( ['xmlnsc' : 0x11696fd30]
(0x01000000:Folder ):BrokerDetails = ( |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Dec 15, 2014 2:33 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Excellent - that shows the differences really nicely.
Did you spot this?
| Code: |
| (0x01000000:Folder):CombinedErrorDetails = ( ['xmlnsc' : 0x11696fd30] |
The 'CombinedErrorDetails' has a parser assigned to it, as requested by the DOMAIN clause in the CREATE statement.
So IF you had copied the rest of the message tree ( including the real CombinedErrorDetails and its value ) under that element THEN you would have been able to successfully write the message. In other words, the name 'XMLNSC' in the last child of root is not important. The attached parser is what controls the writing of each child of OutputRoot. But we almost always use 'XMLNSC' because
a) it would confuse everyone otherwise and
b) the domain gets assigned automatically, as described in my previous post.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| 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
|
|
|
|
