Skip to Main Content
IBM Power Ideas Portal

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:

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,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. 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.

Status Future consideration
Workspace IBM i
Categories Print
Created by Guest
Created on Dec 17, 2021

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)


Use Case:

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.


Idea priority High
  • Guest
    Apr 15, 2022
    .Thank you for information you provided. We recognize the value of this enhancement and will include it among the list of candidates for implementation in a future release. IBM Power Systems Development
  • Guest
    Mar 16, 2022

    Okay, I just verified what you asked, and I responded incorrectly.

    When the file exists and STMFOPT(*NONE) (the default) is specified, the CPYSPLF fails.

    When the file exists and STMFOPT(*REPLACE) is specified, with WSCST(*NONE) the file's data is replace but the new content is written to the file using the Job's CCSID not the CCSID of the file, making it unusable.

    If the WSCST(*PDF) is specified, and the IFS does NOT currently exist, then a PDF is created with CCSID(65535) but its content is CCSID(819). This is fine.

    If, however, I create the IFS file before hand, with CCSID(1208) and use STMFOPT(*REPLACE) and WSCST(*PDF), then the file is replaced, its CCSID retained, and the content is written to the file as CCSID 1208.

    So my request is to provide a CCSID parm on CPYSPLF that will create the file using that CCSID in both contexts (PDF or TEXT) and write the data to the file using it as well.

  • Guest
    Mar 16, 2022

    Yes, if the file already exists, the existing CCSID is respected.
    However, since there is NO CCSID parm on CPYSPLF, it creates the the IFS file with the current job's CCSID. I want to be able to tell it to use 1208 instead. Hence the request to add a CCSID parm to the command itself. Thanks.

  • Guest
    Mar 16, 2022

    Are you saying that the CPYSPLF command currently honors the CCSID of the existing IFS file and performs the CCSID conversion correctly?

  • Guest
    Feb 24, 2022

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Feb 22, 2022

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. This would be one of the more valuable usability enhancements to provide.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Jan 14, 2022

    Thank you for your request. We will take a deeper look soon.

  • Guest
    Dec 21, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Print
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None