| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Hex Tag Delimiters |
« View previous topic :: View next topic » |
| Author |
Message
|
| cloucas |
 Posted: Wed Mar 22, 2006 1:14 am Post subject: |
 |
|
Apprentice
Joined: 10 Mar 2006
Posts: 37
|
Guys
I still don't see how any of these solutions can help me here...what i need is a way to enter a tag value in the toolkit that is two bytes long. These two bytes are expressed in EBCDIC format.
An example is:
F1F3 (This results in ASCII 13), so it can be entered in the toolkit Tag Value as '13')
5D01 (This results in a non printable ASCII characters so I cannot type it in)
I have tried entering <U+5D01> but the toolkit thinks that the tag I am trying to enter is '<U+5D01>', thereby rejecting it because it fails tag length definition of 2 bytes.
Thanks for your continuing help
cloucas |
|
| Back to top |
|
 |
| cloucas |
| Posted: Wed Mar 22, 2006 1:29 am Post subject: |
|
|
Apprentice
Joined: 10 Mar 2006
Posts: 37
|
What other methods of parsing can I use if indeed TDS does not allow me to enter the tag values as hex or binary?
Does that mean I have to write custom parsers, or read the message as BLOB and parse it in ESQL?
Thanks
cloucas  |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Mar 22, 2006 1:57 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
hi cloucas,
I think you will need to parse it in ESQL or write a custom parser, unless these binary tags are just there for decoration (i.e. the fields always come in the same order).
Sorry to be the bearer of bad news. |
|
| Back to top |
|
|
| cloucas |
| Posted: Wed Mar 22, 2006 3:12 am Post subject: |
|
|
Apprentice
Joined: 10 Mar 2006
Posts: 37
|
|
| Back to top |
|
|
| dsriksha |
| Posted: Wed Mar 22, 2006 11:22 am Post subject: |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
| cloucas wrote: |
Thanks all.
cloucas |
Oh my gosh!!!!!!, I am very sad that you didnt get the solution, eventhough I solved it for you. 
Kimbert, could you please tell me where my method not going to work?
The trick is if the delimiter is 5D01 then set delimiter to 5D and group terminator to 01.   |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Mar 23, 2006 1:50 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
drishka,
Your model will certainly parse the example bitstream which cloucas provided, but will it cope with all of the bitstreams below? If not, then it is not a solution.
| Code: |
A07056.1307399405.X3Y.BXY
1307399405.X3Y.BXY.A07056
BXY.X3Y.A07056.1307399405
BXY.X3Y.1307399405.A07056 |
The TDS parser does not use delimiters or group terminators to identify a field. They just indicate where a field ends. Therefore I don't think your model will not cope with fields which occur in random order, fields which are optional, and fields which can repeat a variable number of times. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
