| Author |
Message
|
| amiivas |
 Posted: Fri Dec 07, 2007 12:16 am Post subject: Ascii char []Input as PARSER |
 |
|
Apprentice
Joined: 14 Oct 2007
Posts: 44
Location: Texas, USA
|
Hi,
I am trying to process a input in which the data is parsed with '|' char. But there are Ascii char [] between the pipes, which is getting mismatched while goiing in a message set.
Kindly help me along to get rid of this Char.
Is it a group seperator kind of thing or smth else.
A part of input file:
JOB|CUSTOMER|A|20071205|000000|411004|
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
||MAS|998775||CUSTOMER|213421267||CUSTOMER|JOB2134233|||||CUSTOMER|234242444|ASD|DELETE|||||||N|ACWERER||||F|||+409|W||||||||||||
Thanks in advance,
AMIT |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Dec 07, 2007 3:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
We have no idea what this character is.
In ascii, this is the represention of any one of several "non-printable" characters.
So it could be a lot of things, including a line ending character or etc.
Presumably the documentation on your data format will tell you what it should be.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 07, 2007 3:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If the original format was UTF-8 it might be the representation of a 'special' character that is not printable in ASCII. It might even have clobbered the special character.
Keep the input in the original char set....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| amiivas |
| Posted: Mon Dec 10, 2007 1:27 am Post subject: Problem revised |
|
|
Apprentice
Joined: 14 Oct 2007
Posts: 44
Location: Texas, USA
|
Thanks all for your replies,
After considering the input that ascii char doesn't creates any problem but now the real problem is that my messageset is not able to recognize a next line char. A ascii char corresponding to the next line char (line feed char) sits at the end of any particular group of input. For eg if the name and address is diffrentiated by a new line then we get a new line char at the beginning of the address field in message set.
I have tried using <CR><LF> but still it is not working.
one possible sol. was to give a dummy vacant field at the end of name tag to make the matching of the address but that is not correct in my sense.
Could be ther any possible sol. for this?[/b] |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 10, 2007 8:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Do you have a document that describes, in a logical way, the data format you are trying to model?
Does that document specify what "line endings" should be used - whether a <cr><lf> should be used, a <lf> should be used, or whether the sending platform gets to decide?
Do you have any idea if the data you are receiving is correct for the format? Maybe you are supposed to be failing to parse this data.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Dec 10, 2007 1:18 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Could be ther any possible sol. for this? |
There is a solution. But you will need to provide a lot more information if you want us to find that solution.
Please describe the problem using an example. Describe what the message tree should look like after a successful parse. Give an example of a message which parses successfully, and also one which fails. |
|
| Back to top |
|
|
|
|
