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:
Post your ideas
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
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.