| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Parser Problem with SWIFT |
« View previous topic :: View next topic » |
| Author |
Message
|
| m.schneider |
 Posted: Mon Jun 30, 2008 4:02 am Post subject: Parser Problem with SWIFT |
 |
|
Centurion
Joined: 10 Apr 2007
Posts: 132
Location: Germany
|
Hi,
I have modeled a SWIFT-Message as a MessageSet.
The definition for 35B is the following
Global Element 35B (Sequence, closed) min occur 1, max occur 1
Local complex type
Sequence 35B min occur 0, max occur 1
ISIN min occur 0, max occur 1
Description min occur 0, max occur 4
Processing this is no problem:
:35B:ISIN US045054AA16
ASHTEAD CAPITAL INC
But processing this:
:35B:/US/1309112G4
CALIFORNIA STATEWIDE CMNTYS DE
I receive the following error:
No markup was found following the complex child or group 't_Sequence_35B_Seq_1'. The parent of this child or group has a Data Element Separation of 'All Elements Delimited' or 'Variable Length Elements Delimited'. All complex children within a type or group with a Data Element Separation of 'All Elements Delimited' or 'Variable Length Elements Delimited' mus be followed by some markup. That is a 'Repeating Element Delimiter', a 'Delimiter', a 'Group Terminator' or some markup from a higher level in the message model.
I use <CR><LF> ad delimiter, so that can not be the problem.
I also tried upgrading the runtime from 6.003 to 6.006 with no result.
Do I have to model the complex type as a choice?
Help is much appreciated! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Jul 07, 2008 4:47 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
If you're on v6.1, switch on debug-level user trace - the TDS parser is quite chatty about what it is doing.
I used to be familiar with the format of field 35B, but I can't remember the details now ( and you have not provided them ). |
|
| Back to top |
|
|
| m.schneider |
| Posted: Mon Jul 07, 2008 4:53 am Post subject: |
|
|
Centurion
Joined: 10 Apr 2007
Posts: 132
Location: Germany
|
Does this work under 6.0 too?
By details I assume you mean the SWIFT-specs:
Option B
[ISIN1!e12!c] (Identification of Security)
[4*35x] (Description of Security) |
|
| Back to top |
|
|
| m.schneider |
| Posted: Mon Jul 07, 2008 4:58 am Post subject: |
|
|
Centurion
Joined: 10 Apr 2007
Posts: 132
Location: Germany
|
I created a workaround with defining the following data pattern:
(ISIN {1}[A-Z0-9]{12})|(/[A-Z]{2}/[A-Z0-9]*)
This works for ISIN and also CUSIP, SEDOL, but you have to determine with ESQL code which is used. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jul 07, 2008 5:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Does this work under 6.0 too? |
No - TDS user trace is a v6.1 feature. |
|
| 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
|
|
|
|
