| Author | 
		  Message | 
  		
  		
		     Topic: Problem with TDS message set | 
  		
  		
		  Angel
  
	  	  Replies: 11 Views: 5886
  | 
		   Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Mar 24, 2006 6:39 am   Subject: Problem with TDS message set | 
  		
  		
		  | Which characters should I use then in my input message? The same ones as you are using now, but replace every occurrence of <SOH> with a single byte 0x01. It's up to you how you do that. Persona ... | 
  		
  		
		     Topic: Problem with TDS message set | 
  		
  		
		  Angel
  
	  	  Replies: 11 Views: 5886
  | 
		   Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Mar 24, 2006 6:30 am   Subject: Re: Problems with TDS message set | 
  		
  		
		  Hi,
 
 So, the <CF><LF> may not work either.
 
 You need to try<CR><LF>
 
 I have just discovered that my input message may be wrong, but I will try this also...
 
 Thanks, | 
  		
  		
		     Topic: Problem with TDS message set | 
  		
  		
		  Angel
  
	  	  Replies: 11 Views: 5886
  | 
		   Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Mar 24, 2006 6:27 am   Subject: Problem with TDS message set | 
  		
  		
		  Hi again,
 
 Sorry, I missunderstood your question.
 
 In the input message the <SOH> is used as 5-character string. But it is the x0x1 that is the delimiter. Aha, now I understand. So my input  ... | 
  		
  		
		     Topic: Problem with TDS message set | 
  		
  		
		  Angel
  
	  	  Replies: 11 Views: 5886
  | 
		   Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Mar 24, 2006 6:21 am   Subject: Problem with TDS message set | 
  		
  		
		  Hi again,
 
 Yes, "<SOH>" is the single byte with the value 0x01. So the TDS parser understand that <SOH> is 0x01 because I have written explicitly <SOH> as 5-character string in the ... | 
  		
  		
		     Topic: Problem with TDS message set | 
  		
  		
		  Angel
  
	  	  Replies: 11 Views: 5886
  | 
		   Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Mar 24, 2006 4:51 am   Subject: Problems with TDS message set | 
  		
  		
		  Hi,
 
 I don't get any exceptions, the message is parsed as if everything is the first tag, like below:
 
 tag 1 = FIX.4.3<SOH>9=278<SOH>35=B<SOH>49=SSMB<SOH>56=CSFB<SOH> ... | 
  		
  		
		     Topic: Problem with TDS message set | 
  		
  		
		  Angel
  
	  	  Replies: 11 Views: 5886
  | 
		   Forum: WebSphere Message Broker (ACE) Support   Posted: Fri Mar 24, 2006 4:31 am   Subject: Problem with TDS message set | 
  		
  		
		  Hello,
 
 I am trying to create a TDS message set according to the below message:
 
 8=FIX.4.3<SOH>
 9=278<SOH>
 35=B<SOH>
 49=SSMB<SOH>
 56=CSFB<SOH>
 34=1<SOH>
 5 ... |