| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ESQL Problem - null data values |
« View previous topic :: View next topic » |
| Author |
Message
|
| fat_tony |
 Posted: Sat Dec 02, 2006 7:51 am Post subject: ESQL Problem - null data values |
 |
|
Novice
Joined: 02 Dec 2006
Posts: 15
|
Hi
I'm having a problem with some ESQL code which is leading to an exception further down the line, can anyone help me?
Broker & Toolkit v6.0.0.2 on Windows.
I'm passing some XML into a flow and setting the domain to XMLNSC in the MQInput node. I'm not using Message Sets right now (although I will be soon) but I'd still like to know why it's happening. The following is from a trace node immediately before my ESQL Compute node:
| Quote: |
UserTrace BIP2539I: Node 'FLOW_A.Trace': Evaluating expression ''Root.XMLNSC'' at ('', '1.3'). This resolved to ''Root.XMLNSC''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='XMLNSC' Value=NULL''.
UserTrace BIP4060I: Data ''(
(0x01000000):Request = (
(0x03000000):surname = 'Smith'
(0x03000000):forenames = 'Jeremy John'
(0x01000000):dateOfBirth =
)
) |
Here's my esql:
| Code: |
set OutputRoot.Properties = InputRoot.Properties;
set OutputRoot.MQMD = InputRoot.MQMD;
set OutputRoot.MQRFH2 = InputRoot.MQRFH2;
declare in_xml reference to InputRoot.XMLNSC.Request;
declare surname , forenames , date_of_birth char;
set surname = in_xml.surname;
set forenames = in_xml.forenames;
set date_of_birth = in_xml.dateOfBirth; |
The results of this ESQL are (from trace and also verified by toolkit debug):
surname = Smith
forenames = Jeremy John
date_of_birth = Jeremy John
Why does in_xml.dateOfBirth resolve to the value of in_xml.forenames? I expected this statement to either give date_of_birth a null value or delete the field entirely. If I specify a dateOfBirth on input this works fine, it's just the null value causing this.
Thanks in advance |
|
| Back to top |
|
 |
| kimbert |
| Posted: Sat Dec 02, 2006 11:35 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You are almost certainly encountering a known defect with XMLNSC. My advice would be to raise a PMR. If you do, then please reference this thread on MQSeries.net ( otherwise IBM service might waste a lot of time looking for a known defect ).
The workaround is to use XMLNS instead of XMLNSC. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Feb 02, 2007 1:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| If you raise a PMR you can get an IFix for this. You should ask for a test fix for PMR 12211,999,866. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
