| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Substitution Group Odd Errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| dmw1986 |
 Posted: Wed Oct 22, 2008 5:17 am Post subject: Substitution Group Odd Errors |
 |
|
Apprentice
Joined: 24 Sep 2008
Posts: 35
|
There seems to be a problem with substition groups within Message Broker. On the schema side this is one example. When trying to autocomplete within the schema to the correct element, there are certain ones that dont work. For example Eye Color. When autocompleting it completes to this.
| Code: |
| SET OutputRoot.MRM.CJ37CI80_INPUT_DATA.CJ37CI80_EYE = InputRoot.XMLNSC.mo_warrant:Warrant.mo_warrant:Person.nc:PersonEyeColor |
However if you look in the XML message we created based off the schema it looks like this as an example.
| Code: |
<mo-warrant:Person s:id="P1">
<nc:PersonEyeColorCode>BLU</nc:PersonEyeColorCode>
|
So if I hard code the value like below it picks up ‘BLU’ while in debug but it will not write it to MQ or email. (see node output below)
| Code: |
SET OutputRoot.MRM.CJ37CI80_INPUT_DATA.CJ37CI80_EYE = InputRoot.XMLNSC.mo_warrant:Warrant.mo_warrant:Person.nc:PersonEyeColorCode; |
If you look at the email Output, among other ones with these type of substition groups they dont get written. Heres the output of that email node. Notice theres no HAI, RAC, ORI, DOB, LNM, FNM, MNM, etc... These are all fields that you cant autocomplete to in the ESQL because of substition groups i’m guessing. But actually typing in the path like above gets you the data in debug mode but its like it loses it when it outputs it.
| Code: |
| EW WC00OSCIOSCIOSCI X'414D51204D5348505F514D2020202020F82AFE4820002006' ABCD 1 LIMITATION TEXT 12345678 JEFFERSON 026MO 12345678901234567890 2001 1100 ELM STREET JEFFERSON CITY 026MO H |
Any ideas on why in debug it finds the data and puts it in the right spot in COBOL include but it wont right it to message? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Oct 22, 2008 12:58 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| There seems to be a problem with substition groups within Message Broker. On the schema side this is one example. When trying to autocomplete within the schema to the correct element, there are certain ones that dont work |
That's possible. Substitution groups are pretty contact admin. There may be a defect in the ESQL autocomplete.
Suggestion: Look carefully at the schema and see whether 'PersonEyeColor' is defined as 'abstract'. If it is, then the autocomplete is quite correct not to offer it.
| Quote: |
| Any ideas on why in debug it finds the data and puts it in the right spot in COBOL include but it wont right it to message? |
Well, the debugger is showing you the message tree, not the output message. I can think of lots of reasons why the CWF output message would omit data that was in the message tree.
The first thing I would do is take a debug-level user trace, and look for warnings. |
|
| 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
|
|
|
|
