I have also not seen any way specify the file encoding.
Additionally, there is no way to change the line end markers either.
I've also seen the BOM become an issue when I save the script directly to an iSeries IFS Share.
When saving directly from windows the files get created with a CCSID of 1252 and CRLF line endings.
I've had to update the CCSID to 1208 before I'm able to use the file with the RUNSQLSTM command.
CHGATR OBJ('--IFSSHAREPATH--/test.sql') ATR(*CCSID) VALUE(1208)
So far the line endings haven't caused me an issue.
Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, March 14, 2017 7:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: ACS Run SQL Scripts saves files as UTF-8 BOM
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
midrange.com
