| Author |
Message
|
| whytec |
 Posted: Wed Mar 01, 2006 9:36 pm Post subject: Control character handling - V2.1 vs V5 |
 |
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
I have recently migrated a system from version 2.1 to 5 and am going through a testing phase. I have noticed that some messages are coming out with carriage returns in some of the tags (formatted text) where this wasn't happening in V2.1. I checked the inbound message and found that the formatted text contains carriage returns.
Am I correct in assuming that V2.1 omits control characters from the data in tags and V5 leaves them? If not, is there some setting that would have been used in the V2.1 platform? I didn't implement the V2.1 solution so I don't have that info.
Last edited by whytec on Mon Mar 06, 2006 6:00 pm; edited 2 times in total |
|
| Back to top |
|
 |
| mgk |
| Posted: Thu Mar 02, 2006 12:45 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
Can you post more information about your set up please: Is this XML or MRM messages? Can you post a sample input msg, and any relevant ESQL.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| whytec |
| Posted: Thu Mar 02, 2006 4:55 pm Post subject: |
|
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
In this case I'm using XML, but we use MRM in other flows as well.
Basically I just want to know if there's any difference between V2.1 and V5 with regards to control characters in message data.
Is there somewhere that I can find a complete list of technical differences between V2.1 and V5? I need to be aware of any of these changes. The change in rounding behaviour caught me unaware as well  |
|
| Back to top |
|
|
| whytec |
| Posted: Mon Mar 06, 2006 4:09 pm Post subject: SOLVED: Control character handling - V2.1 vs V5 |
|
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
I found the problem.
In our ESQL we have a few lines of code like this:
| Quote: |
| SET tempStr = tempStr || TRIM(otherStr) || ' ; '; |
This was to get text formatted for a specific supplier.
The migration script for WBIMB5 took this code and turned it into this:
| Quote: |
SET tempStr = tempStr || TRIM(otherStr) || ';
'; |
The migration script found the first instance of the ';' char, regardless of whether it was contained in a string, and assumed it required a new line, adding an extra carriage return in the resultant string.
Trap for young players I guess  |
|
| Back to top |
|
|
| whytec |
| Posted: Mon Mar 06, 2006 6:00 pm Post subject: |
|
|
Apprentice
Joined: 28 Nov 2005
Posts: 26
Location: Brisbane Australia
|
After more investigation I've found that it wasn't the migration script that caused this problem, it was when I right click on the esql editor and select Format from the menu. There must be a bug in the formatting routine so that when it sees this:
| Quote: |
| SET somestring = ';'; |
it formats it like this:
| Quote: |
SET somestring = ';
'; |
Does anyone know a way around this? |
|
| Back to top |
|
|
|
|
