× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Charles,

The best solution, here, is for the python process to be fixed to understand UTF-8 with a BOM.

What Chris describes is a GOOD thing (even if he doesn't see it that way!) The scripts are UTF-8, but his upload process is marking the file as CCSID 1252. That means the system will interpret the file as 1252 -- and that's NOT okay. There are nearly 100000 characters that are different in 1208 vs 1252. So the fact that it is failing and forcing him to change the CCSID to 1208 is a GOOD THING. (It would be even better if the file transfer process detected the BOM and automatically made it 1208... but that is not ACS's problem. Sounds like he's using NetServer, I would consider asking IBM to change NetServer to detect the BOM and set the CCSID correctly. (Which would be impossible if ACS didn't put the BOM in there... so, again, it is a GOOD thing)

Furthermore, consider what happens if you open your SQL script in Windows software where there are no CCSIDs... if it sees the BOM, it treats it as UTF-8, if not most software will treat it as "ANSI" (ASCII) even though it is really UTF-8. Notepad++ is an exception to that rule -- but almost nothing else I've seen will treat it as UTF-8 unless you provide a BOM.

It is a good thing. It is progress... there might be growing pains while we get other software to upgrade their code, but it is a step in the right direction.



On 3/14/2017 4:05 PM, Charles Wilt wrote:
Yes..

Another team uses an automated python process run the scripts and it's not
currently set up to handle UTF-8 BOM.

They are looking at changing it, in the meantime...I can remove the BOM
with notepad++.

Chris points out problems he's had.

Charles


On Tue, Mar 14, 2017 at 2:51 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
wrote:

This seems like a GOOD thing, to me... Is it causing a problem?


On 3/14/2017 8:52 AM, Charles Wilt wrote:

All,

Apparently, the Run SQL Scripts component of ACS saves files as UTF-8 BOM.

I don't see any option's for changing this.

Am I missing something?

iNav's Run SQL Scripts saves as UTF-8, without the BOM.

Thanks!
Charles Wilt

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.