This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
One of the big challenges when receiving text files via FTP etc from external sources is to determine what CCSID it is encoded in. By default 1252 or 819 is used but often it should be 1208 ( UTF-8 ) instead. Especially when it is XML-files. If the file has byte order markers (BOM) and the CCSID is the default 1252 then XML-SAX in RPG will fail - invalid characters.
I would like a way to set the CCSID depending on the content of the file. So it could be 1208 (UTF-8), 1200 (UTF-16), 819 (Ascii / ISO-8859-1) etc.
An easy way to implement this could be enhancing CHGATR allowing the value *CONTENT for the CCSID.
Let the IFS set the CCSID depending on BOM codes when writing files
Today CCSID on files in IFS has no automatic connection the content, which means that you manually have to change the CCSID with CHGATR or setccsid command. This is not practical if files are made by FTP or NETSERVER. If you upload a file with FTP...
Allow UTF-8 with bom to override CCSID attribute for IFS files
Today you can include SQL in PL/SQL Stored procedures, UDTF and compound statements like this; begin include SQL '/prj/sql/NHODATA/VIEWS/KRTSPLV1.sql';end; However if the included SQL file is in UTF-8 with BOM codes you will get this error: SQL St...
Do not place IBM confidential, company confidential, or personal information into any field.