MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2014

Re: SYSCOLUMNS returning garbage for COLUMN_TEXT



fixed

Just verified - did a CHGJOB CCSID(37) and the data was converted automatically.

Except for rare circumstances, it is strongly recommended to change system value QCCSID to 37 (or whatever is the primary national setting).

I think Chuck Pence listed some possible exceptions to look at.

Vern

On 8/5/2014 8:32 AM, DeLong, Eric wrote:
That would be my expectation. Database ccsid translates to job ccsid. Jobs running ccsid 65535 do not translate, so programs receive data in Unicode which must be translated manually (via iconv or some other translation api). Bruce Vining has explained how file / job / device ccsids play together before. Check the archives...

-eric

Sent from my ASUS MeMO Pad

Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:


Good point - John could also try changing his job to CCSID(37) and the
value should show up without casting, right?

On 8/5/2014 8:08 AM, DeLong, Eric wrote:
John, can you check your system QCCSID value? You probably do not want 65535...

Sent from my ASUS MeMO Pad

"John R. Smith, Jr." <smith5646@xxxxxxxxx> wrote:


I am trying to retrieve column information for a file using SQL. The file
was created using DDS and has TEXT values as shown below. However, when the
below sql statement on a V7.1 machine, it returns garbage / unprintable
characters but it works on a V6.1 machine. Is the V7.1 machine missing a
PTF or something or what is different between V6.1 and V7.1?





==> Here is the DDS

R RTEST



FIELD1 10 TEXT('FIELD1')





==> Here is the SQL statement

SELECT SYSTEM_TABLE_NAME, SYSTEM_COLUMN_NAME, COLUMN_TEXT FROM SYSCOLUMNS
WHERE SYSTEM_TABLE_NAME = 'TESTPF'





==> Here are the results of the SQL on a V7.1 machine.

SYSTEM_TABLE_NAME SYSTEM_COLUMN_NAME COLUMN_TEXT

TESTPF FIELD1 ã ñ á < à





==> Here are the results of the SQL on a V6.1 machine.

SYSTEM_TABLE_NAME SYSTEM_COLUMN_NAME COLUMN_TEXT

TESTPF FIELD1 FIELD1

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact