Re: RunSQL

On Wed, Oct 4, 2017 at 4:42 PM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 10/04/2017
04:33:15 PM:

When creating SQL scripts using IBM I Access Client and saving them
on the IFS through a net server share, three garbage characters show
up when viewing the file via wrklnk. If you use any pc editor to
view, these characters are not present. Anyone seen this before and
have a way to fix?

The byte order mark (BOM) is a Unicode character, U+FEFF byte order mark
(BOM), whose appearance as a magic number at the start of a text stream
can signal several things to a program consuming the text:[1]
•What byte order, or endianness, the text stream is stored in;
•The fact that the text stream is Unicode, to a high level of confidence;
•Which of several Unicode encodings that text stream is encoded as.

BOM use is optional, and, if used, should appear at the start of the text
stream.

Wow, you lifted that straight from Wikipedia, even including the
footnote mark! For anyone who cares to read further:

https://en.wikipedia.org/wiki/Byte_order_mark

Chris, the fact that you're seeing three bytes strongly suggests it's UTF-8:

https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8

I would think the extra characters are harmless, so if you can get
yourself to not mind seeing them, I doubt there is any harm in leaving
them there. Maybe there is some way to convince either the client
software to send in a different encoding or the IBM i to use the
appropriate CCSID. (I think it should be 1208.) You can of course set
the CCSID manually, but that would be a pain if this is happening a
lot.

John Y.