Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CSSID 65535

51 views
Skip to first unread message

Peter Kinsman

unread,
May 4, 2012, 2:32:28 AM5/4/12
to
Model 170 at V4R4
Access 2000 on PC running XP Home
File created with QUERY from S/36 file with attached Data Description has
text fields as CSSID 65535

Data Transfer to a csv file with Convert CSSID 65535 ticked these fields are
converted to ASCII
ODBC Import into Access leaves these fields a mess even though Convert CSSID
65535 is ticked.

Any ideas please - apart from the obvious get more up to date hardware and
software?

Many thanks

Peter Kinsman


iseriesflorida

unread,
May 4, 2012, 7:50:57 AM5/4/12
to
Go ODBC ADMIN, click on your ODBC configuarion that your using, look
for a tab called conversions, check the box and then try it.

Peter Kinsman

unread,
May 4, 2012, 10:51:52 AM5/4/12
to
It is that tab that displays the Convert CSSID 65535 tickbox - which has
been ticked.

I tried CHGJOB CCSID(285) and one file translated perfectly but another
didn't.

"iseriesflorida" <iseries...@yahoo.com> wrote in message
news:1751e152-4336-4066...@e42g2000yqa.googlegroups.com...

CRPence

unread,
May 4, 2012, 12:31:44 PM5/4/12
to
On 03 May 2012 23:32, Peter Kinsman wrote:
> Model 170 at V4R4
> Access 2000 on PC running XP Home
>
> File created with QUERY from S/36 file with attached Data Description
> has text fields as CSSID 65535

Running the Query Definition (*QRYDFN) in the S/36 Environment? What
is the DSPFFD of both the input [query] file and the output file
(OUTFILE) created by the query? What is the CCSID for the job and the
*USRPRF being used to run the query?

> Data Transfer to a csv file with Convert CSSID 65535 ticked these
> fields are converted to ASCII

CA file transfer from the server to the client with an option to
create as CSV [¿rwtoPC?] works fine using the "translate 65535" [aka
"Force Translate"] option enabled.

> ODBC Import into Access leaves these fields a mess even though
> Convert CCSID 65535 is ticked.

Does this imply a SELECT using the CA ODBC driver to effectively do
the same as above but as requested from, for example, MS SQL Server?

> Any ideas please - apart from the obvious get more up to date
> hardware and software?

Change user profiles to define their appropriate LANGID and CCSID
values; do not allow the latter to resolve from QCCSID esp. if that
value is 65535. Correct existing files to tag the columns with the
proper CCSID; this might include replacing any S/36 style files with SQL
TABLE or DDS described... which is effectively required anyway to be
doing SQL more directly to avoid the Query/400 query in between.

Regards, Chuck
0 new messages