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
Add CCSID Parameter to CPYSPLF when TOFILE(*TOSTMF) Specified
When copying a SPOOLED File to the IFS (as text or PDF) the CPYSPLF command is normally used. However when TOFILE(*TOSTMF) is specified and the target file does not exists, it creates the file as "binary" or CCSID(65535) when WSCST(*PDF) is used, and the Job's CCSID when anything else is used. I would like to be able to specify the created file's CCSID, such as CCSID(1208) when using CPYSPLF TOFILE(*TOSTMF)
Today we have to call or own functions to create an IFS file with the CCSID in question and then issue the CPYSPLF command. When the file already exists, CPYSPLF does not replace it, so it uses the CCSID of the existing file. Which is great. However, from the command entry line, or in CL, the ability to specify the newly created file's CCSID is important.
Do not place IBM confidential, company confidential, or personal information into any field.