| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Parsing SWIFT message set |
« View previous topic :: View next topic » |
| Author |
Message
|
| jonesn |
 Posted: Tue Jan 31, 2006 8:27 am Post subject: Parsing SWIFT message set |
 |
|
Apprentice
Joined: 09 Jan 2002
Posts: 47
|
Chaps,
I am using WBIMB 5 & the IA0T SWIFT message set and would like to parse my input message. There are three ways to parse these messages: MQInput node, RCD or in eSQL using create lastchild etc...
I have successfully parsed the message using MQInput and RCD but cannot get the eSQL option to work.
For the MQInput node I set the Domain, Message Set & Format in the default tab.
For RCD I set the same three attributes but also check the radio buttons indicating that I want to reset the three attributes.
If I use the following eSQL I get an exception...
| Code: |
set Environment.InputMessage = InputBody;
create lastchild of OutputRoot domain 'MRM'
parse (cast(InputRoot."BLOB"."BLOB" As character
ccsid InputRoot.Properties.CodedCharSetId),
InputRoot.Properties.Encoding,
InputRoot.Properties.CodedCharSetId,
'SWIFT_2005_050615',
'',
'SWIFT'); |
ParserException BIP5136E: Invalid Wire Format Identifier ''.
When processing an MRM message the broker requires a valid wire format identifier.
This code is lifted from the support pack documentation.
Any idea what I am doing wrong?
Thanks
_________________
---
Nick Jones
IBM Certified Solutions Expert (WebSphere MQ Integrator) |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Feb 01, 2006 2:30 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The docs say that the PARSE clause has these parameters:
| Quote: |
|--PARSE--(--BitStreamExpression--+------------------------------+--)--|
| .-<<-----------------------. |
| V | |
'---+-OPTIONS--expression--+-+-'
+-ENCODING--expression-+
+-CCSID--expression----+
+-SET--expression------+
+-TYPE--expression-----+
'-FORMAT--expression---' |
I don't see anything corresponding to OPTIONS in your ESQL. If I'm correct, that would explain why the Wire Format Identfier (i.e. the FORMAT parameter on your parse clause) is being picked up as ''. |
|
| 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
|
|
|
|
