A bug in Xlate??

[Rentian Huang]

Greetings Cloverleafers!!!

V5.2 on AIX

I have a CONCAT action:

Code:

Separator: .br
Source:
  1(0).1(0).1(%g2).OBX.00573
  @obx5
Destination:
  @obx5

When I worked on this xlate, .br becomes \.br\ automagically!!!  I have never touch anything on this action.

Any input is appreciated!

Sam  8)[/code]

Topic

[Anonymous]

Rentain,

I played around with this a little and you’re correct that with the right sequence of events it adds back slashes to the back slashes.  I don’t think this should have caused a problem though.

If you create the concat action and save it with the .b separator, it will write \.b\ into the file.  Then if you load it you’ll have \.b\ in the separator field.  When I saved it again is still only wrote out \.b\ again (I was afraid it might write \\.b\\ but it didn’t).

The reason that it adds extra back slashes in the first place is that the action is evaluated in a TCL procedure and the back slashes by them selves would be escape characters instead of literal back slashes.  The xlate GUI is just anticipating this and adding the extra back slashes.

[Rentian Huang]

Greg,

Thanks for your analysis! I don’t know whether the destination system (Eclipsys) will care about the added back slashes, we still pending for connectivity.

But when I put the .br as one of the source fields, it does what it suppose to do.

Sam

Code:

Source:
  1(0).1(0).1(%g2).OBX.00573
  =.br
  @obx5
Destination:
  @obx5

[Eric Fortenberry]

We just recently experienced the same problem with putting backslashes in the CONCAT Separator field.  We are running 5.8 on AIX.

What’s the protocol for submitting bugs that are found?

Thanks,

Eric

[Jim Kosloskey]

Hmmm I just tried a test and it seemed to work fine for me.

Admittedly this was a simplistic test.

Could you share the values that are being concatenated?

We are Cloverleaf 5.6 Rev 2.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Eric Fortenberry]

Here are the steps to repeat the problem:

1. Add a CONCAT action to an Xlate.

2. Set the separator to a single backslash ().

3. Save.

4. Reload the Xlate.

After reloading the Xlate, you will probably see the separator of the CONCAT action set to double backslashes (\).

The tricky part is that the problem doesn’t show up until you reload/reopen the Xlate.  The IDE appears to be saving the separater as a TCL-escaped string, but when the IDE reads the Xlate file, it appears to be reading the value literally.

Thanks,

Eric

[Jim Kosloskey]

Eric,

OK I just followed that scenario and now see the issue.

As to filing for a bug, with the new support from Infor/Lawson I, for one, am unsure how to proceed for filing a bug report.

However, thi certainly seems like it should not be happening.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies