| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Different delimiters |
« View previous topic :: View next topic » |
| Author |
Message
|
| Nyusser |
 Posted: Tue Jul 02, 2002 5:39 am Post subject: Different delimiters |
 |
|
Apprentice
Joined: 02 Jul 2002
Posts: 48
|
Hi,
I have a simple question here: i have a format with three fields. The first two fields are terminated by SPACE, but the third field may contain SPACES and can be delimited with almost any other special character (# for example). With CWF I'd use the end of bitstream termination for the third field, but it doesn't exist in the TDS. What kind of compound types should I create for the message?
Currently I have following three compound types, but they're not working:
MAIN_TYPE - SEQUENCE, CLOSED, ALL ELEMENTS DELIMITED, Space as a delimiter
SPACE_TYPE - ORDERED SET, CLOSED, ALL ELEMENTS DELIMITED, <Space> as a delimiter
END_TYPE - ORDERED SET, CLOSED, ALL ELEMENTS DELIMITED, # character as a delimiter.
The data in the third field is lost after the first space character. Can anyone give me some hints? |
|
| Back to top |
|
 |
| Nyusser |
| Posted: Tue Jul 02, 2002 5:41 am Post subject: |
|
|
Apprentice
Joined: 02 Jul 2002
Posts: 48
|
Forgot to mention,
MAIN_TYPE contains SPACE_TYPE and END_TYPE
SPACE_TYPE contains STRING1 and STRING2
END_TYPE contains STRING3 |
|
| Back to top |
|
|
| Nyusser |
| Posted: Tue Jul 02, 2002 10:47 pm Post subject: |
|
|
Apprentice
Joined: 02 Jul 2002
Posts: 48
|
I use the following test message to debug the flow:
'fname lname street number'
And I would like to have the message parsed as:
STRING1 = 'fname'
STRING2 = 'lname'
STRING3 = 'street number'
I used trace node to solve the problem and I got almost what I wanted with too different methods:
I set the Data element separation method of MAIN_TYPE to UNDEFINED
-> The message was parsed fine, but the flow was unable to put the message into the output queue...
I set the delimiter for the main type to ##
-> The message was parsed fine, but the output message was like:
'fname lname ##street number#'
This is not acceptable, because the format of the output message has to be equal to the input message.
I understand why this is happening, but I don't have any ideas how to workaround this problem... Any ideas? |
|
| Back to top |
|
|
| Nyusser |
| Posted: Wed Jul 03, 2002 4:00 am Post subject: |
|
|
Apprentice
Joined: 02 Jul 2002
Posts: 48
|
No need to reply anymore -> found the workaround.  |
|
| 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
|
|
|
|
