| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| White paper: New features of WMQI 2.1 ESQL |
« View previous topic :: View next topic » |
| Author |
Message
|
| kolban |
 Posted: Tue Mar 12, 2002 7:39 am Post subject: |
 |
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
|
| Back to top |
|
 |
| kwelch |
| Posted: Tue Mar 12, 2002 10:17 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Kolban,
I thought this was excellent! I plan on sharing it with the rest of the WMQI developers at our meeting tomorrow. After I read it more closely, I may have some questions for you.
Karen
|
|
| Back to top |
|
|
| kolban |
| Posted: Tue Mar 12, 2002 11:44 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| I would very, VERY, much like feedback on this paper. Please (all y'all) use the forum for feedback. Any direct (unsolicited) email will be ignored (sorry). |
|
| Back to top |
|
|
| bh |
| Posted: Wed Mar 13, 2002 12:21 am Post subject: |
|
|
Acolyte
Joined: 25 Jun 2001
Posts: 61
|
Hi Neil,
About feeback on your paper, first, it's clear and simple. It should be add as an introduction in the WMQI documentation. It has the advantage to explain simply the way data are read and manipulated by WMQI in less than 523 pages !
But I found nothing about new functions like:
- PROPAGATE
- THROW
- SQLCODE, STATE, ERRORTEXT, NATIVERROR
- UUIDASCHAR, UUIDASBLOB
- and Localenvironnment/Environnment (replacing DestinationList).
Some of them are minor but PROPAGATE and THROW are important.
Anyway, thanks for your work. |
|
| Back to top |
|
|
| kolban |
| Posted: Wed Mar 13, 2002 4:36 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| Great feedback ... ok, let me spend some more time and add these extra verbs. Especially if the style is working. I took a radically different approach from the manuals and brought it down to the story of "I'm manipulating trees". The new reference variables were so powerful that I felt they needed to be addressed quickly. May be a while before I get to it though. |
|
| Back to top |
|
|
| mapa |
| Posted: Wed Mar 13, 2002 5:36 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Hi,
I liked your paper alot. Written in a style that I like 
The way of parsing messages as trees is the way it is working in another Integration Broker that I've been using for a couple of years before the IBM Integrator.
However I tried to use references on a flow that I already had.
DECLARE myHeadOut REFERENCE TO "OutputRoot"."MRM"."msgFormat1_HEAD";
DECLARE myHeadIn REFERENCE TO "InputRoot"."¨XML"."msgFormat2_HEAD";
Then mapping fields as myHeadOut."Field1" = myHeadIn."elem1" etc.
Keeping the mapping from "InputRoot"."XML"."msgFormat2_ROW" to "OutputRoot"."MRM"."msgFormat1_ROW" elements as they were.
However the the parsed message in the trace after the compute node represented it as this:
(0x1000000)MQRFH2 = (
blablabla
)
(0x3000000)Field1 = 'val1'
(0x3000000)Field2 = 'val2'
(0x3000000)Field2 = 'val3'
.
.
(0x1000008)MRM = (
(0x1000000)msgFormat1_ROW = (
(0x3000000)FieldA = 'valA'
(0x3000000)FieldB = 'valB'
)
)
This the MRM can't serialize.
What I am expecting is to place my head under the OutputRoot.MRM.msgFormat1_HEAD as it did when not using a reference, but it does clearly not. Why?
Not sure this should go in here, but it was a result of trying out what you stated in your whitepaper...
Best regards Magnus Palmer
[ This Message was edited by: mapa on 2002-03-13 05:39 ]
[ This Message was edited by: mapa on 2002-03-13 05:40 ] |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Thu Mar 14, 2002 1:59 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Hi Neil,
Great document, good bedtime reading. I look forward to the additions of the other statements/functions.
Two minor notes on the current text, both regarding new features in V2.1:
- Page 2 MRM, I mis any reference to the new Tagged/Delimited physical binding and import from DTD.
- Page 19 Writable trees, DestinationList is now called LocalEnvironment (both refering to the same area for backward compatability), and the new Environment tree is also a writable tree.
Thanks for your work,
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| 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
|
|
|
|
