Python 3 locally on the IBM i. Anytime I query a 65535 field I get what appears to be hex. I notice when the python job spawns it is CCSID 37 instead of 65535 our default. Interactively I tried issuing a chgjob to ccsid 37 via qsys2.qcmdexc and when I query and print the result list the 65535 fields look the same.
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Tuesday, December 19, 2017 3:57 PM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] 65535 CCSID
The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin.
On Tue, Dec 19, 2017 at 2:57 PM, Jeremy Meyer <JMeyer@xxxxxxxxxxxxx> wrote:
I have been using Python and ibm_db_dbi for automating some tasks. The problem I have is our CMS system stores its data in 65535 CCSID fields. Is there an easier way to translate that than to cast them to 37 on each field?
Dealing with encoding issues is one thing which I think is significantly easier in Python than in SQL.
Which Python are you using, and on which platform?
If you just query the data normally, without explicitly handling CCSID, what do you get?
This is the IBMi Open Source Roundtable (OpenSource) mailing list To post a message email: OpenSource@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: OpenSource-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/opensource
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.