|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Modelling a general SWIFT FIN message |
« View previous topic :: View next topic » |
Author |
Message
|
billybong |
Posted: Mon Oct 22, 2007 4:26 am Post subject: Modelling a general SWIFT FIN message |
|
|
 Disciple
Joined: 22 Jul 2005 Posts: 150 Location: Stockholm, Sweden
|
Hi all!
I'm having some difficulties while modelling a general SWIFT Message which should be used for all types of MT's.
I'm not really interested in validating my messages so all I need to achieve is to put everything in its corresponding elements so I can build logic based on the field blocks.
My problem is with the third block, the User Header.
Sample SWIFT message
{1:F01BANKBEBB2222123456}{2:I100BANKDEFFXXXXU3003}{3:{113:xxxx}{108:abcdefgh12345678}}{4:CRLF
:20:PAYREFTB54302 CRLF
:32A:970103BEF1000000,CRLF
:50:CUSTOMER NAME CRLF
AND ADDRESS CRLF
:59:/123-456-789 CRLF
BENEFICIARY NAME CRLF
AND ADDRESS CRLF
-}{5:{MAC:12345678}{CHK:123456789ABC}
I want to parse the third block and create fields with the names based on the TAG name, ie 113 or 108. Since the third field can contain several different groups I dont want to model every possible field.
For the entire message:
DES= Tagged Delimited
Group indicator= {
Group terminator= }
Delimiter= }{
TDS= :
For the third block:
DES= Tagged Delimited
Group indicator= {
Group terminator= }
Delimiter= }{
TDS= :
Now the first element of the third block gets parsed ok but when the parser comes to the second or the end of the third block it says "MTI. Not all the buffer was used when reading message". How do I model the block so that the elements are dynamically created using the tag names?
In the fourth block, the text block everything works ok, but my guess is that its because I use another delimiter and group identifier than for the entire message.
Thanks in advance!
-- edited, fixed a typo in the third block _________________ IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
Back to top |
|
 |
kimbert |
Posted: Mon Oct 22, 2007 4:49 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
You should be able to look at the SWIFT sample and see how it is done there.
re: BIP5288, you have my sympathy. It's always hard to diagnose. v6.1 will emit user trace messages telling you what the parser is up to, which should make it easier. |
|
Back to top |
|
 |
billybong |
Posted: Mon Oct 22, 2007 4:55 am Post subject: |
|
|
 Disciple
Joined: 22 Jul 2005 Posts: 150 Location: Stockholm, Sweden
|
Thanks for the quick response Kimberly.
I've used the sample MT103 as a template for parts of my message.
The problem is that it models all fields which I dont want to do since I'm creating a more generic message. If I model all possible fields I'm sure I'd be able to work it out but I'd rather not. _________________ IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
Back to top |
|
 |
kimbert |
Posted: Mon Oct 22, 2007 11:42 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
If I model all possible fields I'm sure I'd be able to work it out but I'd rather not. |
I think you may struggle to get this working. SWIFT is a very difficult format to model, and it is hard enough when you are using modelled fields. Trying to model it using self-defining fields is just going to make your job even harder.
If you want a really easy solution, you could always purchase the SWIFT message sets from IBM.
Quote: |
In the fourth block, the text block everything works ok, but my guess is that its because I use another delimiter and group identifier than for the entire message. |
Your guess is probably correct. |
|
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
|
|
|
|