| Author |
Message
|
| jainvik7 |
 Posted: Tue Jun 26, 2007 4:40 am Post subject: V6 discrepancy in handling null values |
 |
|
Apprentice
Joined: 19 Feb 2006
Posts: 38
|
Has anyone faced a similar problem. We are in the process of migrating from V5 to V6. However, the trace results for v6 seem to delete the value which was assigned ' ' ' ' in V5. -->
v6
-----
2007-06-26 09:25:12.458058 36 UserTrace BIP2539I: Node 'com.hm.XXXXXXXX_PROCESS.XXXXXXXX ORDERS THIN INTERMEDIATE SUBFLOW.XXXXXXXX ORDERS THIN Events Reformat': Evaluating expression ''RTRIM(INREF.SYSOWN(1).DataValue)'' at ('com.hm.Build_XXXXXXXX_THIN_AASNMOD_Message', '28.33'). This resolved to ''RTRIM(NULL, NULL)''. The result was ''NULL''.
2007-06-26 09:25:12.458089 36 UserTrace BIP2567I: Node 'com.hm.XXXXXXXX_PROCESS.XXXXXXXX ORDERS THIN INTERMEDIATE SUBFLOW.XXXXXXXX ORDERS THIN Events Reformat': Assigning NULL to ''OUTREF.SYSOWN(1)'', thus deleting it.
---
v5
---
2007-06-26 13:58:16.353306 31 UserTrace BIP2539I: Node 'com.hm.XXXXXXXX_PROCESS.XXXXXXXX ORDERS THIN Events Reformat': Finished evaluating expression 'RTRIM(INREF.SYSOWN(1).DataValue)' at (com.hm.Build_XXXXXXXX_THIN_AASNMOD_Message, 28.33). This resolved to 'RTRIM('')'. The result was ''''.
2007-06-26 13:58:16.353359 31 UserTrace BIP2566I: Node 'com.hm.XXXXXXXX_PROCESS.XXXXXXXX ORDERS THIN Events Reformat': Assigning value '''' to field / variable 'OUTREF.SYSOWN(1)'. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jun 26, 2007 5:23 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
You'll have to tell us more about your message flow.
Which domain are you using?
How was your message tree constructed? |
|
| Back to top |
|
|
| jainvik7 |
| Posted: Tue Jun 26, 2007 11:34 pm Post subject: |
|
|
Apprentice
Joined: 19 Feb 2006
Posts: 38
|
kimbert
-- > Initially message is received as BLOB, then we convert it into MRM domain with Message format as TDS.
-- > message tree is contructed using TDS parser... |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jun 27, 2007 2:01 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| I still cannot diagnose your problem using the information you have provided. Please provide the input message and a trace of the message tree. Highlight the element which is different in v6. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 27, 2007 2:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
I believe the difference here is hit on assigning a value.
V5 the value was '' => empty string (not a null value)
V6 the value is NULL => if not careful will remove the element in XML.
If the element is mandatory but nillable you should change your assignment to be:
SET tree.targetelement VALUE = NULL;
This will create the targetelement and assign a null value.
When doing the alternat assignment:
SET tree.targetelement = NULL; you are effectively removing targetelement from the tree...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
