TCL data conversion issue in Cloverleaf 5.8

[Graham Hartley]

I have an encoding issue now we have moved from Cloverleaf 5.3 to 5.8 in Windows that I am struggling to resolve.

The problem is storing text which contains extended ASCII codes in an SQL Server database.  

The following code demonstrates the issue:


odbc sqlallochandle SQL_HANDLE_STMT $hdbcDW  hstmtDWRS
set SQL “insert into OCMTEXTRESULTS (AgpSeqNo,Comment,OcmTransKey,ResultCode,SessionNumber,EURDate) values (’1′,’b[code]
odbc sqlallochandle SQL_HANDLE_STMT $hdbcDW  hstmtDWRS
set SQL “insert into OCMTEXTRESULTS (AgpSeqNo,Comment,OcmTransKey,ResultCode,SessionNumber,EURDate) values (’1′,’b

Topic

[David Barr]

You could try putting “encoding system identity” in your script before you call msgget or connect to your database. We had to do something similar when we upgraded to 5.8.

[Graham Hartley]

Thanks for the response.  Given it a try and it still dosen’t work I am afraid

[James Cobane]

Graham,

If you are receiving the message on an inbound thread before processing through your proc, make sure you have the encoding on the thread set to Windows-1252.  If you leave it as the default ASCII, it will likely be skewed coming into your proc.  Likewise, if this is going outbound, you would want to configure the outbound thread with Windows-1252 encoding.

Hope this helps.

Jim Cobane

Henry Ford Health

[Graham Hartley]

Thanks James for your comments however the thread used to process the message already has its encoding set to windows-1252 therefore I don

[James Cobane]

If you haven’t already, you should open a case with Support.

Jim Cobane

Henry Ford Health System

[Author]

Replies